Hi Yonik
I do actually encode it like q=titile:%237654321* (which is :
q=titile:#7654321*)
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-cannot-return-result-when-query-with-like-title-7654321-tp4253541p4253734.html
Sent from the Solr - User mailing list
The query is rather simple:
http://127.0.0.1:8080/solr/collection1/select?q=title:#7654321*
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-cannot-return-result-when-query-with-like-title-7654321-tp4253541p4253760.html
Sent from the Solr - User mailing list archive at
Hi Eric
Thank you for your reply.
I saw the admin/analyze page before.
The string "titile:#7654321" for index analysis hit ST with "7654321"
.(That means # is not indexed)
The string "title:#7654321*" for query analysis hit ST(Standard
Tokenizer) with "7654321" as well.
Hi Shawn
Thank you for you reply.
But The weird place is why it can return result by condition
(q=title:#7654321) and condition (q=title:7654321*) or (q=title:7654321).
From your assumption, the condition (q=title:#7654321) should not return
result as well.(But it does return hit
Hi Shawn
Your information is very important. It can explain the phenomena I met.
Do you know from where I can get the related document Or subject about
what you said?
I want to have a deep understand to this.
Thank you Very much!
Diyun
--
View this message in context:
Hi Ahmet
Thank you for your reply.
The title type is "text_general" and it uses Standard Tokenizer.
The string "titile:#7654321" by index analysis hit ST with "7654321"
.(That means # is not indexed)
The string "title:#7654321*" by query analysis hit ST(Standard
Tokenizer) with
Hi guys
I have a document index with title:#7654321.
Then when I query it with q=title:#7654321, it works
When I query it with q=title:#7654321*, it cannot work,it cannot hit any
result.
Then I remove # and query it with q=title:7654321*, it works again.
I tried
Following the guide:
https://cwiki.apache.org/confluence/display/solr/ZooKeeper+Access+Control
Setting solr.xml and solr.in.sh with :
...
...
org.apache.solr.common.cloud.VMParamsSingleSetCredentialsDigestZkCredentialsProvider
Thank you Lance for you experience share. That will be useful to me.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr4-4-or-zookeeper-3-4-5-do-not-support-too-many-collections-more-than-600-tp4088689p4089212.html
Sent from the Solr - User mailing list archive at
Thank you Yago. That seems some strange. Do you know some official document
detail this? I really need more evidence to do dicision.I mean I need to
compare the two method and find out which have more advantages in terms of
performance and cost. And I will change my parameter to do more testing. I
I just found this option -Djute.maxbuffer in zookeeper admin document. But
it's a Unsafe Options. I can't really know what it mean. Maybe that will
bring some unstable problems? Does someone have some real practical
experiences when using this parameter? I will have at least 15K collections.
Or I
Thank you very much for your advice.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr4-4-or-zookeeper-3-4-5-do-not-support-too-many-collections-more-than-600-tp4088689p4089009.html
Sent from the Solr - User mailing list archive at Nabble.com.
Thank you Erick. It's very useful to me. I have already started to merge logs
of collections to 15 collections. but there's another question. If I merge
1000 collections to 1 collection, to the new collection it will have about
20G data and about 30M records. In 1 solr server, I will create 15
*I have installed solr cloud with solr4.4 and zookeeper 3.4.5.
And I'm testing some requirements with 10k collections supporting in one
solr server.
When I post collection to solr
server(admin/collections?action=CREATEname=europetest${loopcnt}numShards=2replicationFactor=2maxShardsPerNode=2)
with
14 matches
Mail list logo