THX!
-Ursprüngliche Nachricht-
Von: Walter Underwood [mailto:wun...@wunderwood.org]
Gesendet: Donnerstag, 18. Januar 2018 08:27
An: solr-user@lucene.apache.org
Betreff: Re: Guideline on when a field absolutely needs to be stored?
There is a nice table for all of the field options.
There is a nice table for all of the field options.
https://lucene.apache.org/solr/guide/7_2/field-properties-by-use-case.html
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 17, 2018, at 11:23 PM, Clemens Wyss DEV wrote:
Kind of "basic question" ... Am I right, that the only real reason to store a
field (stored="true") is when I want to fetch the "originating value" from
documents returned?
What about
geo-location-fields?
Any other reason/(search-)function requiring a field being stored?
Thx
Clemens
Hi Joel, thanks for your follow-up!
Indeed, that's my experience as well - that the export handler streams
data fast enough. Though now that you mention batches, I'm curious if
that batch size is configurable or something like that.
The higher level issue is that I need to show results to the
If the document routing can be arranged such that the children and the
parent are always co-located in the same shard, and share an identifier,
the graph query can pull back the parent plus any arbitrary number of
"children" that have been added at any time in any order. In this scheme
"children"
So is there any way to solve the above problem?
On Jan 18, 2018 1:31 AM, "Mikhail Khludnev" wrote:
> sure
>
> On Wed, Jan 17, 2018 at 9:39 PM, Aashish Agarwal
> wrote:
>
> > Hello,
> > I tried to use block join query feature in solr 4.6.0. My data is in
>
It's been a while since I did it, but I'm pretty sure that when I indexed
polygons a couple years ago, I just sent WKT text for the field value... I
think i do recall some niggle where there was some slight mismatch in wkt
accepted by the javascript library I wanted to use and solr. (One was
Deepak
Would you like to write your post again without asterisks? Include the
asterisks which are necessary to the query of course.
Rick
On January 17, 2018 1:10:28 PM EST, Deepak Goel wrote:
>*Hello*
>
>*In Solr Admin: I type the q parameter as - *
>
>*text_entry:**
>
>*It
Chris / Hoss
Thanks for the detailed explanation. Erick Erickson's explanation made
sense to me but it didn't explain the part why the fields are different for
'hello' vs '*:*' .
I had never paid much attention the parser part of query handling and so
far focused only on the field definitions. I
Hi Emir
I’ve been following one of the only examples I could find on how to index a
POLYGON, which does specify the field as multiValued:
Configuration: schema.xml
Index a polygon (JavaScript syntax around WKT):
{"id":"1", "geo_rpt":
"POLYGON((30 10, 10 20, 20 40, 40 40, 30 10))”}
Indexing
sure
On Wed, Jan 17, 2018 at 9:39 PM, Aashish Agarwal
wrote:
> Hello,
> I tried to use block join query feature in solr 4.6.0. My data is in
> database but since 4.6 does not support DIH with child=true, so I created
> the csv in order list of child followed by parent.
> I
Hello,
It should be something like
{!parent ... score=total}+description:support +exp:[3 TO 7] {!func}exp
On Wed, Jan 17, 2018 at 3:05 PM, Prathyusha Kondeti wrote:
> Hi,
> I have the following indexed documents
> {
>"id":"data1",
>"isParent":"1",
>
I'm not sure I understand the issue fully. From a streaming standpoint, you
get real streamed data from the /export handler. When you use the export
handler the bitset for the search results is materialized in memory, but
all result are sorted/streamed in batches. This allows the exported handler
Hello Steve,
Sorry to disturb, the issue was due to custom tokenizer that I used. Since
that was not storing offset so term vector was not working.
Its resolved now.
On Jan 17, 2018 11:06 PM, "Steve Rowe" wrote:
> Hi Aashish,
>
> Which version of Solr are you using?
>
>
*Hello*
*In Solr Admin: I type the q parameter as - *
*text_entry:**
*It gives the following exception (In the schema I do see a field as
text_entry):*
{ "responseHeader":{ "zkConnected":true, "status":400, "QTime":2, "params":{
"q":"text_entry:*", "_":"1516190134181"}}, "error":{ "metadata":[
UNSUBSCRIBE
On Wed, Jan 17, 2018 at 10:19 AM, David M Giannone
wrote:
>
>
>
>
> Sent via the Samsung Galaxy S® 6, an AT 4G LTE smartphone
>
>
> Original message
> From: Selvam Raman
> Date: 1/17/18 11:47 AM (GMT-05:00)
> To:
Hi Aashish,
Which version of Solr are you using?
Please share your configuration: highlighter and schema.
--
Steve
www.lucidworks.com
> On Jan 16, 2018, at 12:20 PM, Aashish Agarwal wrote:
>
> Hello,
>
> I am using solr highlighting feature on multivalued field
Sent via the Samsung Galaxy S® 6, an AT 4G LTE smartphone
Original message
From: Selvam Raman
Date: 1/17/18 11:47 AM (GMT-05:00)
To: solr-user@lucene.apache.org
Subject: [EXTERNAL] Highlighter is not working for wildcard query
Hi,
solr version 6.4.2
Query Parser
defType=edismax
On Wed, Jan 17, 2018 at 4:47 PM, Selvam Raman wrote:
> Hi,
>
> solr version 6.4.2
>
> hl.method = unified, hl.bs.type=Word, this setting working fine for normal
> queries but failed in wildcard queries.(tried other hl.bs.type parmeter
Hi,
solr version 6.4.2
hl.method = unified, hl.bs.type=Word, this setting working fine for normal
queries but failed in wildcard queries.(tried other hl.bs.type parmeter and
without hl.bs.type as well, highlighting not working for wildcard queries)
hl.method = original, this is working fine for
If you just want docs from both collections in the same results, create an
alias across the 2 collections.
https://lucene.apache.org/solr/guide/6_6/collections-api.html
On Thu, Jan 11, 2018 at 11:12 PM, Suman Saurabh
wrote:
> Try using solr streaming api.
>
Hi,
I have the following indexed documents
{
"id":"data1",
"isParent":"1",
"_childDocuments":[
{
"description":
"Benefit and Payroll consultant with HR team support ",
"isParent":"2",
"exp":2
},
{
"description":" ERP Avalon
On 1/17/2018 5:24 AM, Mark Sullivan wrote:
I am migrating a good number of cores over to the latest instance of solr
(well, 7.1.0) installed locally. It is working well, but my code is
occasionally sending requests to search or index an old field that was replaced
in the schema.
I see this
Thanks Erick!!!
With Warm Regards...
Sushil K. Tripathi
From: Erick Erickson
Sent: Tuesday, January 16, 2018 11:02 AM
To: solr-user
Subject: Re: modify number of Shard
If you're using the default compositeId routing then this will not
Hello,
I have some updates on this, but it's still not very clear for me how
to move forward.
The good news is, that between sources and decorators, data seems to
be really streamed. I hope I tested this the right way, by simply
adding a log message to ReducerStream saying "hey, I got this
I am migrating a good number of cores over to the latest instance of solr
(well, 7.1.0) installed locally. It is working well, but my code is
occasionally sending requests to search or index an old field that was replaced
in the schema.
I see this in the logging, but I can't determine which
Hi,
Can you share the output with debugQuery=true. Note that 3w means there are max
2 words between those two phrases.
Regards,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> On 15 Jan 2018, at
Hi Leila,
I haven’t been using spatial in a while and did not test this, but based on
error, it seems that multivalue is not supported for this field type. Can you
index a single MULTIPOLYGON? Why do you need to have multiple values? Can you
flat your geometry to a single MULTIPOLYGON or
28 matches
Mail list logo