geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-2958) create replicate region with lucene index may restore destroyed defined lucene index
Date Wed, 24 May 2017 18:38:04 GMT

    [ https://issues.apache.org/jira/browse/GEODE-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023420#comment-16023420
] 

ASF subversion and git services commented on GEODE-2958:
--------------------------------------------------------

Commit 662358fdba33ce2ea99cadfe07303361b26ead56 in geode's branch refs/heads/develop from
[~barry.oglesby]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=662358f ]

GEODE-2958: Destroying a defined index now removes the RegionListener


> create replicate region with lucene index may restore destroyed defined lucene index

> -------------------------------------------------------------------------------------
>
>                 Key: GEODE-2958
>                 URL: https://issues.apache.org/jira/browse/GEODE-2958
>             Project: Geode
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Jason Huynh
>             Fix For: 1.2.0
>
>
> Executing the below commands in gfsh will result in the destroyed index being created.
 It appears that the combination of destroying the lucene index while specifying the region
name and index name, along with attempting to create a replicate region can cause the destroyed
index to be restored and created when a partition region with the same name finally is created.
> create lucene index --name="GHOST_INDEX" --region="test" --field=name
> list lucene indexes
> destroy lucene index --region=test --name="GHOST_INDEX"
> create lucene index --name="LUCENE_INDEX" --region="test" --field=name
> create region --name=test --type=REPLICATE
> create region --name=test --type=PARTITION
> list lucene indexes
> If the --name parameter of the index was not supplied on the destroy, then things work
fine.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message