The time that init.d script waits before shutdown should be configurable
The 5 seconds is not enough to all my shards notify the shutdown and the
process ends with a kill command
I think that in solr.in.sh should exists a entry to configure the time to
wait before use a kill command
-
Can anyone help with this error? It’s not an issue with the WKT itself as I can
easily convert the spatial to java using the JTS api without error.
From: Michael Gangl
>
Date: Thursday, November 5, 2015 at 3:40 PM
To:
ehehe your request is kinda delicate :
1) I can't store the
payload at index time
2) Passing all the weights at query time is not an option
So you seem to exclude all the possible solutions ...
Anyway, just thinking loud, have you tried the edismax query parser and the
boost query feature?
1)
I raised a JIRA with this, SOLR-8257
-
Best regards
--
View this message in context:
http://lucene.472066.n3.nabble.com/DELETEREPLICA-command-shouldn-t-delete-de-last-replica-of-a-shard-tp4239054p4239139.html
Sent from the Solr - User mailing list archive at Nabble.com.
Susheel,
This is perfectly fine for simple use-cases and has the benefit that the
filterCache will help things stay nice and speedy. Apache ManifoldCF goes a
bit further and ties back to your authentication and authorization
mechanism:
Hi,
After I configure Authentication with Basic Authentication Plugin and
Authorization with Rule-Based Authorization Plugin, How can I prevent the
strangers from visiting my solr by browser? For example, if the stranger visit
the http://(my host):8983, the browser will pop up a window and
Has anyone written a sample xslt (and would like to share) that converts
output response xml of solr into its input format, to
repost/reindex it back?
Thanks
Hello,
I have a legacy Solr schema that I would like to update to take advantage of
DocValues. I understand that by adding "docValues=true" to some of my fields, I
can improve sorting/faceting performance. However, I have a couple of questions:
1.)Will Solr always take proper advantage of
bq: But if we are keeping the indexed=true, then docValues=true will STILL
use at least as much memory however efficient docValues are
themselves, right?
AFAIK, kinda. The big difference is that with docValues="false", you're
building these structures in the JVM whereas with docValues="true",
the
On Mon, Nov 9, 2015 at 12:06 PM, Alexandre Rafalovitch
wrote:
> Thank you Yonik.
>
> So I would probably advise then to "keep your indexed=true" and think
> about _adding_ docValues when there is a memory pressure or when there
> is clear performance issue for the
https://github.com/OpenSextant/SolrTextTagger/
We're using it for country tagging successfully.
On Wed, Nov 4, 2015 at 3:10 PM, Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> David Smiley had a place name and general tagging engine that for the life
> of me I can't find.
>
> It
Hello
I've been trying to index IMDB data from MySQL with no success yet. The
problem was with the data import handler. When I specify using of
"SqlEntityProcessor", DIH either totally skipped the row, or didn't start
importing at all, or the results are not searchable. I also tried setting
On Mon, Nov 9, 2015 at 10:55 AM, Demian Katz wrote:
> I understand that by adding "docValues=true" to some of my fields, I can
> improve sorting/faceting performance.
I don't think this is true in the general sense.
docValues are built at index-time, so what you will
Use an index-time (but not query time) synonym filter with a rule like:
Abd Allah,Abdallah
This will index the combined word in addition to the separate words.
-- Jack Krupansky
On Mon, Nov 9, 2015 at 4:48 AM, Mahmoud Almokadem
wrote:
> Hello,
>
> We are indexing
Thank you Yonik.
So I would probably advise then to "keep your indexed=true" and think
about _adding_ docValues when there is a memory pressure or when there
is clear performance issue for the ...specific... uses.
But if we are keeping the indexed=true, then docValues=true will STILL
use at
On 11/6/2015 8:39 PM, Yonik Seeley wrote:
> On Fri, Nov 6, 2015 at 10:20 PM, Shawn Heisey wrote:
>> Is there a decent API for getting uniqueKey?
> Not off the top of my head.
> I deeply regret making it configurable and not just using "id" ;-)
By poking around in the admin
I thought docValues were per segment, so the price of un-inversion was
effectively paid on each commit for all the segments, as opposed to
just the updated one.
I admit I also find the story around docValues to be very confusing at
the moment. Especially on the interplay with "indexed=false". It
On Mon, Nov 9, 2015 at 11:19 AM, Alexandre Rafalovitch
wrote:
> I thought docValues were per segment, so the price of un-inversion was
> effectively paid on each commit for all the segments, as opposed to
> just the updated one.
Both the field cache (i.e. uninverting indexed
Yago,
I think a JIRA has been raised for this. I'd encourage you to hunt it
down and make a patch.
Upayavira
On Mon, Nov 9, 2015, at 03:09 PM, Yago Riveiro wrote:
> The time that init.d script waits before shutdown should be configurable
>
> The 5 seconds is not enough to all my shards notify
Thanks Jack,
This is a good solution, but we have more combinations that I think can’t be
handled as synonyms like every word starts with ‘عبد’ ‘Abd’ and ‘أبو’ ‘Abo’.
When using Standard tokenizer on ‘أبو بكر’ ‘Abo Bakr’, It’ll be tokenised to
‘أبو’ and ‘بكر’ and the filters will be applied
http://lucidworks.com/blog/solr-suggester/
Wondering if anyone has uses these new techniques with a boost on
geodist() inverted? So the rows that get returned that are closest
need to come back first.
We are still using Edge Grams since we have not figured out how to
boost the results on geo
On Mon, Nov 9, 2015 at 6:55 PM, Demian Katz
wrote:
> I have a legacy Solr schema that I would like to update to take advantage
> of DocValues. I understand that by adding "docValues=true" to some of my
> fields, I can improve sorting/faceting performance.
Demian,
If
Have you looked at the Spatial extensions for Solr? If you are indexing
Lat/Lon along with your documents, you can compute the distance from the
origin & use that distance as one of the boost factors to affect the score.
Typically, use cases around that combine the geo score with other factors
as
Yeah we have that working today. But the issue is we want to use
http://lucidworks.com/blog/solr-suggester/
And you cannot do a boost with that right?
On Mon, Nov 9, 2015 at 12:41 PM, Sameer Maggon
wrote:
> Have you looked at the Spatial extensions for Solr? If you
Looking through the code and some example Suggesters, it seems that
theoretically, one can write a GeoSuggester and provide that as the Lookup
implementation (lookupimpl) that would factor in the geo score or extend
the SolrSuggestor to support spatial extensions in the same spirit as
"Filters"
Yonik,
I wonder is there a plan or a vision for something like
https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-reverse-nested-aggregation.html
under JSON facets?
Thanks
On Sun, Jun 14, 2015 at 4:02 AM, Yonik Seeley wrote:
> Hey
Hi,
I stuck in DIH...
full import is fine.
and delta import was also fine before I add deltaQuery and parentDeltaQuery
in 'auth' entity.
thank you for any help..
Hi,
Can anybody help me to resolve an issues with solr search relevancy.
Problem is that when somebody search "Bank", it displays some other
business related to this phrase.
For Eg it shows "Blood bank" and "Power bank" as the first results.
To resolve this, we implemented the proximity search at
Hi Dhanesh,
Several things you could try:
* when you are searching for "bank" you are actually searching for
tag/category and in your query you are boosting name 300 while tag is 3.
* you must not sort on premium content weight - you can either use boost
query clauses to prefer premium content
Hello
I followed Yonik's blog regarding faceting on child document and my curl
command is posted below:
curl http://localhost:8983/solr/movie_shard1_replica1/query -d '
q={!parent which="content_type:parent"}+movie&
json.facet={
movies:{
type:terms,
field:actor,
i use solr cloud.
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613p4239100.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Mon, Nov 9, 2015 at 7:30 PM, Yangrui Guo wrote:
> Just solved the problem by changing blockChildren:"content_type:children"
> to blockParent:"content_type:children".
Unless you're dealing with multiple levels, you may be using the wrong
content_type value.
That query
Just solved the problem by changing blockChildren:"content_type:children"
to blockParent:"content_type:children". Does Solrj support json faceting as
well?
Yangrui
On Mon, Nov 9, 2015 at 2:39 PM, Yangrui Guo wrote:
> Hello
>
> I followed Yonik's blog regarding faceting on
Hi Erick,
Thanks for your response.
You right my node running properly and the graph is green.
we solve with remove the data index in collection and reindex again.
Thanks
On Fri, Nov 6, 2015 at 11:02 PM, Erick Erickson
wrote:
> The host may be running well, but my bet
Hello,
We are indexing Arabic content and facing a problem for tokenizing multi
terms phrases like 'عبد الله' 'Abd Allah', so users will search for
'عبدالله' 'Abdallah' without space and need to get the results of 'عبد
الله' with space. We are using StandardTokenizer.
Is there any
To get answer for why 15, you can use field analysis for index/query and
see that "15%" is probably tokenized and as both 15 and 15%.
Emir
On 06.11.2015 20:22, Erick Erickson wrote:
I'm not sure what the question your asking is. You say
that you have debugged the query and the score for 15 is
I quote Emir and I would like to ask if the Norms are ignored or not.
If they are not ignored and 15 is one of the search tokens, I can expect an
high score for a doc containing "15" because the Norm value will be quite
high ( as the field contains basically exactly the query term).
Cheers
On 9
37 matches
Mail list logo