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

Kibana doesn't support attachment type plugin #1118

Closed
DreamRocker opened this issue Apr 5, 2014 · 1 comment
Closed

Kibana doesn't support attachment type plugin #1118

DreamRocker opened this issue Apr 5, 2014 · 1 comment

Comments

@DreamRocker
Copy link

I am trying to use Kibana together with the attachment type plugin (https://github.com/elasticsearch/elasticsearch-mapper-attachments).
The problem is that the fields are not discovered correctly and with that the result table isn't useable.

So far I can see this happens since Kibana uses _source to determine the field list. But this list won't contain all the fields that the ES server actually adds with the plugin.

The _source contains something like:
"my_attachment" : {
"_content_type" : "application/pdf",
"_name" : "resource/name/of/my.pdf",
"content" : "... base64 encoded attachment ..."
}

The server extends this data but this is not visible in _source.

DreamRocker pushed a commit to DreamRocker/kibana that referenced this issue Apr 6, 2014
Plugins can add information to uploaded data. This is not always visible in
_source. Therefore the fields parameter can be used to retrieve this data.
This fix only works if the fields that need to be retrieved are set manually
whether in the panel settings (in columns) or by activating the "Preload
Fields" option.

This fixes elastic#1118
Signed-off-by: Marc Koderer <marc@koderer.com>
@rashidkpc
Copy link
Contributor

Kibana needs the fields to be properly mapped. If any given plugin does not do that we simply can't support it.

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

Successfully merging a pull request may close this issue.

3 participants
@rashidkpc @DreamRocker and others