Btw, why not fix the transformation?
Hi Shay, thanks for the hint. I'm doing this already, but this means
another iteration through the data costing CPU + time;
Currently we grab an SQL result from MYSQL that already is in a map
form and pass it to ES via Java API. Problem here is that mysql can't
easily understand that some of the extracted XML values are not String
and instead makes them all to String. This then leads to trouble for
sorting order... so we define for ES some fields as numeric, but then
are buggered with this empty "" and null problem;
On 13 Nov., 08:14, Shay Banon kim...@gmail.com wrote:
We can support empty strings as null values for numeric types. Open an
issue. Btw, why not fix the transformation?
On Thu, Nov 10, 2011 at 1:13 PM, K.B. korbinian.ba...@googlemail.comwrote:
I know we had this in the past, but could please a feature be
introduced to have a flag at numbers like integer, float, etc, so we
can have ES make empty Strings a "null" value instead?
Currently an empty String "" ceates a
org.elasticsearch.index.mapper.MapperParsingException: Failed to parse
I have this problem when data extracted from XML is passed to ES (done
by ExtractValue in mysql - he can't differ if null or emptyString