Re: [DISCUSS] changing project name to apex-library

The gain is consistency and meeting/setting up expectations on the project quality/maturity. Thank you, Vlad On 8/24/17 09:42, Amol Kekre wrote: In terms of rebasing versions, there is no urgency in mimic-ing some of the other projects. Apex has already be been versioned. What functional

Re: [DISCUSS] changing project name to apex-library

On Thu, Aug 24, 2017 at 9:42 AM, Amol Kekre wrote: > In terms of rebasing versions, there is no urgency in mimic-ing some of the > other projects. Apex has already be been versioned. There is an expectation users have for a version number, which is different for 3.x or

Re: -1 or veto voting

For -1 to be valid there *must* be *technical* justification(s) not to proceed with the code change. Without such justification -1 is considered to be void/invalid [1]. I don't see any possible *technical* justification not to proceed with the package rename as it was done in the past by a

Re: [DISCUSS] changing project name to apex-library

In terms of rebasing versions, there is no urgency in mimic-ing some of the other projects. Apex has already be been versioned. What functional gain do we have by changing versions, names? Functionality wise Apex users do not gain anything. With regards to bumping to 4.X, we should wait for a

Re: -1 or veto voting

Today, I saw the below -1 by Thomas, https://github.com/apache/apex-malhar/pull/666 without the technical justification. Saumya, PR Author, has created a mail thread to discuss the justification, but there was no comment in the mail thread. So should we consider this as invalid -1? On Thu, Aug

Re: Adding Avro Module to encapsulate AvroFileInput Operator and AvroToPojo Operator

I see no reason to create a separate Maven project along with this change. The new classes can be added to the contrib module (under org.apache.apex), as @Evolving. The Maven project should be discussed separately and I would look for an explanation why it makes sense as such, overall

Re: -1 or veto voting

Justification is to not mingle small changes with refactoring and not perform refactoring of this kind without adequate discussion. Both was already conveyed on current PR and previous PR. You did the right thing declaring your intent to merge without just pulling the trigger, but you also need

[jira] [Created] (APEXMALHAR-2538) Enhance Apex Kudu Support for Streaming SQL API

Ananth created APEXMALHAR-2538: -- Summary: Enhance Apex Kudu Support for Streaming SQL API Key: APEXMALHAR-2538 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2538 Project: Apache Apex Malhar

Re: [Design discussion] - Kudu Input operator

Hello Thomas, Thanks for the additional comments. Replies inline marked [Ananth]>>> Regards, Ananth > On 22 Aug 2017, at 2:10 pm, Thomas Weise wrote: > > --> > > Thanks, > Thomas > > > On Sat, Aug 19, 2017 at 2:07 PM, Ananth G

[jira] [Commented] (APEXCORE-775) StramClientUtils.getApexDFSRootDir() incorrectly sets DT_DFS_ROOT_DIR in the configuration object

[ https://issues.apache.org/jira/browse/APEXCORE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140980#comment-16140980 ] ASF GitHub Bot commented on APEXCORE-775: - sanjaypujare opened a new pull request #569:

[jira] [Commented] (APEXCORE-775) StramClientUtils.getApexDFSRootDir() incorrectly sets DT_DFS_ROOT_DIR in the configuration object

[ https://issues.apache.org/jira/browse/APEXCORE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140979#comment-16140979 ] ASF GitHub Bot commented on APEXCORE-775: - sanjaypujare closed pull request #569: APEXCORE-775

[jira] [Commented] (APEXCORE-775) StramClientUtils.getApexDFSRootDir() incorrectly sets DT_DFS_ROOT_DIR in the configuration object

[ https://issues.apache.org/jira/browse/APEXCORE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141001#comment-16141001 ] ASF GitHub Bot commented on APEXCORE-775: - sanjaypujare closed pull request #569: APEXCORE-775

[jira] [Commented] (APEXCORE-775) StramClientUtils.getApexDFSRootDir() incorrectly sets DT_DFS_ROOT_DIR in the configuration object

[ https://issues.apache.org/jira/browse/APEXCORE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141002#comment-16141002 ] ASF GitHub Bot commented on APEXCORE-775: - sanjaypujare opened a new pull request #569:

[jira] [Commented] (APEXCORE-775) StramClientUtils.getApexDFSRootDir() incorrectly sets DT_DFS_ROOT_DIR in the configuration object

[ https://issues.apache.org/jira/browse/APEXCORE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141229#comment-16141229 ] ASF GitHub Bot commented on APEXCORE-775: - sanjaypujare closed pull request #569: APEXCORE-775

[jira] [Commented] (APEXCORE-775) StramClientUtils.getApexDFSRootDir() incorrectly sets DT_DFS_ROOT_DIR in the configuration object

[ https://issues.apache.org/jira/browse/APEXCORE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141230#comment-16141230 ] ASF GitHub Bot commented on APEXCORE-775: - sanjaypujare opened a new pull request #569: