Problem with reading

I am able to establish a connection but there is some problem with reading the columns. When I do df.columns, I see an empty list. When I do df.shape, I see (260654884, 0). When I do df.info_es(), I see the following error.

`AttributeError Traceback (most recent call last) <ipython-input-10-3038caf276b4> in <module> ----> 1 df.info_es()

~/.local/lib/python3.7/site-packages/eland/dataframe.py in info_es(self) 548 buf = StringIO() 549 –> 550 super()._info_es(buf) 551 552 return buf.getvalue()

~/.local/lib/python3.7/site-packages/eland/ndframe.py in _info_es(self, buf) 149 150 def _info_es(self, buf): –> 151 self._query_compiler.info_es(buf) 152 153 def mean(self, numeric_only=True):

~/.local/lib/python3.7/site-packages/eland/query_compiler.py in info_es(self, buf) 471 self._index.info_es(buf) 472 self._mappings.info_es(buf) –> 473 self._operations.info_es(self, buf) 474 475 def describe(self):

~/.local/lib/python3.7/site-packages/eland/operations.py in info_es(self, query_compiler, buf) 774 query_params, post_processing = self._resolve_tasks(query_compiler) 775 size, sort_params = Operations._query_params_to_size_and_sort(query_params) –> 776 _source = query_compiler._mappings.get_field_names() 777 778 script_fields = query_params[‘query_script_fields’]

~/.local/lib/python3.7/site-packages/eland/field_mappings.py in get_field_names(self, include_scripted_fields) 548 def get_field_names(self, include_scripted_fields=True): 549 if include_scripted_fields: –> 550 return self._mappings_capabilities.es_field_name.to_list() 551 552 return self._mappings_capabilities[

~/.local/lib/python3.7/site-packages/pandas/core/generic.py in getattr(self, name) 5177 if self._info_axis._can_hold_identifiers_and_holds_name(name): 5178 return self[name] -> 5179 return object.getattribute(self, name) 5180 5181 def setattr(self, name, value):

AttributeError: ‘DataFrame’ object has no attribute ‘es_field_name’`

[mano-lifion]

@stevedodson You are correct. My elastic search version is 6.x. We are in the process of updating it to 7.x and I just realized that the update has not completely been rolled out. I apologize for the incorrect information in my earlier comment.

I should wait for the update to be complete and try it again. Thank you very much for the help!

[stevedodson]

@mano-professional - your mapping contains a doc ‘type’ (https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html) which seems to imply your Elasticsearch version is 6.x not 7.x.

Could you confirm the Elasticsearch version e.g. the response from GET localhost:9200/?

In any case #149 adds some partial support for accessing 6.x clusters, so may fix your issue.