Hi Nitin, I think this is a bug that the function shows up in that list. We actually have a lot of other internal functions that don't show up in that list because they implement the "InternalEntity" marker interface. So this function should probably implement that as well.
There's another question this brings up, which is whether the lucene integration and lucene jars should be added by default to the classpath when you start a gemfire server. That I'm not as sure about. Thoughts? -Dan On Fri, Feb 19, 2016 at 1:48 PM, Nitin Lamba <[email protected]> wrote: > Hi, > > > While starting-up a new geode cluster, I see that a lucene function is > registered even before any regions are created. Following are the simple > steps to reproduce it: > > > ./bin/gfsh > > gfsh>start locator --name=Locator > > gfsh>start server --name=Server1 > > gfsh>list functions > > > Member | Function > > ------- | > --------------------------------------------------------------------- > > Server1 | > com.gemstone.gemfire.cache.lucene.internal.distributed.LuceneFunction > > > Is this expected/ necessary? I would expect such a function to be defined > only when Lucene integration is intended to be used. Please advise if a > JIRA should be opened for this. > > > Thanks, > > Nitin > > >
