Re: SolrCloud is sick.

I guess this is also a bit normal with software that grows over the years. One could also say that one writes the current use cases and interesting future use cases for Solr in a document and designs from scratch new - taking only the good pieces out of the existing software. Of course there is

Re: SolrCloud is sick.

If Curator would make that easier and we’re doing major surgery anyway…. But yeah, a nifty, new, more modern tool isn’t going to magically help if the design is flawed. Or, if I’m putting my philosophical hat on, code doesn’t get gnarly intentionally. It gets gnarly because there are a bunch of

RE: Lucene index upgrade from 4.6 to 8 facing issue

Hi All, Please help me with below error: java.lang.IllegalStateException: unexpected docvalues type NONE for field 'case.id' (expected one of [BINARY, SORTED]). Re-index with correct docvalues type. at org.apache.lucene.index.DocValues.checkField(DocValues.java:317) at org.apache

Re: SolrCloud is sick.

Figuring out a better overall algorithmic & data structure design that's an order of magnitude improvement seems far more important than swapping out libraries. And I say this as a Curator fan and committer. ;) On Mon, Nov 4, 2019 at 11:44 AM Erick Erickson wrote: > Bram: > > Using Curator has

Re: Missing top level javadocs

+1 fantastic! ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Mon, Nov 4, 2019 at 10:45 AM Andrzej Białecki wrote: > +1, I think it’s an excellent idea. The check should also verify that the > comment not only exists but also that it’s not empty -

Re: SolrCloud is sick.

Bram: Using Curator has been proposed before. It would require significant refactoring b/c of how deeply entwined raw ZK is in the code. That said, if we’re going to do major surgery it may be the right time to consider it. Erick > On Nov 4, 2019, at 9:24 AM, Bram Van Dam wrote: > >> SolrClo

Re: Missing top level javadocs

+1, I think it’s an excellent idea. The check should also verify that the comment not only exists but also that it’s not empty - eg. there’s an IntelliJ template that creates an empty top-level javadoc. > On 4 Nov 2019, at 16:40, Bram Van Dam wrote: > > David Smiley mentioned this in the "Solr

Missing top level javadocs

David Smiley mentioned this in the "SolrCloud is sick" thread. Instead of hijacking that, I figured I'd start another thread. On 03/11/2019 05:32, David Smiley wrote: > requiring javadocs on all top level classes.  I think more javadocs and > code comments would be very helpful -- especially for

Re: SolrCloud is sick.

> SolrCloud is sick right now. The way low level Zookeeper is handeled On an unrelated project, I've stopped using "raw" ZK client access and have switched to Curator. The API is a fair bit easier to work with, and it results in less ugly code. I realize that this won't go very far in resolving mo

Re: dtd anomaly

This job is ran on every ant build on Jenkins so there is no problem. This task you mentioned does not even read that xml file, unless it's somehow misplaced in your build directory and detected as build.xml. We know that there is a bug with ant 1.10 but that was something else as far as I reme

Re: dtd anomaly

> the attempt here is to run the entire build from start to finish with no > errors Do you want to build lucene-java from source? git clone https://github.com/apache/lucene-solr.git && cd lucene-solr/lucene && ant If you are attempting something else

BadApple

With all the discussion about major how broken Solr is, I’m not sure what the value of these is at this point, but they’re quick to do so what the heck. I probably won’t be changing annotations until that discussion reaches a conclusion. although I’ll continue to send these out. Failure

Re: dtd anomaly

but using xml-maven-plugin i got the same error with maven as i did ant org.codehaus.mojo xml-maven-plugin 1.0.1 validate initialize transform

Re: dtd anomaly

having used xsl parsing in other projects to create HTML I am attempting to run the ant build script lucene/build.xml but the build errors out on lucene\src\main\xml\ENTITY_TermQuery.xml attempting to find the Unknown host www.bar.xyz

Re: [ANNOUNCE] Apache Solr 8.3.0 released

Hey Ishan, Somedays back it was announced that the foundation will majorly focus on HTML guides now and thus, 8.2 guide was released (which was said to be shorter than 8.0). C*an we expect Ref Guide 8.3 in coming days* or maybe is it not required? Asking because we are planning to upgrade to lates

RE: dtd anomaly

Hi, I am wondering what you are doing. If you run “ant documentation” from Solr’s or Lucene’s root folder, it should not even read those files – they are only relevant for the XML queryparser. Could it be that you have accidentally copied into some other folder where they are caught by some

dtd anomaly

here is a bug i cannot shake in when building lucene/site inside lucene/src/main/xml/ENTITY_TermQuery.xml http://www.bar.xyz/external";> http://www.bar.xyz/param";> using ant build.xml: OR maven pom.xml org.codehaus.

Proposal: Solr Security news-feed

Hi, I'm proposing to add security announcements RSS/Atom feed to the web site. We're in the process of migrating our web site to Git and in that same process we also change CMS from an ASF one to Pelican. The new site has built-in support for news posts as individual files and also RSS feeds of t

Re: SolrCloud is sick.

Martin, please don’t hijack a subject but start a new mail thread for a new topic. Jan Høydahl > 4. nov. 2019 kl. 01:00 skrev Martin Gainty : > >  > here is a bug i cannot shake in when building lucne/site > > inside lucene/src/main/xml/ENTITY_TermQuery.xml > > > > http://www.bar.xyz/exte