The extra port seems unnecessary unless you are planning to associate each
individual data tuple with a file reference (similar to WindowedTuple)?
On Sat, Jun 3, 2017 at 8:50 PM, Bhupesh Chawda
wrote:
> This is not specific to the batch work. This is a more generic
> functionality which even str
This is not specific to the batch work. This is a more generic
functionality which even streaming applications can benefit from.
The separate port is for both the actual tuple as well as the metadata.
~ Bhupesh
___
Bhupesh Chawda
E: bhup...@
The way this is supposed to work is if the downstream operator wants both
data+metadata then it connects to this new port ("...which would carry the
meta data along with the actual tuple...") otherwise it connects to the
legacy port which continues to behave the same way. Note that each tuple on
th
[
https://issues.apache.org/jira/browse/APEXCORE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXCORE-739:
--
Labels: newbie (was: )
> Remove empty checkstyle-suppressions.xml from codestyle
> --
Thomas Weise created APEXCORE-739:
-
Summary: Remove empty checkstyle-suppressions.xml from codestyle
Key: APEXCORE-739
URL: https://issues.apache.org/jira/browse/APEXCORE-739
Project: Apache Apex Core
[
https://issues.apache.org/jira/browse/APEXMALHAR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2505:
-
Fix Version/s: 3.8.0
> SnapshotSchema should retain original field order
> --
[
https://issues.apache.org/jira/browse/APEXMALHAR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved APEXMALHAR-2505.
--
Resolution: Fixed
Assignee: Thomas Weise
> SnapshotSchema should retain origi
[
https://issues.apache.org/jira/browse/APEXMALHAR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036113#comment-16036113
]
ASF GitHub Bot commented on APEXMALHAR-2505:
Github user asfgit closed th
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/629
---
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036103#comment-16036103
]
ASF GitHub Bot commented on APEXMALHAR-2505:
GitHub user tweise reopened
[
https://issues.apache.org/jira/browse/APEXMALHAR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036102#comment-16036102
]
ASF GitHub Bot commented on APEXMALHAR-2505:
Github user tweise closed th
Github user tweise closed the pull request at:
https://github.com/apache/apex-malhar/pull/629
---
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
GitHub user tweise reopened a pull request:
https://github.com/apache/apex-malhar/pull/629
APEXMALHAR-2505 retain original field order in SnapshotSchema
@amberarrow please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/twe
How does this relate to the batch control tuples work?
With a separate port, how can a downstream operator relate the metadata to
the tuples emitted from the primary port?
--
sent from mobile
On Jun 2, 2017 12:06 PM, "Bhupesh Chawda" wrote:
Hi,
Emitting file
information
for a file based
[
https://issues.apache.org/jira/browse/APEXCORE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035997#comment-16035997
]
Pramod Immaneni commented on APEXCORE-736:
--
The exception is thrown because yar
[
https://issues.apache.org/jira/browse/APEXCORE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035997#comment-16035997
]
Pramod Immaneni edited comment on APEXCORE-736 at 6/3/17 3:28 PM:
Hi,
I'm currently preoccupied, won't be able to work on this as of now.
Thanks,
A
_
Sent with difficulty, I mean handheld ;)
On 1 Jun 2017 10:23 am, "Thomas Weise" wrote:
> Hi,
>
> I recently tried to figure out what is involved in maintaining the Apex
>
17 matches
Mail list logo
