[jira] [Created] (APEXMALHAR-2164) Add documentation and examples for JMSInputOperator

Sanjay M Pujare created APEXMALHAR-2164: --- Summary: Add documentation and examples for JMSInputOperator Key: APEXMALHAR-2164 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2164 Project:

[jira] [Commented] (APEXMALHAR-2156) JMS Input operator enhancements

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

[jira] [Commented] (APEXMALHAR-2156) JMS Input operator enhancements

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

[GitHub] apex-malhar pull request #347: APEXMALHAR-2156 changes

GitHub user sanjaypujare reopened a pull request: https://github.com/apache/apex-malhar/pull/347 APEXMALHAR-2156 changes APEXMALHAR-2156 changes: @PramodSSImmaneni @amberarrow @ashwinchandrap pls review. You can merge this pull request into a Git repository by running: $

[GitHub] apex-malhar pull request #347: APEXMALHAR-2156 changes

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

Re: Bleeding edge branch ?

Can we create JIRAs for the issues we are facing by staying with the older versions and link them to a story JIRA. If we know the particulars of all the problems we might be able to chart a more finer grained course. Thanks On Wed, Jul 20, 2016 at 10:56 AM, Pradeep A. Dalvi

Re: Bleeding edge branch ?

I agree with Sandesh on following. The official branch from where releases are cut, shall continue taking EOL into consideration. However we also need to be prepared wrt future releases of Hadoop. --prad On Wed, Jul 20, 2016 at 10:43 AM, Sandesh Hegde wrote: > @Amol >

Re: Bleeding edge branch ?

@Amol EOL is important for master branch. To start the work on next version of Hadoop on different branch ( let us call that master++ ), we should not worry about the EOL. Eventually, master++ becomes master and the master++ will continue on the later version of the Hadoop. On Wed, Jul 20,

Re: Bleeding edge branch ?

Ok, whether branches or forks. I still think we should have at least some materialized version of malhar/core for the big influencer like java, hadoop or even kafka. Java 8, for example, is actually not new. We don't have to be aggressive to try out new features from those right now. But we can

Re: Bleeding edge branch ?

Sandesh, Not worrying about EOL is a big deal. It creates problems for current users, and also sends a message to new users (pre-adoption) on how we will take care of them. Two branches, etc. need to be thought through by all of us in terms of our ability to support. IMHO, we are rushing on this

[jira] [Commented] (APEXMALHAR-2157) Improvements in JSON Formatter

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

[GitHub] apex-malhar pull request #348: APEXMALHAR-2157 Json formatter improvements

Github user devtagare commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/348#discussion_r71555740 --- Diff: library/src/test/java/com/datatorrent/lib/formatter/JsonFormatterTest.java --- @@ -35,6 +35,8 @@ import

[jira] [Commented] (APEXMALHAR-2157) Improvements in JSON Formatter

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

[jira] [Commented] (APEXMALHAR-2157) Improvements in JSON Formatter

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

[jira] [Commented] (APEXMALHAR-2157) Improvements in JSON Formatter

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

[jira] [Commented] (APEXMALHAR-2157) Improvements in JSON Formatter

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

Re: Bleeding edge branch ?

Our current model of supporting the oldest supported Hadoop, penalizes the users of latest Hadoop versions by favoring the slow movers. Also, we won't benefit from the increased maturity of the Hadoop platform, as we will be working on the many years old version of Hadoop. We also need to

Re: Container & memory resource allocation

I've verified 'multiples of minimum-allocation-mb' on latest Apex. However 'increment-allocation-mb' was not set during that exercise. I shall check that param as well. Thanks, --prad On Wednesday, July 20, 2016, Munagala Ramanath wrote: > Please note that there are

Re: Container & memory resource allocation

Please note that there are multiple sites making the claim that memory allocation is in multiples of *yarn.scheduler.minimum-allocation-mb*; this may have been true at one time but is no longer true (thanks to Sandesh for fact-checking this). There is a (?new?) parameter,

Re: Using DSL api to construct sql queries

It is a good idea to get rid of vendor specific implementation differences for SQL. However, the licensing does not seem to be straightforward. Please check: http://www.jooq.org/legal/licensing. Can this be used as a dependency in Apex? ~ Bhupesh On Wed, Jul 20, 2016 at 3:06 AM, Priyanka Gugale

[GitHub] apex-malhar pull request #349: APEXMALHAR-2138: Removed multiple declaration...

GitHub user harsh306 opened a pull request: https://github.com/apache/apex-malhar/pull/349 APEXMALHAR-2138: Removed multiple declarations of mockito lib. You can merge this pull request into a Git repository by running: $ git pull https://github.com/harsh306/apex-malhar

[jira] [Created] (APEXMALHAR-2163) User query dsl api to construct SQL query

Priyanka Gugale created APEXMALHAR-2163: --- Summary: User query dsl api to construct SQL query Key: APEXMALHAR-2163 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2163 Project: Apache Apex

[jira] [Commented] (APEXMALHAR-2157) Improvements in JSON Formatter

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

[GitHub] apex-malhar pull request #348: APEXMALHAR-2157 Json formatter improvements

GitHub user shubham-pathak22 opened a pull request: https://github.com/apache/apex-malhar/pull/348 APEXMALHAR-2157 Json formatter improvements You can merge this pull request into a Git repository by running: $ git pull