Hello, Rosa.
You can try to replace them to
org.apache.lucene.queryparser.classic.QueryParser
org.apache.lucene.queryparser.classic.ParseException
org.apache.lucene.search.IndexSearcher
Though, migrating from 2.9 to 7 might have high mileage.
On Tue, Oct 8, 2019 at 5:32 AM Rosa Margarita
ASF Jenkins Jobs also reconfigured.
I left the 8.2 Refguide job in the queue (I cloned it), not sure if that one is
still needed. All other jobs are 8.3 now.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
>
Policeman Jenkins builds and tests 8.3 for Windows and Linux.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Ishan Chattopadhyaya
> Sent: Tuesday, October 8, 2019 4:32 PM
> To: Lucene Dev ; Uwe
I was thinking about this some more. What if the release manager has (yet
another) step in which non-released intermediate versions are marked
as-such in CHANGES.txt, and furthermore the associated JIRA issues are
advanced in bulk to the Closed step. That step could include an a comment
about
I've cut the 8.3 branch. Please feel free to push in any bug fix. For
any feature, please let me know to see how we can accommodate it
safely.
I'm planning to get myself familiarized with what I need to do for the
ref guide release (simultaneously with the binary release). So, most
likely, I'll be
While using MiniSolrCloudCluster on another project with a solr.xml that
looks like the standard solr.xml, I ran into some problems.
The default solr.xml has a solrCloud element with these elements:
${host:}
${jetty.port:8983}
${hostContext:solr}
And MiniSolrCloudCluster.DEFAULT_CLOUD_SOLR_XML,
Why even "cluster mode" or "cloud mode"?
Solr, by default , should use the cluster mode. So in all our
documentation, we should use just "Solr" and it should refer to a
"cluster mode of Solr"
Wherever we don't have a "cluster mode" should be explicitly qualified
as "standalone Solr"
On Wed, Oct
Thanks Shawn for clarifying. I took the lead on seeing this one through.
I don't love the duplicity of a public issue & private issue -- separate
JIRA tracking numbers is confusing. The public issue, which I filed because
I was supposed too, seems of low value because it's merely a duplication of
