[
https://issues.apache.org/jira/browse/APEXMALHAR-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314195#comment-15314195
]
Yogi Devendra commented on APEXMALHAR-2104:
-------------------------------------------
As per the discussion on the PR comments, here is the summary of changes:
1. Marking BytesFileOutputOperator as @evolving
1. Removed input port stringInput
1. Added japicmp exclusion for this class
1. Added Converter field for pluging-in custom conversion to byte[]
1. Provided default converters for no-op, String
1. Renamed BytesFileOutputOperator-> GenericFileOutputOperator
1. Introduced BytesFileOutputOperator, String FileOutputOperator
1. Added javadocs
> BytesFileOutputOperator Refactoring
> -----------------------------------
>
> Key: APEXMALHAR-2104
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2104
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Yogi Devendra
> Assignee: Yogi Devendra
> Priority: Minor
>
> BytesFileOutputOperator has two ports one is for byte[] input other is for
> String input.
> We should allow app developers to connect to any one of this port.
> Thus, both the streams should be marked as optional.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
