[
https://issues.apache.org/jira/browse/GEODE-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-3932:
-----------------------------
Description:
GEODE-3928 is about making sure that after a lucene index is added to an
existing region, the data in the region is indexed for queries.
This task is clarifying that we should not wait until a query is executed
before indexing the data. The implementation details of GEODE-3928 are vague
about whether the indexing will happen immediately or when a query executes.
Acceptance:
After calling create lucene index on an existing region, indexing should begin
and stats should reflect that data is added to the index.
Implementation Details:
There may be nothing to do here, depending on how GEODE-3928 is implemented.
But if we haven't done anything to eagerly trigger indexing of data, we may
need to add a second function to call computeRepository on all members after
the index is created on all members.
was:
The existing index command should allow a Lucene Index to be created on an
existing region. It should call the function created in GEODE-3929.
The command should wait until the indexing is complete before returning. This
may require another function to call computeRepository on all buckets or if
computeRepository is invoked asynchronously in the previous function, it might
want to wait until the result is available.
> create lucene index on existing region should not wait for a query to index
> data
> --------------------------------------------------------------------------------
>
> Key: GEODE-3932
> URL: https://issues.apache.org/jira/browse/GEODE-3932
> Project: Geode
> Issue Type: Sub-task
> Components: lucene
> Reporter: Jason Huynh
> Priority: Major
>
> GEODE-3928 is about making sure that after a lucene index is added to an
> existing region, the data in the region is indexed for queries.
> This task is clarifying that we should not wait until a query is executed
> before indexing the data. The implementation details of GEODE-3928 are vague
> about whether the indexing will happen immediately or when a query executes.
> Acceptance:
> After calling create lucene index on an existing region, indexing should
> begin and stats should reflect that data is added to the index.
> Implementation Details:
> There may be nothing to do here, depending on how GEODE-3928 is implemented.
> But if we haven't done anything to eagerly trigger indexing of data, we may
> need to add a second function to call computeRepository on all members after
> the index is created on all members.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
