You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Line 524 uses "include == null" to check if the exclude string is null.
I don't know why this had to be a one-liner, but I don't like using ternary operators, particularly twice (!) on the same line. Makes it harder to read and can lead to bugs like this.
Affects v1.2.1
Cheers!
The text was updated successfully, but these errors were encountered:
jnaous
changed the title
SearchRequestBuilder.setFetchSource(String, String) does not set excludes correctly
SearchSourceBuilder.fetchSource(String, String) does not set excludes correctly
Jun 26, 2014
Due to a bogus if-check in SearchSourceBuilder.fetchSource(String include, String exclude)
the excludes only got set when the includes were not null. Fixed this and added some
basic tests.
Closeselastic#6632
Due to a bogus if-check in SearchSourceBuilder.fetchSource(String include, String exclude)
the excludes only got set when the includes were not null. Fixed this and added some
basic tests.
Closes#6632
spinscale
changed the title
SearchSourceBuilder.fetchSource(String, String) does not set excludes correctly
JAVA API: Fix source excludes setting if no includes were provided
Jul 2, 2014
Due to a bogus if-check in SearchSourceBuilder.fetchSource(String include, String exclude)
the excludes only got set when the includes were not null. Fixed this and added some
basic tests.
Closes#6632
clintongormley
changed the title
JAVA API: Fix source excludes setting if no includes were provided
Java API: Fix source excludes setting if no includes were provided
Jul 9, 2014
clintongormley
changed the title
Java API: Fix source excludes setting if no includes were provided
Fix source excludes setting if no includes were provided
Jun 7, 2015
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Due to a bogus if-check in SearchSourceBuilder.fetchSource(String include, String exclude)
the excludes only got set when the includes were not null. Fixed this and added some
basic tests.
Closeselastic#6632
Line 524 uses "include == null" to check if the exclude string is null.
I don't know why this had to be a one-liner, but I don't like using ternary operators, particularly twice (!) on the same line. Makes it harder to read and can lead to bugs like this.
Affects v1.2.1
Cheers!
The text was updated successfully, but these errors were encountered: