Skip to content
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

Column headers on browser should be path not field_name #45

Open
mobz opened this issue Feb 20, 2013 · 2 comments
Open

Column headers on browser should be path not field_name #45

mobz opened this issue Feb 20, 2013 · 2 comments

Comments

@mobz
Copy link
Owner

mobz commented Feb 20, 2013

Hello. I think that browser's column names should be field's path and not field's name.
I have many documents similar to:
{
field1: {
name: "name1",
value: "value2"
},
field2:{
name: "name2",
value: "value2"
},
etc.

And a browser is unusable because only last field is shown.
Columns names should be field1.name, field1.value, field2.name, field2.value instead of name and value.

I hacked it in following way:
in core.js I changed line 342 from
var field_name = metadata.paths[dpath].field_name;
to
var a = path.concat(prop);
a.shift();
a.shift();
var field_name = a.join(".");

I know that's not pretty solution but it works for me.
Maybe it'd be a good addition to elasticsearch-head?
Also I'd like my array type fields to be shown fully, and not only last of them. Is it possible?

@mobz
Copy link
Owner Author

mobz commented Feb 20, 2013

Copied from original issue Aconex/elasticsearch-head#5 by @Avatah

@lukas-lansky
Copy link

This issue bites if you don't know about the behavior. "What is this value there? OMG, my data are so corrupted..."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants