Alisa - sorry for not seeing this sooner, but I think Yonik is right… try 
adding `-format solr` to the command-line of bin/post.

Solr 5.5 is where the changed occurred to use a different end-point for JSON.

—
Erik Hatcher, Senior Solutions Architect
http://www.lucidworks.com <http://www.lucidworks.com/>



> On Mar 28, 2016, at 2:04 PM, Alisa Z. <prol...@mail.ru> wrote:
> 
> @Yonik, thank you for your response. 
> 
> I think that the issue is of a different kind because my upload used to work 
> well on Solr 5.3.1 and does not want to work on Solr 5.5.0 because of some 
> changes in dynamic schema recognition.  So maybe you could advise on 
> reconsidering the data model that I am using. 
> 
> I have the  type_s field serving as an indicator of different types of 
> parents and children. However, in my data model, siblings at one level could 
> be of different type/category, e.g.,:
> 
> ------------------------------------------------------------------------- 
> type_s: PARENT
> -------------------------------/---------------------------------------------------|--------------------------------------------\
> --------------------- type_s: child_type1 ------------------------------  
> type_s: child_type2   ------------------------- type_s: child_type3
> --------------------------/--------------\ 
> ----------------------------------------- 
> /------------------\---------------------------------------/                \ 
>         
> type_s: grandchild_type4    type_s: grandchild_type5       grandchild_type6   
>     grandchild_type4      grandchild_type7   grandchild_type5
>  
> So the hierarchy distinguishing field  type_s can have different values at 
> different levels of the hierarchy because the nodes could be of different 
> type.
> 
> 
> Further, in Solr 5.3.1 
> solr-5.3.1$ bin/post -c my_collection ../data/data-solr.json 
> doesn't produce any error and I can produce BlockJoin queries using  type_s 
> field for indicating the nodes.   
> 
> However, in Solr 5.5.0, when I try upload the same data in the same format 
> (which was consumed perfectly in Solr 5.3.2):
> solr-5.5.0$ bin/post -c my_collection ../data/data-solr.json
> I get the following error:  
> "msg":"ERROR: [parent=id1] multiple values encountered for non multiValued 
> field _childDocuments_._childDocuments_.type_s: [grandchild_type4, 
> grandchild_type5]" .
> 
> 
> So now I feel that I should have either 2 types of fields for hierarchy 
> description: one for hierarchy level specification and another for type of 
> node specification; or make all single-valued fields multi-valued in 
> descendants.  However, I am not sure whetherte 2nd option will uniquely  
> specify a document. 
> 
> Can anybody advise on the data modelling/schema approach for successful 
> navigation a hierarchical data structure?  
> I will be trying to adapt the approach outlined in " The Many Facets of 
> Apache Solr " to my data. Yet I would like to hear any other practical tips 
> for hierarchical data on Solr 5.5?
> 
> Thank you in advance. 
> --Alisa 
> 
> 
>> Sat, 26 Mar 2016 -4:48:00 -0400 от Yonik Seeley <ysee...@gmail.com>:
>> 
>> Found the JIRA:  https://issues.apache.org/jira/browse/SOLR-7042
>> It looks like you can try adding
>>    -format solr
>> to your bin/post command line to get back to normal "solr JSON"
>> 
>> -Yonik
>> 
>> 
>> On Fri, Mar 25, 2016 at 8:43 PM, Yonik Seeley < ysee...@gmail.com > wrote:
>>> On Fri, Mar 25, 2016 at 6:19 PM, Alisa Z. < prol...@mail.ru > wrote:
>>>> Hi all,
>>>> It is partially a question, partially a discussion.
>>>> I am working with documents with deep levels of nesting. The documents are 
>>>> in a single JSON file (see a sample below).
>>>> 
>>>> When I was on Solr 5.3.1,
>>>> solr-5.3.1$ bin/post -c my_collection ../data/data-solr.json
>>> 
>>> I think i recall seeing a JIRA go by that changed the URL that
>>> /bin/post hits from /update/json to /update/json/docs.
>>> I know the latter does more processing and handles "custom" JSON, but
>>> I don't know the details.  That would be my guess about what changed
>>> and what's messing you up.
>>> 
>>> You could try using curl directly to /update/json and see if that works 
>>> better.
>>> 
>>> -Yonik
> 

Reply via email to