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

Remove size limitations #178

Closed
To-om opened this issue Mar 13, 2019 · 0 comments
Closed

Remove size limitations #178

To-om opened this issue Mar 13, 2019 · 0 comments
Assignees
Milestone

Comments

@To-om
Copy link
Contributor

To-om commented Mar 13, 2019

Request Type

Feature Request

Problem Description

Depending on how data is stored in ElasticSearch, some fields have size limitation (32kB). In some cases, it is not enough. For example, some responders accept TheHive alert as input, which can be huge.

Solutions

The aim of this issue is to change the ElasticSearch mapping of fields that may contain large data:

  • data in artifact
  • data, parameters and input in job
  • full, summary and operations in report
  • avatar and preferences in user
  • configuration in worker and workerConfig

All these fields, will be stored in a binary format, without analysis and wont be indexed. Thus, they become unsearchable.

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

No branches or pull requests

1 participant