In latest version form query is included in TermsQuery . So no difference in TermsQuery. Still unable to figure it out the reason why filter is not applicable when form field data is in different indexing folder. Please suggest any ideas to debug.
Thanks, Jyothsna -----Original Message----- From: Jyothsna Bavisetti <[email protected]> Sent: Wednesday, October 30, 2019 11:53 AM To: '[email protected]' <[email protected]> Subject: RE: Lucene index upgrade from 4.6 to 8 facing issue Hi All, 1. After Upgrading Lucene from 4.6 to 8, facing issue in search process. 2.We are creating 5 different folder for indexing with different index id ( 5 folders from 5 different tables). During search process we will join all these data to display. After upgrading we are facing issue in search data. 3. When we are applying filter for different fields from different index_id. It is searching for only one field. 4. I am seeing difference in Join Query. JoinUtil.createJoinQuery(fromField, false, toField, Query, srch, ScoreMode.None); Query formation with different versions: Lucene 4.6.0: TermsQuery{field=case.id} fromQuery=+(history.attribute:SExtendedAttribute1) +history.modifiedBy:3ff0000000000000 (different parameter) Lucene 8.0.0: TermsQuery{field=case.id fromQuery=+(history.attribute:SExtendedAttribute1) +history.modifiedBy:3ff0000000000000} fromQuery=+(history.attribute:SExtendedAttribute1) +history.modifiedBy:3ff0000000000000 (different parameter is also visible.) Actual Filter Condition: [Filter: condition: (&(case.caseType in (Scase))(case.sourceName in (SDEDUPLICATE))(&(history.attribute in (SExtendedAttribute1))(history.modifiedBy eq 3ff0000000000000))) ] Please Suggest me , as new to the Lucene unable to predict it. Thank you. Thanks, Jyothsna -----Original Message----- From: Jyothsna Bavisetti Sent: Wednesday, October 2, 2019 2:49 AM To: [email protected] Subject: RE: Lucene index upgrade from 4.6 to 8 facing issue Hi Shawn, Any doc or links for re indexing process. We are using Lucene core 8.0.0. Thanks, Jyothsna -----Original Message----- From: Jyothsna Bavisetti Sent: Thursday, September 26, 2019 11:51 PM To: [email protected] Subject: RE: Lucene index upgrade from 4.6 to 8 facing issue Hi Shawn, Re-indexing is costly transaction in my use case as it takes more than three days. Please let me know if any work around? Thanks, Jyothsna -----Original Message----- From: Shawn Heisey <[email protected]> Sent: Thursday, September 26, 2019 11:35 PM To: [email protected] Subject: Re: Lucene index upgrade from 4.6 to 8 facing issue On 9/26/2019 11:41 AM, Jyothsna Bavisetti wrote: > I am trying to upgrade Lucene index from 4.6 to 8.0.0. When I'm trying > to upgrade tool using: > > java -cp lucene-core.jar:lucene-backward-codecs.jar \ > > org.apache.lucene.index.IndexUpgrader-delete-prior-commits \ <snip> > Please let me know any option other than reindexing. If you're upgrading more than one major version, you must reindex. Multiple major version upgrades have always been discouraged and never guaranteed to work, but now such upgrades are explicitly denied. When you used the IndexUpgrader from Lucene 6, the Lucene version was written into the index. The recorded version was preserved by the upgrader for version 7. When the index was subsequently read by version 8, it complained because the original index was not written by version 7 or later. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
