For me, these variants have worked ...
solrQuery.add("json.facet", "...");
solrQuery.setParam("json.facet", "...");
You get ...
QueryResponse.getResponse().get("facets");
SRK
On Thursday, January 5, 2017 1:19 PM, Jeffery Yuan
wrote:
Thanks for your response.
We definitely use solrQ
Hi,
I uploaded (upconfig) config (schema and solrconfig XMLs) to Zookeeper and then
linked (linkconfig) the confname to a collection name.
When I attempt to create a collection using the API like this
.../solr/admin/collections?action=CREATE&name=abc&numShards=1&collection.configName=abc
... it
59:00],detailLevel=9,prefixGridScanLevel=7))
SRK
On Thursday, November 24, 2016 9:02 PM, Alessandro Benedetti
wrote:
Hey Sandeep,
can you debug the query ( debugQuery=on) and show how the query is parsed ?
Cheers
On Thu, Nov 24, 2016 at 12:38 PM, Sandeep Khanzode <
sandeep_kha
something in the syntax.
SRK
On Thursday, November 24, 2016 11:16 PM, Sandeep Khanzode
wrote:
Hi All, Erick,
Please suggest. Would like to use the ComplexPhraseQueryParser for searching
text (with wildcard) that may contain special characters.
For example ...John* should match John V
. Doe
SRK
On Thursday, November 24, 2016 5:57 PM, Sandeep Khanzode
wrote:
Hi,
This is the typical TextField with ...
SRK
On Thursday, November 24, 2016 1:38 AM, Reth RM
wrote:
what is the fieldType of those records?
On Tue, Nov 22, 2016 at 4:18 AM
Z]'})
SRK
On Tuesday, November 22, 2016 9:41 PM, Erick Erickson
wrote:
_How_ does it "not work"? You haven't told us what you expect .vs.
what you get back.
Plus a sample doc that that violates your expectations (just the
dateRange field) would
also help.
Best,
Eri
Hi,
This is the typical TextField with ...
SRK
On Thursday, November 24, 2016 1:38 AM, Reth RM
wrote:
what is the fieldType of those records?
On Tue, Nov 22, 2016 at 4:18 AM, Sandeep Khanzode
wrote:
Hi Erick,
I gave this a try.
These are my results
Hi,
I have a simple query that should intersect with dateRange1 and NOT be
contained within dateRange2. I have tried the following options:
WORKS:
+{!field f=dateRange1 op=Intersects v='[2016-11-22T12:01:00Z TO
2016-11-22T13:59:00Z]'} +(*:* -{!field f=dateRange2 op=Contains
v='[2016-11-22T12:01
r=true}name:"John D S*" ... fetches that record.
SRK
On Sunday, November 13, 2016 7:43 AM, Erick Erickson
wrote:
Right, for that kind of use case you want complexPhraseQueryParser,
see:
https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-ComplexPhraseQu
l be pretty good though.
In all this sounds like an XY problem, what's the use-case you're
trying to solve?
Best,
Erick
On Thu, Nov 10, 2016 at 10:11 PM, Sandeep Khanzode
wrote:
> Hi Erick, Reth,
>
> The 'a\ b*' as well as the q.op=AND approach worked (successfu
i.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-ComplexPhraseQueryParser
>
> On Thu, Nov 10, 2016 at 11:40 AM, Sandeep Khanzode <
> sandeep_khanz...@yahoo.com.invalid> wrote:
>
>> Hi,
>> How does a search like abc* work in StrField. Since the entire thi
Hi,
How does a search like abc* work in StrField. Since the entire thing is stored
as a single token, is it a type of a trie structure that allows such wildcard
matching?
How can searches with space like 'a b*' be executed for text fields (tokenized
on whitespace)? If we specify this type of qu
atures/fixes
> with OR, I think.
>
> Regards,
> Alex.
>
> Newsletter and resources for Solr beginners and intermediates:
> http://www.solr-start.com/
>
>
> On 26 September 2016 at 16:56, Sandeep Khanzode
> wrote:
>> Hi Alex,
>> It seems
:09 PM, Sandeep Khanzode
wrote:
Yup. That works. So does (*:* NOT ...)
Thanks, Alex. SRK
On Monday, September 26, 2016 3:03 PM, Alexandre Rafalovitch
wrote:
Try field2:value2 OR (*:* -field1=value1)
There is a magic in negative query syntax that breaks down when it
gets more
n the mailing list a bunch of
times, though the discussions are hard to find by title.
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 26 September 2016 at 16:06, Sandeep Khanzode
wrote:
> Hi,
> If I query for
> -field1=va
Hi,
If I query for
-field1=value1 ... I get, say, 100 records
and if I query for
field2:value2 ... I may get 200 records
I would assume that if I query for
-field1:value1 OR field2:value2
... I should get atleast 100 records (assuming they overlap, if not, upto 300
records). I am assuming tha
Thanks a lot, Bram. I will try that ... SRK
On Wednesday, September 21, 2016 11:57 AM, Bram Van Dam
wrote:
On 21/09/16 05:40, Sandeep Khanzode wrote:
> How can I specify JSON Facets in SolrJ? The below facet query for example ...
SolrQuery query = new SolrQuery();
query.
reference to this stuff is:
>
> https://cwiki.apache.org/confluence/display/solr/Local+Parameters+in+Queries
> But that page doesn't address the implications for when the syntax is a
> clause of a larger query instead of being the whole query (i.e. has "{!"...
> but but
Hello,
How can I specify JSON Facets in SolrJ? The below facet query for example ...
&json.facet={
facet1: {
type: query,
q: "field1:value1 AND field2:value2",
facet:
{
facet1sub1: {
type: query,
q: "{!field f=mydate op=Intersects}2016-09-08T08:00:00",
facet:
{
id:
{
type:
ead need to put it in the special "v"
local-param. e.g.:
-{!field f=schedule op=Contains v='[2016-08-26T12:00:12Z TO
2016-08-26T15:00:12Z]'}
On Tue, Sep 20, 2016 at 8:15 AM Sandeep Khanzode
wrote:
> This is what I get ...
> { "responseHeader": { "status
json", "_": "1474373612202" } }, "error": { "msg":
"Invalid Date in Date Math String:'[2016-08-26T12:00:12Z'", "code": 400 }}
SRK
On Tuesday, September 20, 2016 5:34 PM, David Smiley
wrote:
It should, I think...
For Solr 6.1.0
This works .. -{!field f=schedule op=Intersects}2016-08-26T12:00:56Z
This works .. {!field f=schedule op=Contains}[2016-08-26T12:00:12Z TO
2016-08-26T15:00:12Z]
Why does this not work?-{!field f=schedule op=Contains}[2016-08-26T12:00:12Z TO
2016-08-26T15:00:12Z]
SRK
Have been trying to understand this for a while ...How can I specify NOT clause
in the following query?{!field f=schedule op=Intersects}[2016-08-26T12:30:00Z
TO 2016-08-26T18:30:00Z]{!field f=schedule op=Contains}[2016-08-26T12:30:00Z TO
2016-08-26T18:30:00Z]Like, without LocalParams, we can spe
Hi, Can someone please reply to my query? Let me know if it is not
understandable. Thanks.
SRK
On Monday, September 19, 2016 6:00 PM, Sandeep Khanzode
wrote:
Hi,
Can I not query like this?
{!field f=schedule1 op=Contains}[1988-10-22T18:30:00Z TO *] AND
-schedule3:[1988-10-22T18:30
Hi,
Can I not query like this?
{!field f=schedule1 op=Contains}[1988-10-22T18:30:00Z TO *] AND
-schedule3:[1988-10-22T18:30:00Z TO *] AND -schedule2:[1988-10-22T18:30:00Z TO
*] I keep getting parsing and date math related errors.
If I change it to ...schedule1:[1988-10-22T18:30:00Z TO *] AND
-sc
Hi,
Can someone please direct me to some documentation that shows how to do this
... ?
I need to write a non-trivial function that will return a new custom (not in
schema) field but which is more complicated than a simple sum/avg/etc.
I want to create a function that looks at a few dateranges in
, Sandeep Khanzode
wrote:
Hello,
There are quite a few links that detail the difference between StrField and
TextField. Also links that explain that, even though the field is indexed, it
is not tokenized and stored as a single keyword, as can be verified by the
debug analysis on Solr admin and
Hello,
There are quite a few links that detail the difference between StrField and
TextField. Also links that explain that, even though the field is indexed, it
is not tokenized and stored as a single keyword, as can be verified by the
debug analysis on Solr admin and CURL debugQuery options.
Wh
28 matches
Mail list logo
