[
https://issues.apache.org/jira/browse/METRON-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436417#comment-16436417
]
ASF GitHub Bot commented on METRON-1347:
----------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/863
It seems this PR is meant to address the global case, since the writer is
general purpose. Per @cestella's comments, I don't know that we can include
original_string. I do think there's value in minimally ensuring the timestamp
and source.type fields are validated in the near term. It seems that addressing
a broader validation strategy might be in order, but maybe we could handle that
separately as a compromise? Thoughts @ottobackwards?
> Indexing Topology should fail tuples without a source.type
> ----------------------------------------------------------
>
> Key: METRON-1347
> URL: https://issues.apache.org/jira/browse/METRON-1347
> Project: Metron
> Issue Type: Bug
> Reporter: Casey Stella
> Priority: Major
>
> If you are sending data into metron indexing without a source.type, which
> would only happen if you're bypassing our previous topologies, we cannot
> configure how we write to the indices, so the message should be explicitly
> failed and reported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
