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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 8.11
• Fix Version/s: 9.4
• Assignee: Unassigned
• Reporter: Rahul Goswami
• Created: 29/Aug/22 22:53
• Updated: 15/Oct/23 19:57
• Resolved: 09/Aug/23 04:40

Description

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" }

Issue Links

• links to: GitHub Pull Request #1816