For the invalid date format case:
The error message is like this:
" MapperParsingException[Failed to parse [birthday]]; nested:
MapperParsingException[failed to parse date field [], tried both date format
[dateOptionalTime], and timestamp number]; nested:
IllegalArgumentException[Invalid format: ""]; ","status":400}"
And I doubt that it is caued by automatical deduction of mapping. Because
the 'date' field has either empty string value "" or "yyyy-mm-dd"
for the invalid "(" case, I fix it , I wrote a script to escape all these
offending '(', but I dont konw how many other invalid character I will
stumble upon
And my main question maybe : why this dirty problem won't occurs when using
mongo-river plugin, but all burst out when I manually do it ??? So I came
here to ask if I do anything wrong or any elegent method ?
For the invalid date format case:
The error message is like this:
" MapperParsingException[Failed to parse [birthday]]; nested:
MapperParsingException[failed to parse date field , tried both date
format [dateOptionalTime], and timestamp number]; nested:
IllegalArgumentException[Invalid format: ""]; ","status":400}"
And I doubt that it is caued by automatical deduction of mapping.
Because the 'date' field has either empty string value "" or
"yyyy-mm-dd"
for the invalid "(" case, I fix it , I wrote a script to escape all
these offending '(', but I dont konw how many other invalid character
I will stumble upon
And my main question maybe : why this dirty problem won't occurs when
using mongo-river plugin, but all burst out when I manually do it ???
So I came here to ask if I do anything wrong or any elegent way to do
this?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.