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
[X ] Bug report. If you’ve found a bug, please provide a code snippet or test to reproduce it below.
The easier it is to track down the bug, the faster it is solved.
INCORRECTLY states this setting is es.field.read.as.array.include
some other pages (github issues, stackoverflow questions) have this incorrect as well (not sure they can be changed, but misleading nonetheless). It appears maybe this changed in some release and there are lingering references to old setting name? Seems like a very unimportant change that causes potentially lots of confusion... I lost a few hours trying to figure out why this was not working for me.
Version Info
Hadoop/Spark: Spark 1.6.1
ES-Hadoop : 2.4.0
ES : 2.3.1
The text was updated successfully, but these errors were encountered:
What kind an issue is this?
The easier it is to track down the bug, the faster it is solved.
Issue description
Description: There is a discrepancy on documentation of the correct configuration name for
es.read.field.as.array.include
Page:
https://www.elastic.co/guide/en/elasticsearch/hadoop/master/configuration.html#cfg-field-info
is CORRECT in identifying the setting as es.read.field.as.array.include.
Page:
https://www.elastic.co/guide/en/elasticsearch/hadoop/current/mapping.html#mapping-multi-values
INCORRECTLY states this setting is es.field.read.as.array.include
some other pages (github issues, stackoverflow questions) have this incorrect as well (not sure they can be changed, but misleading nonetheless). It appears maybe this changed in some release and there are lingering references to old setting name? Seems like a very unimportant change that causes potentially lots of confusion... I lost a few hours trying to figure out why this was not working for me.
Version Info
Hadoop/Spark: Spark 1.6.1
ES-Hadoop : 2.4.0
ES : 2.3.1
The text was updated successfully, but these errors were encountered: