Solr version:4.6.1
On Sat, Nov 15, 2014 at 12:24 PM, Jeon Woosung jeonwoos...@gmail.com
wrote:
Could you let me know version of the solr?
On Sat, Nov 15, 2014 at 5:05 AM, Suchi Amalapurapu su...@bloomreach.com
wrote:
Hi
Getting the following exception when using fl renaming with unique
I see the same issue on 4.10.1.
I’ll open a JIRA if I don’t see one.
I guess the best immediate work around is to copy the unique field, and use
that field for renaming?
On Nov 15, 2014, at 3:18 AM, Suchi Amalapurapu su...@bloomreach.com wrote:
Solr version:4.6.1
On Sat, Nov 15, 2014 at
https://issues.apache.org/jira/browse/SOLR-6744 created.
And hopefully correctly, since that’s my first.
On Nov 15, 2014, at 9:12 AM, Garth Grimm
garthgr...@averyranchconsulting.commailto:garthgr...@averyranchconsulting.com
wrote:
I see the same issue on 4.10.1.
I’ll open a JIRA if I don’t
I guess that I caused by shard which return renamed field.
following code is source code of solr 4.6
===
986:if ((sreq.purpose ShardRequest.PURPOSE_GET_FIELDS) != 0) {
987: boolean
Am facing issue in running junit after 'svn up', junit works well without
any issue with a fresh trunk checkout. Only difference between fresh and
updated is that the earlier was once launched solr in cloud mode. There is
no issue in running through ant test -Dtestcase.
Following are the log
On 11/14/2014 10:32 PM, Anurag Sharma wrote:
Also like know, is this the only IRC or there are other's as well like solr
dev, lucene dev etc
The freenode channels #solr and #solr-dev exist specifically for Solr.
End users should keep their questions in #solr, because #solr-dev is for
Hi All,
How do I index complex JSON data in SOLR? For example,
{prices:[{state:CA, price:101.0}, {state:NJ,
price:102.0},{state:CO, price:102.0}]}
It's simple in ElasticSearch, but in SOLR it always reports the following
error:
Error parsing JSON field value. Unexpected OBJECT_START
Thanks,
It's simple in Elasticsearch, but what you actually get is a single
document and all it's children data ({state, price}) entries are
joined together behind the scenes into the multivalued fields. Which
may or may not be an issue for you.
For Solr, nested documents need to be parent/child separate
Thanks Alex. I take a look at the approach of transforming JSON document
before mapping it to the Solr schema at
http://lucidworks.com/blog/indexing-custom-json-data/ .
It's a walk-around. But in my case, if every state has its own price,
the number of documents needs to be indexed will
The first link shows how to create children with specific content, but
you need to use _childDocuments_:... explicitly instead of the
prices: and perhaps add type: price or some such to differentiate
record types.
But I am not quite following why you say it will increase 50 times. By
comparison
Assume that we are selling a product online to 50 states in the USA. But
each state has its own price. ALthough the base product information is the
same, the index size will increase 50 times if we index that way.
The usage is similar as searching a product; but based on the location of
the
It sounds to me that you are not actually searching on the state or
price. So, does it make sense to store it in Solr? Maybe it should
stay in external database and you merge it. Or store (not index) that
json as pure text field and parse what you need out of it manually, as
you would with
You can take 4.* of Solr and just apply my fix.
Store JSON stringified into a string field (make sure the field name ends
in _json). Then you can output with: wt=jsonjson.fsuffix=_json
OK?
Use SOLR-4685.
On Sat, Nov 15, 2014 at 5:07 PM, Alexandre Rafalovitch arafa...@gmail.com
wrote:
It
Thanks a lot Shawn for the detailed explanation. The wiki is also very
helpful. Any recommended client like pidgin, adium etc. especially for
windows.
On Sat, Nov 15, 2014 at 11:26 PM, Shawn Heisey apa...@elyograg.org wrote:
On 11/14/2014 10:32 PM, Anurag Sharma wrote:
Also like know, is this
Thanks Alex and William for the suggestions. I'll try out the approach
storing the JSON string.
On Sat, Nov 15, 2014 at 5:27 PM, William Bell billnb...@gmail.com wrote:
You can take 4.* of Solr and just apply my fix.
Store JSON stringified into a string field (make sure the field name ends
You could implement a custom highlighter for that field. Otherwise, you are
requesting a feature that does not exist in Solr today. The fl parameter
specifies fields to return, not portions of fields.
-- Jack Krupansky
-Original Message-
From: kumar
Sent: Thursday, November 13, 2014
16 matches
Mail list logo
