geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aparnard <>
Subject [GitHub] incubator-geode pull request #190: Feature/geode 11 gfsh commands
Date Wed, 06 Jul 2016 23:10:15 GMT
GitHub user aparnard opened a pull request:

    Feature/geode 11 gfsh commands

    GEODE-11: Implementing GFSH command to list Lucene indexes
    Added a GFSH command to list the Lucene indexes.  Also added a dunit test to verify this
functionality. The file is required to register
the Lucene commands in GFSH. The GFSH command to list the Lucene indexes is implemented through
the LuceneIndexCommands class and the LuceneListIndexFunction class gets information about
the Lucene indexes from the cache.

You can merge this pull request into a Git repository by running:

    $ git pull feature/GEODE-11-gfsh-commands

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #190
commit ef735dac52e042e19d9984aef83e2d2ab60791a6
Author: Dan Smith <>
Date:   2016-07-01T17:45:04Z

    GEODE-11: GFSH commands for Lucene
    Signed-off-by: Aparna Dharmakkan <>

commit dd6fa830269dffba3e2e4be819f69e68a9442338
Author: Aparna Dharmakkan <>
Date:   2016-07-06T22:43:26Z

    GEODE-11: Implementing GFSH command for listing lucene indexes.
    Added the LuceneIndexCommands class that implements the list lucene index functionality
in GFSH and the LuceneListIndexFunction class
    that gets the information about lucene indexes from the cache. Also added a test to verify
this functionality. The file is required to register the lucene commands
in GFSH.
    Signed-off-by: Gester Zhou <>


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message