Indeed! Now it works for me too. JSON Facets seems powerful, but not
friendly to me.
Yonik, thanks for example!
Xavi,
I took json docs from http://yonik.com/solr-nested-objects/ and just
doubled book2_c3
Here is what I have with json.facet={catz: {type:terms,field:cat_s, facet:{
Hi Roland,
is a boolean parameter already supported by the
AnalyzingInfixLookup strategy.
At a Lucene level is parameter for the Lookup method.
At a Solr level is exposed through the configuration :
*suggest.allTermsRequired*
Anyway the default configuration is *True*, so it is weird you get
Can you confirm that the indexes *are* in place on disk before you shut
down? Whilst it may seem like indexes are being removed, this would seem
extremely unlikely, and the explanation is likely something else.
Try looking at your index files, post some content, commit, look again
at your index
Hi,
When I query q=*:* I can't get child documents back, Below is
configuration I am using for child Document to index in solr.
Am I missing something?
note: child document are using dynamic fields.
SolrInputDocument childDoc = new SolrInputDocument();
childDoc.addfield("index_l", 2);
When I query using solr admin page. I can see the parent document there
in results, but now child document.
On 23/11/15 12:24, Alexandre Rafalovitch wrote:
Do you get a parent doc? If not, maybe you forgot to commit the whole lot.
On 23 Nov 2015 6:42 am, "Novin" wrote:
Do you get a parent doc? If not, maybe you forgot to commit the whole lot.
On 23 Nov 2015 6:42 am, "Novin" wrote:
> Hi,
>
> When I query q=*:* I can't get child documents back, Below is
> configuration I am using for child Document to index in solr.
>
> Am I missing something?
Caused by: org.apache.solr.client.solrj.SolrServerException:
java.lang.IllegalStateException: Connection pool shut down
org.apache.solr.client.solrj.SolrServerException:
java.util.concurrent.RejectedExecutionException: Task
Yes. Hard commit using SolrJ 4.10.4 client with UpdateResponse.commit() which
defaults to waitFlush=true and waitSearcher=true
We reverted back to Solr 4.7 for the time being, which is a pity as we really
benefitted from the concurrent commit fix.
> On 17 Nov 2015, at 18:00, Erick Erickson
hello everyone
Caused by: org.apache.solr.client.solrj.SolrServerException:
java.lang.IllegalStateException: Connection pool shut down
how to solve this problem
Thanks
Regards
soledede_w...@ehsy.com
Could somebody please give schema example for creating child document?
On 23/11/15 12:57, Novin wrote:
When I query using solr admin page. I can see the parent document
there in results, but now child document.
On 23/11/15 12:24, Alexandre Rafalovitch wrote:
Do you get a parent doc? If not,
FWIW
I am getting fairly consistent results that if I follow the SOLR-8326 procedure
just up through the step of "solr-5.3.1/bin/solr start -e cloud -z
localhost:2181": if I then stop just one node (either "./solr stop -p 7574" or
"./solr stop -p 8983") and then restart that same node (using
To restart solr, you should instead use something like:
bin/solr start -c -p 8983 -s "example/cloud/node1/solr" -z localhost:2181
or
bin/solr start -c -p 7574 -s "example/cloud/node2/solr" -z localhost:2181
I've seen others report the same exception but never ran into this one
myself. Let me try
Yes, I see the same issue. I'll update the JIRA and drill down. Thanks.
On Mon, Nov 23, 2015 at 4:18 PM, Anshum Gupta
wrote:
> To restart solr, you should instead use something like:
> bin/solr start -c -p 8983 -s "example/cloud/node1/solr" -z localhost:2181
> or
>
Hi Scott,
I've created a Jira issue for this, the code is SOLR-8334.
Regards,
Edwin
On 24 November 2015 at 00:36, Scott Stults <
sstu...@opensourceconnections.com> wrote:
> Edwin,
>
> Congrats on getting it to work! Would you please create a Jira issue for
> this and add the patch? You won't
: Subject: Solr 5.2 child documents
: References:
:
:
: In-Reply-To:
Edwin,
Congrats on getting it to work! Would you please create a Jira issue for
this and add the patch? You won't need the inline change comments -- a good
description in the ticket itself will work best.
k/r,
Scott
On Sun, Nov 22, 2015 at 10:13 PM, Zheng Lin Edwin Yeo
The backup/restore approach in SOLR-5750 and in solrcloud_manager is
really just that - copying the index files.
On backup, it saves your index directories, and on restore, it puts them
in the data dir, moves a pointer for the current index dir, and opens a
new searcher. Both are mostly just
Novin,
As it's stated here http://yonik.com/solr-nested-objects/ there is no
requirements for schema. Perhaps
http://blog.griddynamics.com/2013/09/solr-block-join-support.html might be
useful too.
I suppose LogUpdateProcessor messages might answer about the root cause of
your problem.
On Mon,
: You've been asked a couple of times by several people to explain your
: business needs (level higher than Solr itself). As it is, you are
: slowly getting deeper and deeper into Solr's internals, where there
: might be an easier question if we know what you are trying to achieve.
:
: It is
19 matches
Mail list logo