[jira] [Created] (SOLR-16360) Atomic update on boolean fields doesn't reflect when value starts with "1", "t" or "T"

["Rahul Goswami (Jira)" <ji...@apache.org>]

Rahul Goswami created SOLR-16360:
------------------------------------

             Summary: Atomic update on boolean fields doesn't reflect when value starts with "1", "t" or "T"
                 Key: SOLR-16360
                 URL: https://issues.apache.org/jira/browse/SOLR-16360
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
    Affects Versions: 8.11
            Reporter: Rahul Goswami


I am running Solr 8.11. As per the Solr documentation, any value starting with "1","t" or "T" for a boolean field is interpreted as true.
 [https://solr.apache.org/guide/8_11/field-types-included-with-solr.html#recommended-field-types]
 
However, I hit a potential Solr bug where if the String value  "1","t" or "T"  is passed in an atomic update, it is treated as false.
 
//Eg:Below document is indexed first => query returns "inStock" as true (as expected) 
{
"id":"test",
"inStock":"true"
}
 
//Follow above update with below atomic update and commit. => inStock becomes false in query result
{
"id":"test",
"inStock":\{"set":"1"}
}
 
This doesn't happen though if value "1" is passed in a regular update.
Eg:Below update reflects the value of inStock as true when queried.
{
"id":"test",
"inStock":"1"
}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org