Bringing attention to this thread again.
Now that Lucene has some experience after the migration and with using Issues,
labels etc, I'd like to discuss whether we'd want to copy the Lucene approach
or do something different.
I'm not frequenting the Lucene issue tracker much, and am not either
Hi, I got the issue in Solrj upgrade.
Nifi 1.23.2 or 1.24.0 uses jetty-http 9.4.51 jar where as Solrj 9.4 needs
jetty-http 10.17. It means Solrj 9.x is not compatible with nifi 1.24.0.
Nifi 2.0.0-M has 10,x version of jetty. But this uses java 21 and lot of
methods are deprecated. So its not a
Hi,
Got some initial (positive) feedback on the auto-categorization PR and plan to
merge on Thursday, giving you some more time to review. I feel I have not 100%
nailed perfect labels. Obviously we can't auto label things like feature/bug,
or versions, so this is only a "category". Ideally
This is really a discussion for the users@ list, but you have to check all your
transivite dependencies for conflicts.
Here is a helpful article:
https://www.javaadvent.com/2020/12/how-to-debug-dependency-conflicts-in-maven-and-gradle.html
Jan
> 8. jan. 2024 kl. 18:08 skrev Subhasis Patra
> :
Any further thoughts on this?
I'd like to proceed with the PR for SOLR-16962 [1], which I've updated
with a fix to address now-once-again-relevant SOLR-6537 [2] (at
whatever point SOLR-16962 made it impossible to configure an external
tlog, SOLR-6537 (cleanup/deletion of external tlog) became
Thank you for your response.
We don’t have any issue when Solrj is part of other services. The issue is
specific to nifi. Is nifi using some different version of jetty that is
conflicting with the jetty Solrj is using?
I don’t have any jetty in my pom, the jeety jars are getting pulled as part
Check the class path of your application, whether it already has a dependency
on Jetty. If so, you need to pick one version so you don’t get multiple
versions of jetty on the class path.
If you use maven you can run “mvn dependency:tree” or similar to see them all.
Jan Høydahl
> 8. jan. 2024
Awesome, thanks for volunteering Raghavan!
Anyone have thoughts on scheduling? Absent other strong opinions, maybe we
could aim for the week of Monday the 15th through Friday the 19th and pick
a day/time in that range?
Best,
Jason
On Sun, Jan 7, 2024 at 1:27 AM raghavan m wrote:
> Happy New
