-
Notifications
You must be signed in to change notification settings - Fork 24.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to index with logstash with current master #11458
Comments
isn't this a logstash issue in the first place? I mean null is not a valid id? |
I don't know anything about the particulars, I just wanted to raise the issue. I'm using logstash 1.5 fwiw. |
@rmuir When it was working you were running logstash 1.4.2? |
When i started doing index size tests with master, I started with a 1.5 release candidate but upgraded to the official release. Since then i semi-regularly index that test dataset with logstash into es master, because its a little sample index for debugging, etc. (in this case, I am looking at our stats api so i wanted some data there) |
@rmuir I'll have a look, lets keep this issue open, if needed I'll migrate it. |
btw. this is also in |
#11331 throws an exception if a "metadata" field (like |
we should see if this is a regression on the logstash-output-elasticsearch plugin /cc @talevy . |
@tlrx i think that null values should be ignored here |
Easy fix on our side we can remove the |
@ph we should just fix this before 1.6, to ignore null values. |
This will be fixed by #11459, sorry for the regression |
This was working for me as of a few weeks ago. but now I hit this:
Got error to send bulk of actions to elasticsearch server at localhost : [400] {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Malformed action/metadata line [1], expected a simple value for field [_id] but found [VALUE_NULL]"}],"type":"illegal_argument_exception","reason":"Malformed action/metadata line [1], expected a simple value for field [_id] but found [VALUE_NULL]"},"status":400} {:level=>:error}
I'm using the simple config here: https://github.com/peterskim12/elk-index-size-tests
The text was updated successfully, but these errors were encountered: