Dan - LGTM check it in! ;-) (kidding of course) Jake - there is a side effect to this in that the user would have to reimport all their data into the user defined region too. Client apps would also have to know which of the regions to put into.. also, I may be misunderstanding this suggestion, completely. In either case, I'll support whoever implements the changes :-P
On Wed, Nov 6, 2019 at 2:53 PM Jacob Barrett <jbarr...@pivotal.io> wrote: > > > > On Nov 6, 2019, at 2:16 PM, Jason Huynh <jhu...@pivotal.io> wrote: > > > > Jake, -from my understanding, the implementation details of geode-lucene > is > > that we are using a partitioned region as a "file-system" for lucene > > files. > > Yeah, I didn’t explain well. I mean to say literally create a new region > for the new version of lucene and effectively start over. Yes this is > expensive but its also functional. So new members would create region > `lucene-whatever-v8` and start over there. Then when all nodes are upgraded > the old `lucent-whatever` region could be deleted. > > Just tossing out alternatives to what’s already been posed. > > -Jake > >
