[jira] [Updated] (APEXCORE-542) Fix debug level verbose option for apex cli

2016-09-28 Thread Deepak Narkhede (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Narkhede updated APEXCORE-542: - Description: Fix debug level verbose option for apex cli. Currently "" option displa

[jira] [Updated] (APEXCORE-542) Fix debug level verbose option for apex cli

2016-09-28 Thread Deepak Narkhede (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Narkhede updated APEXCORE-542: - Summary: Fix debug level verbose option for apex cli (was: Add DEBUG level verbose opti

Re: Using DSL api to construct sql queries

2016-09-28 Thread Priyanka Gugale
Thanks for your input Justin. We did use JOOQ runtime only. -Priyanka On Thu, Sep 29, 2016 at 11:16 AM, Justin Mclean wrote: > Hi, > > A little late here but form a quick look it should be OK. > > The jOOQ runtime (which I assume is the bit you want to use) is Apache > licensed and what it depe

[jira] [Created] (APEXCORE-542) Add DEBUG level verbose option to apex cli

2016-09-28 Thread Deepak Narkhede (JIRA)
Deepak Narkhede created APEXCORE-542: Summary: Add DEBUG level verbose option to apex cli Key: APEXCORE-542 URL: https://issues.apache.org/jira/browse/APEXCORE-542 Project: Apache Apex Core

Re: Using DSL api to construct sql queries

2016-09-28 Thread Justin Mclean
Hi, A little late here but form a quick look it should be OK. The jOOQ runtime (which I assume is the bit you want to use) is Apache licensed and what it depends is compatible. You could not bundle the jOOQ-meta-extensions in source or binary release as it depends on Category B license (MPL) w

[jira] [Commented] (APEXCORE-532) New dynamically added operator does not start with correct windowId.

2016-09-28 Thread Tushar Gosavi (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531822#comment-15531822 ] Tushar Gosavi commented on APEXCORE-532: Rechecked the code again, for newly dep

[jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected

2016-09-28 Thread Priyanka Gugale (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531808#comment-15531808 ] Priyanka Gugale commented on APEXMALHAR-2272: - When we developed this mod

[jira] [Commented] (APEXCORE-310) apex cli - support to kill the app by appname

2016-09-28 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531791#comment-15531791 ] ASF GitHub Bot commented on APEXCORE-310: - GitHub user deepak-narkhede opened a

[GitHub] apex-core pull request #399: APEXCORE-310 - Apex cli support to kill the app...

2016-09-28 Thread deepak-narkhede
GitHub user deepak-narkhede opened a pull request: https://github.com/apache/apex-core/pull/399 APEXCORE-310 - Apex cli support to kill the app by appname This changes adds support to kill the application by application name for apex cli. Unit Testing Completed: Please find

[jira] [Updated] (APEXMALHAR-1720) Development of Inner Join Operator

2016-09-28 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-1720: - Labels: (was: roadmap) > Development of Inner Join Operator > -

Re: Automated changes git author

2016-09-28 Thread Pradeep A. Dalvi
Build Meister? On Wed, Sep 28, 2016 at 1:20 PM, Thomas Weise wrote: > What about the name "CI Support"? Does not look like best fit either. Any > better ideas or keep it? > > I will document the outcome in the contributor guidelines. > > On Wed, Sep 28, 2016 at 11:13 AM, Pramod Immaneni > wrote

[jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected

2016-09-28 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531246#comment-15531246 ] Thomas Weise commented on APEXMALHAR-2272: -- Why was the operator not marked

[jira] [Commented] (APEXMALHAR-1818) Integrate Calcite to support SQL

2016-09-28 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530912#comment-15530912 ] Julian Hyde commented on APEXMALHAR-1818: - [~chinmay], I have reviewed the PR

[jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected

2016-09-28 Thread David Yan (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530908#comment-15530908 ] David Yan commented on APEXMALHAR-2272: --- Please fix the spelling in "sequencial

Re: Automated changes git author

2016-09-28 Thread Vlad Rozov
Apex Dev? On 9/28/16 13:41, Sandesh Hegde wrote: BigFoot? On Wed, Sep 28, 2016 at 1:20 PM Thomas Weise wrote: What about the name "CI Support"? Does not look like best fit either. Any better ideas or keep it? I will document the outcome in the contributor guidelines. On Wed, Sep 28, 2016 a

Re: Automated changes git author

2016-09-28 Thread Pramod Immaneni
The dev email you suggested for email sounds good. How about "Apex Dev" for name? > On Sep 28, 2016, at 4:20 PM, Thomas Weise wrote: > > What about the name "CI Support"? Does not look like best fit either. Any > better ideas or keep it? > > I will document the outcome in the contributor guidelin

Re: Automated changes git author

2016-09-28 Thread Sandesh Hegde
BigFoot? On Wed, Sep 28, 2016 at 1:20 PM Thomas Weise wrote: > What about the name "CI Support"? Does not look like best fit either. Any > better ideas or keep it? > > I will document the outcome in the contributor guidelines. > > On Wed, Sep 28, 2016 at 11:13 AM, Pramod Immaneni > wrote: > > >

Re: Automated changes git author

2016-09-28 Thread Thomas Weise
What about the name "CI Support"? Does not look like best fit either. Any better ideas or keep it? I will document the outcome in the contributor guidelines. On Wed, Sep 28, 2016 at 11:13 AM, Pramod Immaneni wrote: > What trustworthy jenkins no more. Kidding aside +1 > > On Wed, Sep 28, 2016 at

[GitHub] apex-malhar pull request #433: japicmp 0.9.0

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

Re: Automated changes git author

2016-09-28 Thread Pramod Immaneni
What trustworthy jenkins no more. Kidding aside +1 On Wed, Sep 28, 2016 at 11:34 AM, Thomas Weise wrote: > Hi, > > For changes made by scripts, there has been an undocumented convention to > use the following author information (example): > > commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca > Aut

Travis CI build failing

2016-09-28 Thread Chinmay Kolhatkar
Hi All, I'm getting a weird error in travis CI build related to connection to repository. https://s3.amazonaws.com/archive.travis-ci.org/jobs/163438909/log.txt Error is as following: Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on project ma

[jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected

2016-09-28 Thread Munagala V. Ramanath (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530098#comment-15530098 ] Munagala V. Ramanath commented on APEXMALHAR-2272: -- Guess not -- nex

[jira] [Assigned] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected

2016-09-28 Thread Yogi Devendra (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yogi Devendra reassigned APEXMALHAR-2272: - Assignee: Yogi Devendra > sequencialFileRead property on FSInputModule not f

Re: Automated changes git author

2016-09-28 Thread Vlad Rozov
+1 and making it a documented convention. Vlad On 9/28/16 08:34, Thomas Weise wrote: Hi, For changes made by scripts, there has been an undocumented convention to use the following author information (example): commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca Author: CI Support Date: Mon Se

[jira] [Updated] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected

2016-09-28 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2272: - Summary: sequencialFileRead property on FSInputModule not functioning as expected (w

[jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule is functioning as expected

2016-09-28 Thread Yogi Devendra (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530073#comment-15530073 ] Yogi Devendra commented on APEXMALHAR-2272: --- [~dtram] Is it OK if break bac

[jira] [Commented] (APEXMALHAR-1818) Integrate Calcite to support SQL

2016-09-28 Thread Chinmay Kolhatkar (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530008#comment-15530008 ] Chinmay Kolhatkar commented on APEXMALHAR-1818: --- Hi [~julianhyde], Than

Re: Automated changes git author

2016-09-28 Thread Aniruddha Thombare
+1 on switching from jenk...@datatorrent.com. Is it possible to have c...@apex.apache.org? Or no-reply@apex...? Thanks, A _ Sent with difficulty, I mean handheld ;) On 28 Sep 2016 9:04 pm, "Thomas Weise" wrote: > Hi, > > For changes made by scripts, there

Re: Automated changes git author

2016-09-28 Thread David Yan
+1 On Sep 28, 2016 8:34 AM, "Thomas Weise" wrote: > Hi, > > For changes made by scripts, there has been an undocumented convention to > use the following author information (example): > > commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca > Author: CI Support > Date: Mon Sep 26 20:36:22 2016 -07

Automated changes git author

2016-09-28 Thread Thomas Weise
Hi, For changes made by scripts, there has been an undocumented convention to use the following author information (example): commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca Author: CI Support Date: Mon Sep 26 20:36:22 2016 -0700 Fix trailing whitespace. I would suggest we discontinue us

Re: APEXMALHAR-1818 : Apex-Calcite Integration

2016-09-28 Thread Chinmay Kolhatkar
Dear Community, I've created a review only PR for first phase of calcite integration. https://github.com/apache/apex-malhar/pull/432 Features implemented this PR are as follows: 1. SELECT STATEMENT 2. INSERT STATEMENT 3. INNER JOIN with non-empty equi join condition 4. WHERE clause 5. SCALAR func

[GitHub] apex-malhar pull request #433: japicmp 0.9.0

2016-09-28 Thread tweise
GitHub user tweise opened a pull request: https://github.com/apache/apex-malhar/pull/433 japicmp 0.9.0 @vrozov please merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/apex-malhar japicmp Alternatively you can review a

[GitHub] apex-malhar pull request #432: [Review Only] SQL Support for converting give...

2016-09-28 Thread chinmaykolhatkar
GitHub user chinmaykolhatkar opened a pull request: https://github.com/apache/apex-malhar/pull/432 [Review Only] SQL Support for converting given SQL statement to APEX DAG Features implemented are: 1. SELECT STATEMENT 2. INSERT STATEMENT 3. INNER JOIN with non-empty equi

[jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule is functioning as expected

2016-09-28 Thread Munagala V. Ramanath (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529874#comment-15529874 ] Munagala V. Ramanath commented on APEXMALHAR-2272: -- sequencial => se

[jira] [Created] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule is functioning as expected

2016-09-28 Thread Yogi Devendra (JIRA)
Yogi Devendra created APEXMALHAR-2272: - Summary: sequencialFileRead property on FSInputModule is functioning as expected Key: APEXMALHAR-2272 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2272