Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/438
So assuming we put aside the issue of flattening the data per METRON-735,
what should be the go-forward for this PR? I outlined two options above.
Please share your opinions on those options.
> (1) Assume that any indexer that cannot handle complex types is currently
broken.
>
> Since the assumption is that the Solr indexer is 'broke', then we can
move forward and commit this PR (pending further review) BEFORE addressing the
Solr indexer.
> I will then create a JIRA to test and fix any indexer that cannot handle
complex types. Based on the discussion here, I am assuming this includes the
Solr indexer.
>
> (2) Assume that we need to live in our current box.
>
> I will update this PR to flatten the data to make the Solr Indexer happy.
> I will then create a JIRA to fix the Solr Indexer.
> After the Solr Indexer is fixed, I will then create another PR to return
threat triage to its current state (using a complex type instead of flattening.)
Personally I am +1 on option 1, but either works for me. Maybe there is a
better approach that I am not thinking of.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---