The hit from the command line has the same wrong integer, but I cannot repeat this problem using a new index. Could it be corruption? Some of my other indices were corrupted because of node thrashing: new nodes kept being started after updating to 1.0.1 because I didn't know the command line options and default behavior were changed (!!!).
-- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d0465fc9-ce73-4ff5-9154-568619a5565e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
