Higher level of details for parsing error in CSV import

[bahaaldine]

The current level of details a user get for parsing error does not allow for debugging:

Could be good to have at least the field and the related parsing error details.

[Bargs]

The field name should be included. Could you provide the CSV you're using and a screen shot of the type mapping step?

[bahaaldine]

@Bargs here is the file I'm using:

https://drive.google.com/open?id=0B2nTr5APsKxcbjNLMm52M0RySTg

Here is the mapping screenshot:

This is the parsing error output:

With +13000 lines displayed in the list (#7648)

[Bargs]

@bahaaldine those output screenshots look different than the one in your original post, in this case it's correctly identifying timestamp as the problem field. Do you have any idea what happened in your original screenshot?

[bahaaldine]

@Bargs that's true and I don't know how I got the first screenshot, and I can't reproduce it.

My point for this issue is:

• The field name is indeed included, but the user doesn't why there was an error. I think it's necessary to have the parse exception detail.
• Only one field name is actually shown up, here related test:
  • I've first tried to import the same CSV by setting the Date to a date type:

• and this is what I have:

So far so good.

• When I try to set both timestamp and Date to date

• This is what I got

• Only timestamp is displayed in the error, even if I go through all the +13K lines, Date is never displayed.

[Bargs]

Hmmm yeah that does stink. I wonder if Elasticsearch returns both errors, or if I'm only getting timestamp back. I'll have to check.

The field name is indeed included, but the user doesn't why there was an error. I think it's necessary to have the parse exception detail.

Could you add your thoughts on that to this ticket #7632? I'm not sure yet what the perfect error message looks like. For some users the full Elasticsearch error info might be overwhelming, but as you mentioned other users are just gonna want to see the full details from ES.

[epixa]

I'm going to close this since CSV upload was pulled. We can always refer back to this issue if/when we revisit the feature.