You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@streams.apache.org by "Steve Blackmon (JIRA)" <ji...@apache.org> on 2018/11/02 16:02:00 UTC

[jira] [Updated] (STREAMS-148) Platform-level type validation

     [ https://issues.apache.org/jira/browse/STREAMS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Blackmon updated STREAMS-148:
-----------------------------------
    Sprint:   (was: 0.6.1)

> Platform-level type validation
> ------------------------------
>
>                 Key: STREAMS-148
>                 URL: https://issues.apache.org/jira/browse/STREAMS-148
>             Project: Streams
>          Issue Type: Improvement
>            Reporter: Steve Blackmon
>            Priority: Major
>
> Investigate / implement mechanisms for a streams runtime (starting with streams-runtime-local) to validate each document against it's declared type class(es) using whatever javax.validation annotations are present on those classes at any point where a document is pulled off a provider or processor  outbound queue.  A non-valid document should be logged to WARN, and written to a different queue which downstream processors/providers can connect to using StreamBuilder.  Demonstrate this works by making activity.id a required field in streams-pojo and having a test that ensures an activity without an id is caught and handled by the runtime.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)