, but it has
a precision of 0, meaning it is only indexed once.
Upayavira
On Thu, Sep 24, 2015, at 03:00 AM, Ravi Solr wrote:
> Recently I installed 5.3.0 and started seeing weird exception which
> baffled
> me. Has anybody encountered such an issue ? The indexing was done via
> DIH,
Recently I installed 5.3.0 and started seeing weird exception which baffled
me. Has anybody encountered such an issue ? The indexing was done via DIH,
the field that is causing the issue is a TrieDateField defined as below
Looking at the following exceptions it feels like a wrong exception
Hi Hoss,
Thanks for replying. I have created a jira:
https://issues.apache.org/jira/browse/SOLR-5697
It contains the required configs (actually a shard) and a query parser
maven project. These illustrate the issue.
I had to omit the solr.war from the webapps of the shard as it exceeded the
upload
We are still hitting an issue with two cores, each having their own custom
query parser.
The problem in passing {!qparser} is that the custom query parser can
pretty much alter an input query into something that is not desirable for
the delete by query operation.
Is there any way of specifying
: We found out that:
:
: 1. this happens iff on two cores inside the same container there is a
: query parser defined via defType.
: 2. After removing index files on one of the cores, the delete by query
: works just fine. Right after restarting the container, the same query fails.
Hello!
We are hitting a really strange and nasty issue when trying to delete by
query and not when just adding documents. The exception says:
http://pastebin.com/B1x5dAF7
Any ideas as to what is going on?
The delete by query is referencing the unique field. The core's index does
not contain the
This exception is similar to what is talked about here:
https://gist.github.com/mbklein/6367133
http://irc.projecthydra.org/2013-08-28.html
We found out that:
1. this happens iff on two cores inside the same container there is a query
parser defined via defType.
2. After removing index files on
The solution (or workaround?) is to drop the defType from one of the cores
and use {!qparser} local param on every query, including the delete by
query. It would be really great, if this could be handled on the solr
config side only without involving the client changes.
On Mon, Feb 3, 2014 at
in context:
http://lucene.472066.n3.nabble.com/Query-OR-operator-triggers-weird-exception-tp4098605.html
Sent from the Solr - User mailing list archive at Nabble.com.
-
From: michael.boom
Sent: Thursday, October 31, 2013 7:31 AM
To: solr-user@lucene.apache.org
Subject: Query OR operator triggers weird exception
I run a set of queries using the AdminUI and some of them trigger a weird
error:
error: {
msg: org.apache.solr.client.solrj.SolrServerException
.472066.n3.nabble.com/Query-OR-operator-triggers-weird-exception-tp4098605p4098607.html
Sent from the Solr - User mailing list archive at Nabble.com.
this message in context:
http://lucene.472066.n3.nabble.com/Query-OR-operator-triggers-weird-exception-tp4098605p4098609.html
Sent from the Solr - User mailing list archive at Nabble.com.
in context:
http://lucene.472066.n3.nabble.com/Query-OR-operator-triggers-weird-exception-tp4098605p4098614.html
Sent from the Solr - User mailing list archive at Nabble.com.
13 matches
Mail list logo
