Re: Shutdown of an Apex app

Hi Thomas, The part of initiating the shutdown from another operator was the original intention of the email. ~ Bhupesh On Wed, Jan 18, 2017 at 10:35 PM, Thomas Weise wrote: > Bhupesh, > > If your intention is to let processing complete, the sources should > terminate the

[jira] [Commented] (APEXMALHAR-2392) Upgrade mysql connector in demo applications

[ https://issues.apache.org/jira/browse/APEXMALHAR-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829220#comment-15829220 ] Thomas Weise commented on APEXMALHAR-2392: -- {code} $ git grep -C1 mysql-connector-java

[jira] [Created] (APEXMALHAR-2392) Upgrade mysql connector in demo applications

Thomas Weise created APEXMALHAR-2392: Summary: Upgrade mysql connector in demo applications Key: APEXMALHAR-2392 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2392 Project: Apache Apex

[jira] [Updated] (APEXMALHAR-2390) There is no sorting operator list

[ https://issues.apache.org/jira/browse/APEXMALHAR-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teddy Rusli updated APEXMALHAR-2390: Attachment: FireShot Capture 93 - Apache Apex Malhar Documentation -

[jira] [Created] (APEXMALHAR-2391) JDBC Poller Input Operator exist but not listed

Teddy Rusli created APEXMALHAR-2391: --- Summary: JDBC Poller Input Operator exist but not listed Key: APEXMALHAR-2391 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2391 Project: Apache Apex

[jira] [Updated] (APEXMALHAR-2390) Operator list in doc is not sorted

[ https://issues.apache.org/jira/browse/APEXMALHAR-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teddy Rusli updated APEXMALHAR-2390: Summary: Operator list in doc is not sorted (was: There is no sorting operator list)

[jira] [Updated] (APEXMALHAR-2390) Operator list in doc is not sorted

[ https://issues.apache.org/jira/browse/APEXMALHAR-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teddy Rusli updated APEXMALHAR-2390: Description: The list of operators at http://apex.apache.org/docs/malhar/ is not

[jira] [Created] (APEXMALHAR-2390) There is no sorting operator list

Teddy Rusli created APEXMALHAR-2390: --- Summary: There is no sorting operator list Key: APEXMALHAR-2390 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2390 Project: Apache Apex Malhar

[GitHub] apex-malhar pull request #538: Sort operator list in alphabetical order, cor...

GitHub user trusli opened a pull request: https://github.com/apache/apex-malhar/pull/538 Sort operator list in alphabetical order, correct a few typos and add missing JDBC Poll Input You can merge this pull request into a Git repository by running: $ git pull

[jira] [Resolved] (APEXMALHAR-2359) Optimise fire trigger to avoid go through all data

[ https://issues.apache.org/jira/browse/APEXMALHAR-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2359. --- Resolution: Fixed Fix Version/s: 3.7.0 > Optimise fire trigger to avoid go

Re: google analytics for apex website?

Could we enable this for the download button as well. Thanks On Wed, Oct 12, 2016 at 3:36 PM, Hitesh Shah wrote: > Probably should be accessible to PMC and/or committers only for now. If > the PMC wants to allow sharing this data with other 3rd parties, then the > privacy

[jira] [Commented] (APEXMALHAR-2359) Optimise fire trigger to avoid go through all data

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

[GitHub] apex-malhar pull request #518: APEXMALHAR-2359 #resolve #comment Optimise fi...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/518 --- 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: Shutdown of an Apex app

Bhupesh, If your intention is to let processing complete, the sources should terminate the stream (that's already implemented, except that you want to initiate it from another operator). It does not really matter if they all stop at the same streaming window. If you want to just stop the

ApacheCon CFP closing soon (11 February)

Hello, fellow Apache enthusiast. Thanks for your participation, and interest in, the projects of the Apache Software Foundation. I wanted to remind you that the Call For Papers (CFP) for ApacheCon North America, and Apache: Big Data North America, closes in less than a month. If you've been

Re: Shutdown of an Apex app

Agreed on input adapter way. Enforcing all input adapters send shutdown on the same window cannot be guaranteed, so there will be a corner case where windows are not aligned. An ask from Stram to send shutdown way in the future reduces the scope of the corner case, but then defeats the purpose.

[jira] [Commented] (APEXCORE-604) Extend DAG API to allow accessing DAG objects.

[ https://issues.apache.org/jira/browse/APEXCORE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827946#comment-15827946 ] ASF GitHub Bot commented on APEXCORE-604: - GitHub user tushargosavi opened a pull request:

[GitHub] apex-core pull request #447: APEXCORE-604 extend DAG API to get operators an...

GitHub user tushargosavi opened a pull request: https://github.com/apache/apex-core/pull/447 APEXCORE-604 extend DAG API to get operators and streams from the DAG. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (APEXCORE-503) support KillException

[ https://issues.apache.org/jira/browse/APEXCORE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827814#comment-15827814 ] Tushar Gosavi commented on APEXCORE-503: I am already doing the change to shutdown the

[jira] [Commented] (APEXCORE-294) Graceful application shutdown

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

[GitHub] apex-core pull request #424: APEXCORE-294 controlled shutdown of an applicat...

GitHub user tushargosavi reopened a pull request: https://github.com/apache/apex-core/pull/424 APEXCORE-294 controlled shutdown of an application. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tushargosavi/apex-core

Re: APEXCORE-294 Clean application shutdown

Dear Community, I have changed the implementaion plan based on PR comments. Following is the new proposal for this feature. https://docs.google.com/a/datatorrent.com/document/d/1hSLH4xi_15OWwW4KY7--LU3e2iHHhfthOpATicnC5eE/edit?usp=sharing Please provide the feedback. I will update the PR

[jira] [Closed] (APEXMALHAR-2382) User should not be required to create "dt_meta" table while using JdbcPOJOInsertOutputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Kapoor closed APEXMALHAR-2382. - Resolution: Won't Fix As per the consensus on the dev email thread (attached to this

[jira] [Updated] (APEXMALHAR-2382) User should not be required to create "dt_meta" table while using JdbcPOJOInsertOutputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Kapoor updated APEXMALHAR-2382: -- Attachment: De_meta_mail_thread.pdf Mail thread discussing if/how this Jira should

Re: Schema Discovery Support in Apex Applications

+1 to have this feature. -Priyanka On Tue, Jan 17, 2017 at 9:18 PM, Pramod Immaneni wrote: > +1 > > On Mon, Jan 16, 2017 at 1:23 AM, Chinmay Kolhatkar > wrote: > > > Hi All, > > > > Currently a DAG that is generated by user, if contains any POJOfied

Re: Shutdown of an Apex app

Yes, Amol. That will be the case for a kill type of shutdown. But for graceful shutdown, it is important that each operator in the DAG processes exactly the same amount of data. That is the reason the shutdown needs to start at input operators and stop their functioning as the first step.