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

Cao Manh Dat updated SOLR-8543:
-------------------------------
    Description: 
When schemaless core index a json document. Solr will try to find field type 
based on first value. It is quite convenient, but sometime solr's detection is 
not match with json specification. For example, given a document
{code}
{
 "name" : "50",
 "star" : 5
}
{code}
Solr will detect {{name, star}} as {{long}} field. But it quite trivial in json 
when a value is number or string. So {{name}} should be {{string}} field and 
{{star}} should be {{long}} field.

  was:
When schemaless core index a json document. Solr will try to find field type 
based on first value. It is quite convenient, but sometime solr's detection is 
not match with json specification. For example, given a document
{code}
{
 "name" : "50",
 "star" : 5
}
{code}
Solr will detect {{name, star}} as {{long}} field. But it quite trivial in json 
when a value is number or string. So {{name}} should be {{string}} field and 
star as {{long}} field.


> Index json documents properly
> -----------------------------
>
>                 Key: SOLR-8543
>                 URL: https://issues.apache.org/jira/browse/SOLR-8543
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Cao Manh Dat
>         Attachments: SOLR-8543.patch
>
>
> When schemaless core index a json document. Solr will try to find field type 
> based on first value. It is quite convenient, but sometime solr's detection 
> is not match with json specification. For example, given a document
> {code}
> {
>  "name" : "50",
>  "star" : 5
> }
> {code}
> Solr will detect {{name, star}} as {{long}} field. But it quite trivial in 
> json when a value is number or string. So {{name}} should be {{string}} field 
> and {{star}} should be {{long}} field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to