Breaking change in Lucene 4.8.0-beta00017 requires new Build/Release of Examine v4 (beta)

[jemayn]

trafficstars

Heya!

We are using Examine v4.0.0-beta-1 on a number of Umbraco 13 sites for facetting. With the latest release they bumped the Lucene.Net.Replicator version due to a security issue in the previous one. Along with the security issue they also apparently have a breaking change which makes searching throw errors.

This is the PR to Umbraco with the version update: https://github.com/umbraco/Umbraco-CMS/pull/17415

I think this is the issue with the change: https://github.com/apache/lucenenet/issues/408

[Shazwazza]

So we just need to rebuild the Examine beta release against the new Lucene beta and ship another package right?

[jemayn]

I don't think it's quite that simple, I had a quick look and it's a bit more involved than simply bumping the package version. There are a few locations that use the now removed SnapshotDirectoryTaxonomyWriter:

I had a quick look to see if it was a simple renaming, but they changed it into this SnapshotDirectoryTaxonomyIndexWriterFactory : https://github.com/apache/lucenenet/pull/847/files#diff-701133a10ee7bdd5365c112da105d17aadfa7e3cd51c999e80c2d667f2de6891R31

Which is not a simple rename:

I stopped digging at this point so am not entirely sure how large the chain of changes will be.

[Shazwazza]

Thanks @jemayn, I suppose I just meant, we need to recompile (fix breaking changes) for v4beta with the latest Lucene beta, and then ship a new release :)

I'll try to take a look tomorrow.

[marcoteodoro]

Hi @Shazwazza, this issue persists with version 4.0.0-beta.1, right? I was trying it on Umbraco 13.9.2, and I still see the same problems in the logs. Additionally, I'm unable to index or examine at all. @jemayn, maybe you can confirm this as well?

[Shazwazza]

There's been no updates to beta 4 release. Its something I'm working on to get it aligned with all new changes from v3. I've found several issues along the way that have been fixed along with introducing several breaking changes that we're needed. I still don't have an ETA for next beta4 release but hopefully soon. Then we'll have to add some compatibility shims back in.

v4 is a beta, and while several people are using it in prod, it does have some issues, especially if you are using it on azure with the synced directory settings enabled.