Re: auto-generated emails

I'm going to create a ticket to turn off pull request comments to the dev@ mailing list. In addition to that, we have also PR comments attached to JIRA: https://reference.apache.org/pmc/github The JIRA comments are also sent to the mailing list. So we could either turn off attaching PR comments

[jira] [Commented] (APEXMALHAR-2129) ManagedState: Add a disable purging option

[ https://issues.apache.org/jira/browse/APEXMALHAR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418173#comment-15418173 ] ASF GitHub Bot commented on APEXMALHAR-2129: GitHub user chandnisingh reopened a pull

[jira] [Commented] (APEXMALHAR-2129) ManagedState: Add a disable purging option

[ https://issues.apache.org/jira/browse/APEXMALHAR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418174#comment-15418174 ] ASF GitHub Bot commented on APEXMALHAR-2129: Github user chandnisingh closed the pull

[GitHub] apex-core issue #365: APEXCORE-494 Fix scale up from single partition when p...

Github user tweise commented on the issue: https://github.com/apache/apex-core/pull/365 Trailing white spaces in PhysicalPlan got removed automatically when saving the file. I have no intention adding them back :-) It would be nice if checkstyle would catch them.. --- If your

[GitHub] apex-core pull request #365: APEXCORE-494 Fix scale up from single partition...

Github user tweise commented on a diff in the pull request: https://github.com/apache/apex-core/pull/365#discussion_r74525780 --- Diff: engine/src/main/java/com/datatorrent/stram/plan/physical/StreamMapping.java --- @@ -285,6 +286,17 @@ private void redoMapping()

[jira] [Commented] (APEXMALHAR-2142) High-level API window support

[ https://issues.apache.org/jira/browse/APEXMALHAR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417939#comment-15417939 ] ASF GitHub Bot commented on APEXMALHAR-2142: Github user siyuanh closed the pull request

[jira] [Commented] (APEXMALHAR-2142) High-level API window support

[ https://issues.apache.org/jira/browse/APEXMALHAR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417940#comment-15417940 ] ASF GitHub Bot commented on APEXMALHAR-2142: GitHub user siyuanh reopened a pull request:

[GitHub] apex-malhar pull request #339: APEXMALHAR-2142 Windowed Stream First Impleme...

GitHub user siyuanh reopened a pull request: https://github.com/apache/apex-malhar/pull/339 APEXMALHAR-2142 Windowed Stream First Implementation This is for review only, please ignore all checkstyle violations, format issue etc. For windowed operator changes, refer

[GitHub] apex-malhar pull request #339: APEXMALHAR-2142 Windowed Stream First Impleme...

Github user siyuanh closed the pull request at: https://github.com/apache/apex-malhar/pull/339 --- 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

Re: can operators emit on a different from the operator itself thread?

Correct, except that it is Sink not an Operator that will need to save current thread during setup(). Sink does not need access to an Operator, it is sufficient to rely on the platform to call setup() method on the Operator thread. Vlad On 8/11/16 11:47, Munagala Ramanath wrote: If I

Re: can operators emit on a different from the operator itself thread?

If I understand Vlad correctly, what he is saying is that each operator saves currentThread in its own setup() and checks it in its own output methods. The threads in different operators are running potentially on different nodes and/or processes and there will be no connection between them. Ram

Re: can operators emit on a different from the operator itself thread?

Name check is expensive, agreed, but there isn’t anything else currently. Ideally the stram engine (considering that it is an engine providing resources like threads etc) should use a ThreadFactory or a ThreadGroup to create operator threads so identification and adding functionality is easier.

Re: can operators emit on a different from the operator itself thread?

Name verification is too expensive, it will be sufficient to store currentThread during setup() and verify that it is the same during emit. Checks should be supported not only for DefaultOutputPort, so we may have it implemented in various Sinks. Vlad On 8/11/16 10:21, Sanjay Pujare wrote:

[jira] [Created] (APEXMALHAR-2186) Configurable start offset for kafka input operator (0.9)

Siyuan Hua created APEXMALHAR-2186: -- Summary: Configurable start offset for kafka input operator (0.9) Key: APEXMALHAR-2186 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2186 Project: Apache

[jira] [Updated] (APEXMALHAR-2186) Configurable start offset for kafka input operator (0.9)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2186: --- Issue Type: Improvement (was: Bug) > Configurable start offset for kafka input operator

Re: can operators emit on a different from the operator itself thread?

Thinking more about this – all of the “operator” threads are created by the Stram engine with appropriate names. So we can put checks in the DefaultOutputPort.emit() or in the various implementations of Sink.put() that the current-thread is one created by the Stram engine (by verifying the

[jira] [Resolved] (APEXMALHAR-2172) Update JDBC poll input operator to fix issues

[ https://issues.apache.org/jira/browse/APEXMALHAR-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhupesh Chawda resolved APEXMALHAR-2172. Resolution: Fixed Merged > Update JDBC poll input operator to fix issues >

[jira] [Updated] (APEXMALHAR-2172) Update JDBC poll input operator to fix issues

[ https://issues.apache.org/jira/browse/APEXMALHAR-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhupesh Chawda updated APEXMALHAR-2172: --- Fix Version/s: 3.5.0 > Update JDBC poll input operator to fix issues >

[GitHub] apex-malhar pull request #358: APEXMALHAR-2172: Updates to JDBC Poll Input O...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/358 --- 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

[jira] [Commented] (APEXMALHAR-2100) Development of Inner Join Operator using Spillable Datastructures

[ https://issues.apache.org/jira/browse/APEXMALHAR-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417048#comment-15417048 ] ASF GitHub Bot commented on APEXMALHAR-2100: Github user chaithu14 closed the pull

[jira] [Commented] (APEXMALHAR-2100) Development of Inner Join Operator using Spillable Datastructures

[ https://issues.apache.org/jira/browse/APEXMALHAR-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417049#comment-15417049 ] ASF GitHub Bot commented on APEXMALHAR-2100: GitHub user chaithu14 reopened a pull

[GitHub] apex-malhar pull request #330: APEXMALHAR-2100 Implementation of Inner Join ...

Github user chaithu14 closed the pull request at: https://github.com/apache/apex-malhar/pull/330 --- 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

[GitHub] apex-malhar pull request #330: APEXMALHAR-2100 Implementation of Inner Join ...

GitHub user chaithu14 reopened a pull request: https://github.com/apache/apex-malhar/pull/330 APEXMALHAR-2100 Implementation of Inner Join operator You can merge this pull request into a Git repository by running: $ git pull https://github.com/chaithu14/incubator-apex-malhar

[GitHub] apex-malhar pull request #358: APEXMALHAR-2172: Updates to JDBC Poll Input O...

Github user DT-Priyanka closed the pull request at: https://github.com/apache/apex-malhar/pull/358 --- 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

[jira] [Commented] (APEXMALHAR-2172) Update JDBC poll input operator to fix issues

[ https://issues.apache.org/jira/browse/APEXMALHAR-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417030#comment-15417030 ] ASF GitHub Bot commented on APEXMALHAR-2172: GitHub user DT-Priyanka reopened a pull

[GitHub] apex-malhar pull request #358: APEXMALHAR-2172: Updates to JDBC Poll Input O...

GitHub user DT-Priyanka reopened a pull request: https://github.com/apache/apex-malhar/pull/358 APEXMALHAR-2172: Updates to JDBC Poll Input Operator Changes include: 1. Using jooq query to construct sql queries 2. Update logic to query based on row numbers instead of primary

[jira] [Commented] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

[ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417017#comment-15417017 ] ASF GitHub Bot commented on APEXCORE-494: - Github user chaithu14 commented on a diff in the pull

[jira] [Created] (APEXMALHAR-2185) Add a Deduper implementation for Bounded data

Bhupesh Chawda created APEXMALHAR-2185: -- Summary: Add a Deduper implementation for Bounded data Key: APEXMALHAR-2185 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2185 Project: Apache

Re: [ANNOUNCE] New Apache Apex Committer: Devendra Tagare

Congrats Dev!! -Priyanka On Thu, Aug 11, 2016 at 11:45 AM, Yogi Devendra < devendra.vyavah...@gmail.com> wrote: > Congratulations Dev !!! > > ~ Yogi > > On 11 August 2016 at 11:37, Chinmay Kolhatkar > wrote: > > > Congrats Dev!! > > > > On Thu, Aug 11, 2016 at 10:50

[jira] [Commented] (APEXMALHAR-2151) Enricher - Add delimited file format support to FSLoader

[ https://issues.apache.org/jira/browse/APEXMALHAR-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416667#comment-15416667 ] ASF GitHub Bot commented on APEXMALHAR-2151: Github user shubham-pathak22 closed the pull

[jira] [Commented] (APEXMALHAR-2151) Enricher - Add delimited file format support to FSLoader

[ https://issues.apache.org/jira/browse/APEXMALHAR-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416668#comment-15416668 ] ASF GitHub Bot commented on APEXMALHAR-2151: GitHub user shubham-pathak22 reopened a pull

[jira] [Commented] (APEXMALHAR-2063) Integrate WAL to FS WindowDataManager

[ https://issues.apache.org/jira/browse/APEXMALHAR-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416641#comment-15416641 ] ASF GitHub Bot commented on APEXMALHAR-2063: Github user ilooner commented on a diff in

[jira] [Commented] (APEXMALHAR-2184) Add documentation for FileSystem Input Operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416638#comment-15416638 ] ASF GitHub Bot commented on APEXMALHAR-2184: GitHub user DT-Priyanka opened a pull

[jira] [Created] (APEXMALHAR-2184) Add documentation for FileSystem Input Operator

Priyanka Gugale created APEXMALHAR-2184: --- Summary: Add documentation for FileSystem Input Operator Key: APEXMALHAR-2184 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2184 Project: Apache

[jira] [Commented] (APEXMALHAR-2063) Integrate WAL to FS WindowDataManager

[ https://issues.apache.org/jira/browse/APEXMALHAR-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416630#comment-15416630 ] ASF GitHub Bot commented on APEXMALHAR-2063: Github user ilooner commented on a diff in

Re: A proposal for Malhar

Thomas thanks for the suggestions and the comments in the document. I will take another look at the ones that I had shortlisted in the document to keep. Within that subset, would it be ok to leave the ones that don't have a large state problem, for the time being, till we have replacement

Re: [ANNOUNCE] New Apache Apex Committer: Devendra Tagare

Congratulations Dev !!! ~ Yogi On 11 August 2016 at 11:37, Chinmay Kolhatkar wrote: > Congrats Dev!! > > On Thu, Aug 11, 2016 at 10:50 AM, Shubham Pathak > wrote: > > > Congratulations Dev ! > > > > Thanks, > > Shubham > > > > On Thu, Aug 11,

Re: [ANNOUNCE] New Apache Apex Committer: Devendra Tagare

Congrats Dev!! On Thu, Aug 11, 2016 at 10:50 AM, Shubham Pathak wrote: > Congratulations Dev ! > > Thanks, > Shubham > > On Thu, Aug 11, 2016 at 10:43 AM, Bhupesh Chawda > wrote: > > > Congrats Dev!! > > > > ~ Bhupesh > > > > On Thu, Aug 11,