[ 
https://issues.apache.org/jira/browse/SOLR-16655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fil Shaman updated SOLR-16655:
------------------------------
    Description: 
I testing some functionality of indexing nested child documents and It looks 
like the custom URPs does not apply to child documents and Solr  use build-in 
update request processor chain to processing childs.

Configs and data to reproduce the issue  in the attachment.

When sending data to Solr:

{{{{{}curl --data-binary @nested.json -H 'Content-type:application/json' 
'[http://localhost:8983/solr/nesttest/update?commit=true'|http://localhost:8983/solr/nesttest/update?commit=true%27]{}}}}}

{\{{}}
{{  "responseHeader":{}}
{{    "status":400,}}
{{    "QTime":1},}}
{{  "error":{}}
{{    "metadata":[}}
{{      "error-class","org.apache.solr.common.SolrException",}}
{{      "root-error-class","org.apache.solr.common.SolrException"],}}
{{    "msg":"ERROR: [doc=doc1c1c1] Error adding field 
'date'='2015-10-02T14:52:37' msg=Invalid Date String:'2015-10-02T14:52:37'",}}
{{{}    "code":400{}}}}}

If remove child from data, dates fields recognized with configured templates 
correctly. If added to date field value in children 'Z' char it again work.

 

  was:
I testing some functionality of indexing nested child documents and It looks 
like the custom URPs does not apply to child documents and Solr  use default 
update request processor chain to processing childs.

Configs and data to reproduce the issue  in the attachment.

When sending data to Solr:

{{{{curl --data-binary @nested.json -H 'Content-type:application/json' 
'[http://localhost:8983/solr/nesttest/update?commit=true'|http://localhost:8983/solr/nesttest/update?commit=true%27]}}}}

{{{}}
{{  "responseHeader":{}}
{{    "status":400,}}
{{    "QTime":1},}}
{{  "error":{}}
{{    "metadata":[}}
{{      "error-class","org.apache.solr.common.SolrException",}}
{{      "root-error-class","org.apache.solr.common.SolrException"],}}
{{    "msg":"ERROR: [doc=doc1c1c1] Error adding field 
'date'='2015-10-02T14:52:37' msg=Invalid Date String:'2015-10-02T14:52:37'",}}
{{    "code":400}}}}

If remove child from data, dates fields recognized with configured templates 
correctly. If added to date field value in children 'Z' char it again work.

 


> Indexing nested documents and URPs
> ----------------------------------
>
>                 Key: SOLR-16655
>                 URL: https://issues.apache.org/jira/browse/SOLR-16655
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Schema and Analysis
>    Affects Versions: 8.11.2
>            Reporter: Fil Shaman
>            Priority: Major
>         Attachments: managed-schema, nested.json, solrconfig.xml
>
>
> I testing some functionality of indexing nested child documents and It looks 
> like the custom URPs does not apply to child documents and Solr  use build-in 
> update request processor chain to processing childs.
> Configs and data to reproduce the issue  in the attachment.
> When sending data to Solr:
> {{{{{}curl --data-binary @nested.json -H 'Content-type:application/json' 
> '[http://localhost:8983/solr/nesttest/update?commit=true'|http://localhost:8983/solr/nesttest/update?commit=true%27]{}}}}}
> {\{{}}
> {{  "responseHeader":{}}
> {{    "status":400,}}
> {{    "QTime":1},}}
> {{  "error":{}}
> {{    "metadata":[}}
> {{      "error-class","org.apache.solr.common.SolrException",}}
> {{      "root-error-class","org.apache.solr.common.SolrException"],}}
> {{    "msg":"ERROR: [doc=doc1c1c1] Error adding field 
> 'date'='2015-10-02T14:52:37' msg=Invalid Date String:'2015-10-02T14:52:37'",}}
> {{{}    "code":400{}}}}}
> If remove child from data, dates fields recognized with configured templates 
> correctly. If added to date field value in children 'Z' char it again work.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to