Re: Solr index writing to s3

There is some experience on backup to s3 https://issues.apache.org/jira/browse/SOLR-9952 iirc, it lacks performance. Jörn, it's not a point, but literally s3 consistency might be enough, since s3 provides read-after-write for PUT and Lucene index writer is append-only. On Thu, Jan 17, 2019 at 10:1

Re: Content from EML files indexing from text/html (which is not clean) instead of text/plain

Y, I tracked this down within Solr. This is a feature, not a bug. I found a solution (set {{captureAttr}} to {{true}}): https://issues.apache.org/jira/browse/TIKA-2814?focusedCommentId=16745263&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16745263 Please, though,

Tokenizer violates TokenStream.reset() contract?

Hello, It seems that Tokenizer may violate the contract put forth by the TokenStream.reset function. Specifically, TokenStream.reset states: "*Resets this stream to a clean state. Stateful implementations must implement this method so that they can be reused, just as if they had been created fres

8.0.0-SNAPSHOT snapshot repo poms broken?

All, I recently tried to upgrade a project that relies on the snapshot repos[1], but maven wasn't able to pull lucene-highlighter, lucene-test-framework, lucene-memory, among a few others. However, maven was able to pull lucene-core and most other artifacts for 8.0.0-SNAPSHOT. I manually checke

Re: 8.0.0-SNAPSHOT snapshot repo poms broken?

User error..please ignore. On Thu, Jan 17, 2019 at 4:36 PM Tim Allison wrote: > > All, > I recently tried to upgrade a project that relies on the snapshot > repos[1], but maven wasn't able to pull lucene-highlighter, > lucene-test-framework, lucene-memory, among a few others. However, > ma

stats.field using Config API

Hi all, I am trying to set multiple stats.field parameters to get the min and max of multiple fields in one request. I am able do this by doing this in the URL stats.field=statsfield1&stats.field=statsfield2&stats.field=statsfield3 I would like to replicate this, but in the configoverlay.json fi

Error using collapse parser with /export

Hello, I am using SolrCloud on Solr 7.2.1. I get the NullPointerException in the Solr logs (in ExportWriter.java) when the /stream handler is invoked with a search() streaming expression with qt="/export" containing fq="{!collapse field=id_field sort="time desc"} (among other fq's. I tried elimina

[QA-search] About field setting

hi Can you use multiple query analyzers to search for or? Ex) Can you get synonyms to run before tokenzier? Ex)