I'm getting a SyntaxError which I do not understand when I execute a block join
parent query. I'm running Solr5.2.1, with 2 shards. The problem appears to be
in that portion of the query that filters the child document. Any insight as to
where I made the error is greatly appreciated.
This quer
... ... "(" ... "*" ... "^" ...
... ... ... ... ...
... "[" ... "{" ... ... ...
400
- Original Message -
From: "Mikhail Khludnev"
To: "solr-user"
Sent: Wednesday, March 23, 2016 5:02:29 PM
Sub
"language":"en"},
{
"documentKind":"TestParent",
"uri":"https://ping/pong/testparent2";,
"view_uri":"https://ping/pong/testparent2";,
"id":"Tes
rmer. And
come back with response.
On Thu, Mar 24, 2016 at 3:23 PM, Charles Sanders
wrote:
> Ah yes. Thank you. Made the correction and I do not get the SyntaxError.
> However, it does not apply the child filter. The query should return only
> TestParent4. But it is returning
Hello,
Multivalued fields are controlled by the schema. You need to define your field
in the schema file as 'not' a multivalue field. Here are a couple of examples
of field definitions, one multivalued, the other not.
If you do not explicitly define your field, then solr will use default
Not able to get the DocTransformer [explain] to work in Solr 5. I'm sure I'm
doing something wrong. But I'm following the example in the documentation.
https://cwiki.apache.org/confluence/display/solr/Transforming+Result+Documents
Other transformers ( [docid] and [shard] ) are working as expect
Using the Query Elevation Component in solr 4.8 and the elevateIds parameter to
force 3 documents to the top of the query results. Query and results included
below. In the results, you will see only one document of the three is in the
query results. It is the first document and it is marked as e
pache.org
Sent: Friday, February 6, 2015 2:54:20 PM
Subject: Re: Query Elevation Component only elevates one document in elevateIds
list
Try sending the elevateIds as a comma delimited list.
Joel Bernstein
Search Engineer at Heliosearch
On Fri, Feb 6, 2015 at 2:17 PM, Charles Sanders wrote:
&g
I'm seeing a problem with the LengthFilter. It appears to work fine until I
increase the max value above 254. At the point it stops removing the very large
token from the stream. As a result I get the error:
java.lang.IllegalArgumentException: Document contains at least one immense
term.. U
3456789012345678901234567890123456789012345678901234567890"
],
"_version_": 1501249997589446700,
"timestamp": "2015-05-15T15:26:05.205Z",
"language": "en"
}
]
}
}
- Original Message -
From: "Shawn Heisey"
To: so
-- Jack Krupansky
On Fri, May 15, 2015 at 11:38 AM, Charles Sanders
wrote:
> Yes, that is what I am seeing. Looking in the code myself, I see no reason
> for this behavior. That is why I assumed I was doing something very wrong.
>
> Below I have included an example. I set th
345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345
portal_package:678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901
Shawn,
Thanks a bunch for working with me on this.
I have deleted all records from my index. Stopped solr. Made the schema changes
as requested. Started solr. Then insert the one test record. Then search. Still
see the same results. No portal_package is not the unique key, its uri. Which
is a
456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"
],
"_ve
string anyway, you
could just use the keyword tokenizer.
-- Jack Krupansky
On Fri, May 15, 2015 at 4:06 PM, Charles Sanders
wrote:
> Shawn,
> Thanks a bunch for working with me on this.
>
> I have deleted all records from my index. Stopped solr. Made the schema
> chang
s it as an unanalyzed
string field? You need to delete the index and start over if you want to
change the field types like that.
-- Jack Krupansky
On Mon, May 18, 2015 at 8:33 AM, Charles Sanders
wrote:
> Jack,
> Thanks for the information. If I understand this correctly, the White
> s
I'm running Solr 4.8 in a distributed environment (2 shards). I have added the
spellcheck component to my request handler. In my test system, which is not
distributed, it works. But when I move it to the Dev box, which is distributed,
2 shards, it is not working. Is there something additional I
",
"code":500}}
- Original Message -
From: "Erick Erickson"
To: solr-user@lucene.apache.org
Sent: Tuesday, December 30, 2014 6:07:13 PM
Subject: Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
Did you try the shards parameter? See:
ht
Got it. Thanks for your help everyone.
- Original Message -
From: "Shawn Heisey"
To: solr-user@lucene.apache.org
Sent: Tuesday, December 30, 2014 7:16:59 PM
Subject: Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
On 12/30/2014 5:03 PM, Charles San
I'm running solr 4.8. On my test system I ran the query
http://localhost:/solr/collection1/select?q=*:*&fq=-hasPublishedRevision:true&rows=100&fl=documentKind,
hasPublishedRevision&wt=json&indent=true
The results are as expected. It returns 59 documents of various documentKinds,
all having
ecember 31, 2014 12:56:02 PM
Subject: Re: Filter Queries Do Not Allow OR operator ??
On 12/31/2014 10:45 AM, Charles Sanders wrote:
> I'm running solr 4.8. On my test system I ran the query
> http://localhost:/solr/collection1/select?q=*:*&fq=-hasPublishedRevision:true
ds parameter? See:
https://cwiki.apache.org/confluence/display/solr/Spell+Checking#SpellChecking-DistributedSpellCheck
On Tue, Dec 30, 2014 at 2:20 PM, Charles Sanders wrote:
> I'm running Solr 4.8 in a distributed environment (2 shards). I have added
> the spellcheck component to m
Attempting to follow the documentation found here:
https://cwiki.apache.org/confluence/display/solr/Suggester
The example given in the documentation is not working. See below my
configuration. I only changed the field names to those in my schema. Can anyone
provide an example for this componen
you can please post more details about your documents -- ideally a full
set of all the documents in your index (using a small test index of
course) that may help to understand the results you are getting.
: Date: Thu, 22 Jan 2015 11:14:43 -0500 (EST)
: From: Charles Sanders
: Reply-T
Derrick,
This makes me think you do not have a default query field identified. Look in
your solrcong.xml file for the requesthandler you are calling and see if it has
the "df" parameter set. Should look something like:
text
Hope this helps!
- Original Message -
From: "Derrick Cui"
25 matches
Mail list logo
