Apach Solr Exercise 1 Index the Techproducts Data step not working
Hello, I am trying to run the Solr Tutorial Exercise 1 Index Techproducts Data in Windows 10. I typed the exact same command following it link: https://solr.apache.org/guide/solr/latest/getting-started/tutorial-techprodu cts.html java -jar -Dc=techproducts -Dauto example\exampledocs\post.jar example\exampledocs\* But I always got the following error messages: Error: Could not find or load main class org.apache.solr.util.SimplePostTool. My Java CLASSPATH has been configured with solr-core-9.8.0.jar as following: CLASSPATH = C:\Solr\solr-9.4.0\dist\solr-core-9.4.0.jar I have googled many stack overflow answers but no luck. Does anyone know what is wrong with this error? Are there any other jar libraries that I need to configure in my CLASSPATH in order to run this command? For the first step, "Launch Solr in SolrCloud Model", in the above link was working very well. Why the same Windows command line doesn't work in my computer? Where is the library for org.apache.solr.util.SimplePostTool? Someone said that SimplePostTool was only used in Solr old version. Is that true? It is very hard to follow Solr command line to design Schema and indexing for Solr. Are there any GUI interface for client side to implement Solr server design? Thank you very much qizhi
Re: [JENKINS] Lucene » Lucene-Solr-repro - Build # 1164 - Still Failing!
I agree - all of it looks very strange indeed. Seems like some of these jobs were brought back from inactive state. Dawid On Fri, Nov 3, 2023 at 10:37 PM Chris Hostetter wrote: > > : I'm not even sure how it's possible but this build seems to be using > stale > : configuration (repo pointing at the commit that informs about project > split > : between Solr and Lucene). I've disabled the plan. > > This jenkins job stoped sending emails ~ March of 2021. > > There is a thread from March of 2022 where Smiley mentioned it > didn't survive the gradle migration, and suggested bring it back... > > > https://lists.apache.org/list?d...@solr.apache.org:gte=365d:reproduceJenkinsFailures.py > > > But around Oct 27, it started running again and sending emails ... possily > because of something going horribly wrong on the jenkins machines > (possibly related to the other git related failures that started happening > in other jobs recently?) > > > > -Hoss > http://www.lucidworks.com/ > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
Re: [JENKINS] Lucene » Lucene-Solr-repro - Build # 1164 - Still Failing!
: I'm not even sure how it's possible but this build seems to be using stale : configuration (repo pointing at the commit that informs about project split : between Solr and Lucene). I've disabled the plan. This jenkins job stoped sending emails ~ March of 2021. There is a thread from March of 2022 where Smiley mentioned it didn't survive the gradle migration, and suggested bring it back... https://lists.apache.org/list?d...@solr.apache.org:gte=365d:reproduceJenkinsFailures.py But around Oct 27, it started running again and sending emails ... possily because of something going horribly wrong on the jenkins machines (possibly related to the other git related failures that started happening in other jobs recently?) -Hoss http://www.lucidworks.com/ - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: [JENKINS] Lucene » Lucene-Solr-repro - Build # 1164 - Still Failing!
I'm not even sure how it's possible but this build seems to be using stale configuration (repo pointing at the commit that informs about project split between Solr and Lucene). I've disabled the plan. Dawid On Fri, Nov 3, 2023 at 10:17 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Solr-repro/1164/ > > [...truncated 40 lines...] > > - > To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org > For additional commands, e-mail: builds-h...@lucene.apache.org
How can I get Apache Lucene demo web application working in Windows 10?
Hello,
I am new for Apache Lucene. I am trying to follow the Apache Lucene link,
https://lucene.apache.org/core/2_9_4/demo3.html to build up a demo web
application under Windows 10. I have installed the Tomcat web server and
successfully got it running. However, when I ran the following command line
in CMD:
java org.apache.lucene.demo.IndexHTML -create -index {index-dir}
..
It always showed the error: "could not find or load main class
org.apache.lucene.demo.IndexHTML caused by java.lang.ClassNotFoundException:
org.apache.lucene.demo.IndexHTML".
My Java CLASSPATH has been configured, and I was able to run IndexFiles
under Windows 10:
java org.apache.lucene.demo.IndexFiles -docs
C:/rootpath/chidpath/src
It is very strange as my IndexFiles can be run under Windows 10 without
error. Why can IndexHTML not be run with the same CLASSPATH setting? Does
anyone know how to run an Apache Lucene web application in Windows 10
environment?
Thanks
qizhi
Re: Bump minimum Java version requirement to 21
Hi, I had another idea: Why not release main as 10.0.0 *NOW* and create branch_10x (with Java 17) minimum, stop working on 9.x, and move main branch to 21? I would be happy to remove the MmapByteBuffer directory in Java 18. Unfortunately in Java 21 we still need a hack top compile the MemorySegment classes because of the preview flag. And for the incubator we also need the APIJAR files. But we can do this then without MR-JAR unless we need a new version for Java 22, 23 of vectors. My idea would be to patch in the api JAR during compile of "main" sourceset classes. Uwe Am 03.11.2023 um 13:20 schrieb Chris Hegarty: Hi, I would like to start the discussion and gather feedback on bumping the minimum Java version requirement to 21. I have no particular timeline in mind, but these kinda bumps often require dependency updates [*], small code refactorings, etc, and can take some time to plan and execute. It's best to at least have a plan for when, rather than if! Any bump would of course be limited to the _main_ branch, and therefore targeting a major Lucene release (no changes to branches targeting minor patch releases). I'm sure subscribers to this list are already familiar with the various goodies that have been added between Java 17 and 21, so I'll not enumerate them here, but rather callout just two particular benefits that I think are significant to the Lucene project. 1) Put a lower bound on the number of memory segment mmap and Panama Vector similarity implementations that we need to carry. This not only reduces maintenance cost, but avoids additional consideration and experimentation for performance improvements. 2) Support for half float, Float::float16ToFloat and Float::floatToFloat16, which will likely be beneficial in several places. More concretely, and somewhat orthogonal to the discussion of when, I would like to create a meta-issue capturing the prerequisites to a version bump. Your thoughts, comments, and feedback are very much welcome. -Chris. [*] we need at least an ECJ JDT dependency update, that supports Java 21, https://www.eclipse.org/lists/eclipse-dev/msg12203.html - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org -- Uwe Schindler Achterdiek 19, D-28357 Bremen https://www.thetaphi.de eMail: u...@thetaphi.de - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Bump minimum Java version requirement to 21
Hi, I would like to start the discussion and gather feedback on bumping the minimum Java version requirement to 21. I have no particular timeline in mind, but these kinda bumps often require dependency updates [*], small code refactorings, etc, and can take some time to plan and execute. It's best to at least have a plan for when, rather than if! Any bump would of course be limited to the _main_ branch, and therefore targeting a major Lucene release (no changes to branches targeting minor patch releases). I'm sure subscribers to this list are already familiar with the various goodies that have been added between Java 17 and 21, so I'll not enumerate them here, but rather callout just two particular benefits that I think are significant to the Lucene project. 1) Put a lower bound on the number of memory segment mmap and Panama Vector similarity implementations that we need to carry. This not only reduces maintenance cost, but avoids additional consideration and experimentation for performance improvements. 2) Support for half float, Float::float16ToFloat and Float::floatToFloat16, which will likely be beneficial in several places. More concretely, and somewhat orthogonal to the discussion of when, I would like to create a meta-issue capturing the prerequisites to a version bump. Your thoughts, comments, and feedback are very much welcome. -Chris. [*] we need at least an ECJ JDT dependency update, that supports Java 21, https://www.eclipse.org/lists/eclipse-dev/msg12203.html - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
