1. No it is with schema with some dynamic fields but facet fields are
proper field
2. No copy field is stored field all are set as stored=false
On Fri, Jun 23, 2017 at 10:21 PM Erick Erickson
wrote:
> OK, new collection.
>
> 1> With schemaless? When you add a document in schemaless mode, it
>
OK, new collection.
1> With schemaless? When you add a document in schemaless mode, it
makes some guesses that may not play nice later.
2> Are you storing the _destination_ of any copyField? Atomic updates
do odd things if you set stored="true" for fields that are
destinations for atomic updates,
No Shawn,
I download the latest solr again then run without installing by command
./bin/solr -c
after upload the fresh configset and create the new collection
Then create a single document in solr
after do atomic update
and the same error occurs again.
On Fri, Jun 23, 2017 at 7:53 PM Shawn Heisey
On 6/20/2017 11:01 PM, Aman Deep Singh wrote:
> If I am using docValues=false getting this exception
> java.lang.IllegalStateException: Type mismatch: isBlibliShipping was
> indexed with multiple values per document, use SORTED_SET instead at
> org.apache.solr.uninverting.FieldCacheImpl$SortedDocVa
Hi Shawn,
If I am using docValues=false getting this exception
java.lang.IllegalStateException: Type mismatch: isBlibliShipping was
indexed with multiple values per document, use SORTED_SET instead at
org.apache.solr.uninverting.FieldCacheImpl$SortedDocValuesCache.createValue(FieldCacheImpl.java:79
On 6/20/2017 12:07 AM, Aman Deep Singh wrote:
> Again the same problem started to occur and I haven't change any schema
> It's only coming to the Numeric data types only (tint,tdouble) and that too
> in group query only
> If I search with string field type it works fine.
>
> Steps which i have foll
Again the same problem started to occur and I haven't change any schema
It's only coming to the Numeric data types only (tint,tdouble) and that too
in group query only
If I search with string field type it works fine.
Steps which i have followed
1. drop the old collection
2. create the new
bq: Is their any roadmap to avoid the remanent data issue,
Not that I've ever heard of. Well, Uwe did show a process for adding
docValues to an existing index here:
http://lucene.472066.n3.nabble.com/Adding-Docvalues-to-a-Field-td4333503.html
but you can see what kinds of deep-level Lucene knowled
I tried to recreate the collection and its working fine,
But if i try to change the any field level value this error again comes
Is their any roadmap to avoid the remanent data issue, since every time you
change the field definition you need to delete the data directory or
recreate the collection.
bq: But I only changed the docvalues not the multivalued
It's the same issue. There is remnant metadata when you change whether
a field uses docValues or not. The error message can be ambiguous
depending on where the issue is encountered.
Best,
Erick
On Fri, Jun 16, 2017 at 9:28 AM, Aman Deep Si
But I only changed the docvalues not the multivalued ,
Anyway I will try to reproduce this by deleting the entire data directory
On 16-Jun-2017 9:52 PM, "Erick Erickson" wrote:
> bq: deleted entire index from the solr by delete by query command
>
> That's not what I meant. Either
> a> create an
bq: deleted entire index from the solr by delete by query command
That's not what I meant. Either
a> create an entirely new collection starting with the modified schema
or
b> shut down all your Solr instances. Go into each replica/core and
'rm -rf data'. Restart Solr.
That way you're absolutely s
Yes ,it was a new schema(new collection),and after that I change only
docvalues= true using schema api,but before changing the schema I have
deleted entire index from the solr by delete by query command using admin
gui.
On 16-Jun-2017 9:28 PM, "Erick Erickson" wrote:
My guess is you changed the
My guess is you changed the definition of the field from
multiValued="true" to "false" at some point. Even if you re-index all
docs, some of the metadata can still be present.
Did yo completely blow away the data? By that I mean remove the entire
data dir (i.e. the parent of the "index" directory)
Hi,
Facets are not working when i'm querying with group command
request-
facet.field=isBlibliShipping&facet=true&group.facet=true&group.field=productCode&group=true&indent=on&q=*:*&wt=json
Schema for facet field
It was throwing error stating
Type mismatch: isBlibliShipping was indexed with multi
15 matches
Mail list logo
