Re: [RESULT] [VOTE] Major version change for Apex Library (Malhar)

I totally agree with Sandesh. Things are being pushed when there is clear disagreement. If Apex has to grow the community, it can't grow using divide and conquer method. On Fri, Sep 1, 2017 at 10:45 PM, Sandesh Hegde wrote: > Using all the technicalities and loop holes,

Re: [VOTE] Major version change for Apex Library (Malhar)

-1 from my side for "1. Version 4.0 as major version change from 3.x" Was out of station for festival season in India so delay in voting and replying. Reason: I don't see a compelling reason for a major change at this moment. As a user of Apex, I have developed a system using Apex but now I

[jira] [Commented] (APEXMALHAR-2365) LogParser - Operator to parse byte array using log format and emit a POJO

[ https://issues.apache.org/jira/browse/APEXMALHAR-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714919#comment-15714919 ] Sandeep Deshmukh commented on APEXMALHAR-2365: -- Can someone from PMC list assign

Re: Questions regarding R operator

Hi Ananth, Please see my answers in-line Regards, Sandeep On Thu, Oct 27, 2016 at 11:52 PM, ananth wrote: > Hello all, > > I want to use Apex for executing R scripts wherein the parameters for the > script are coming in as tuples. In this regard, I have a few

Re: S3 Output Module

+1 Regards, Sandeep On Thu, Oct 27, 2016 at 1:53 PM, Chaitanya Chebolu < chaita...@datatorrent.com> wrote: > Hi All, > > I am planning to implement the approach (2) of S3 Output Module which I > proposed in my previous email. Performance would be better as compared to > approach (1) because

Re: Kudu store operators

+1 Regards, Sandeep On Mon, Oct 3, 2016 at 10:16 AM, Tushar Gosavi wrote: > +1, It will be great to have this operator. > > - Tushar. > > On Mon, Oct 3, 2016 at 8:15 AM, Chinmay Kolhatkar > wrote: > > +1. > > > > - Chinmay. > > > > On 3 Oct

[jira] [Updated] (APEXMALHAR-1953) Add generic (insert, update, delete) support to JDBC Output Operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Deshmukh updated APEXMALHAR-1953: - Fix Version/s: 3.5.0 > Add generic (insert, update, delete) support to J

Re: Should YARN_APPLICATION_TYPE be changed to ApacheApex from DataTorrent

Yes, good idea. Will that be a backward compatible change? I think, we should wait for 4.0. On Thu, Jun 23, 2016 at 1:44 PM, Aniruddha Thombare < anirud...@datatorrent.com> wrote: > Hi, > > StramClient.java still refers the yarn application type to be > "DataTorrent". > Should it be ApacheApex?

Listing Apex under hadoop-related projects on hadoop page

Hi All, Hadoop main page http://hadoop.apache.org/ lists hadoop-related projects. Apex being hadoop native should also be listed there. Can we explore option to be listed there? Regards, Sandeep

Re: [ANNOUNCE] New Apache Apex PMC Member: Siyuan Hua

Congrats Siyuan !!! Regards, Sandeep On Thu, Jun 16, 2016 at 10:49 AM, Aniruddha Thombare < anirud...@datatorrent.com> wrote: > Congratulations!!! > > Thanks, > > A > > _ > Sent with difficulty, I mean handheld ;) > On 16 Jun 2016 10:47 am, "Devendra Tagare"

[jira] [Commented] (APEXMALHAR-2113) JdbcPOJOOutputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320205#comment-15320205 ] Sandeep Deshmukh commented on APEXMALHAR-2113: -- It would be good to update title

Compilation error while updating dependency to malhar 3.4.0

Hi All, We had developed an application using AbstractKafkaInputOperator from Malhar 3.2.0-incubator. We are planning to upgrade to Malhar 3.4.0. While recompiling our code, we observed that the compilation fails due to backward incompatible change in the AbstractKafkaInputOperator. The

Re: [VOTE] Apache Apex Malhar Release 3.4.0 (RC1)

+1 Checked for: - Signature verification - No bin files bundled in the source distribution - Rat check & build passed - Ran pi demo on Apex 3.4.0 I will open a PR to update verification guidelines to remove disclaimer. Regards Sandeep Regards, Sandeep On Mon, May 23, 2016 at 10:24 AM, Tushar