On 2022-08-27 9:47 PM, Rahul Goswami wrote:
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.
Why would one want to interpret 1 as true in non-boolean context? (hint, hint)
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"
}
The bug is, I have 1 in stock. Not 2, not "true", just 1. Dima
