[ 
https://issues.apache.org/jira/browse/SOLR-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009989#comment-16009989
 ] 

ASF subversion and git services commented on SOLR-10412:
--------------------------------------------------------

Commit 9dc952a47c48f463f04722e2f22ad99689831319 in lucene-solr's branch 
refs/heads/master from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9dc952a ]

SOLR-10412: v2 API: many API command specification properties are typed 
"number" but should instead be typed "integer"


> v2 API: many API command specification properties are typed "number" but 
> should instead be typed "integer" 
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-10412
>                 URL: https://issues.apache.org/jira/browse/SOLR-10412
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: v2 API
>            Reporter: Steve Rowe
>            Priority: Minor
>             Fix For: master (7.0)
>
>
> JSON schema distinguishes between the {{number}} type (which is the same as 
> JSON's number, i.e. an arbitrary precision floating point number) and the 
> {{integer}} type; the latter requires integral values.
> Here are the inappropriately typed {{number}} properties I found  - note that 
> *every single {{number}} type in current use* should instead be an 
> {{integer}}:
> ||apispec file||command||property/ies||
> |collections.collection.Commands.json|rebalance-leaders|maxAtOnce, 
> maxWaitSeconds|
> |collections.Commands.json|create|numShards, replicationFactor|
> |core.SchemaEdit.addFieldType.json|N/A|positionIncrementGap|
> |cores.Commands.json|create|numShards|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to