Seth Michael Larson
Seth Michael Larson
What is your use case for adding a constant column to an Eland dataframe? Does pulling your data locally and doing this operation in Pandas fit your use case?
jenkins test this please
For anyone finding this issue, there is already support for referencing fields by name via `df["agent.hostname"]`.
Thanks for opening this, I'll take a look and see if there are any optimizations to be made.
The area that needs most optimizing is the `QueryParams._flatten_dict()` method and the `Mapping` class.
I'm wondering if it makes sense to have `es_info` display things more vertically rather than horizontally. There'd be a lot of output but at least you'd be able to see...
@NickolayVasilishin Agreed! Having an object is definitely preferred.
I'll handle the elasticsearch-py stuff, there's a subtle change that needs to be made regarding which elasticsearch-py version to install
jenkins test this please
This is unlikely to be implemented as its no more efficient than `ed_df.to_pandas().apply()`. Is there a use-case in particular that's more efficient to implement and desirable?