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

Object array fields missing from field chooser #3410

Closed
vichargrave opened this issue Mar 20, 2015 · 0 comments · Fixed by #3583
Closed

Object array fields missing from field chooser #3410

vichargrave opened this issue Mar 20, 2015 · 0 comments · Fixed by #3583
Assignees
Labels
bug Fixes for quality problems that affect the customer experience good first issue low hanging fruit Mend It Monday

Comments

@vichargrave
Copy link

I'm ingesting fields from tweets into Elasticsearch 1.4.4. I'm dynamically mapping the entities.urls.expanded_url field - see https://dev.twitter.com/overview/api/entities#obj-url. Here is that the field looks like in Sense:

screen shot 2015-03-20 at 3 10 37 pm

I can see the entities.urls field in the list of fields to select in the table view of KIbana 3 as you can see here:

screen shot 2015-03-20 at 3 07 57 pm

I cannot see the same field in the list of selectable fields in the Discover view of Kibana 4 - note the "entitied.urls" field should show up between the "created_at" and "favorite_count" fields:

screen shot 2015-03-20 at 3 12 42 pm

However I can see the field and its contents in the table part of the Discover view that shows the contents of the _source field:

screen shot 2015-03-20 at 3 11 10 pm

Will this be fixed in a future revision of Kibana 4?

@rashidkpc rashidkpc changed the title Problem with dynamically mapped Twitter field in Kibana 4 Object array fields missing from field chooser Mar 20, 2015
@rashidkpc rashidkpc added bug Fixes for quality problems that affect the customer experience good first issue low hanging fruit labels Mar 20, 2015
@spalger spalger self-assigned this Apr 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience good first issue low hanging fruit Mend It Monday
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants