Re: [ANNOUNCE] New Apache Apex PMC: Tushar Gosavi

2017-11-03 Thread Venkatesh Kottapalli
Congratulations Tushar! -Venky On Fri, Nov 3, 2017 at 9:24 AM Hitesh Kapoor wrote: > Congratulations Tushar. > > Regards, > Hitesh Kapoor > > On 03-Nov-2017 9:53 PM, "Ashwin Chandra Putta" > wrote: > > > Congratulations Tushar!! > > > >

Re: Specialized operator recovery

2017-04-24 Thread Venkatesh Kottapalli
+1 for this feature to explicitly identify operators for specialized operator recovery as in Pramod’s email. Don’t think that this can be made default. From my understanding, by default, this can guarantee ATLEAST_ONCE and not EXACTLY_ONCE in the downstream of failed container as the stream is

[jira] [Created] (APEXMALHAR-2479) Create example for RegexParser operator

2017-04-18 Thread Venkatesh Kottapalli (JIRA)
Venkatesh Kottapalli created APEXMALHAR-2479: Summary: Create example for RegexParser operator Key: APEXMALHAR-2479 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2479 Project

[jira] [Commented] (APEXMALHAR-2250) AbstractFileInputOperator.DirectoryScanner does not handle directories correctly.

2017-04-11 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965048#comment-15965048 ] Venkatesh Kottapalli commented on APEXMALHAR-2250: -- [~tushargosavi] Can I pick

[jira] [Created] (APEXMALHAR-2454) CsvParser documentation xml formatting and rendering issue.

2017-03-22 Thread Venkatesh Kottapalli (JIRA)
Venkatesh Kottapalli created APEXMALHAR-2454: Summary: CsvParser documentation xml formatting and rendering issue. Key: APEXMALHAR-2454 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2454

[jira] [Resolved] (APEXMALHAR-2218) RegexParser- Operator to parse byte stream using Regex pattern and emit a POJO

2017-02-27 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli resolved APEXMALHAR-2218. -- Resolution: Fixed Merged. > RegexParser- Operator to parse b

[jira] [Updated] (APEXMALHAR-2218) RegexParser- Operator to parse byte stream using Regex pattern and emit a POJO

2017-02-27 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli updated APEXMALHAR-2218: - Fix Version/s: 3.7.0 Issue Type: New Feature

[jira] [Created] (APEXMALHAR-2426) Add user document for RegexParser operator

2017-02-24 Thread Venkatesh Kottapalli (JIRA)
Venkatesh Kottapalli created APEXMALHAR-2426: Summary: Add user document for RegexParser operator Key: APEXMALHAR-2426 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2426 Project

[jira] [Updated] (APEXMALHAR-2218) RegexParser- Operator to parse byte stream using Regex pattern and emit a POJO

2017-02-24 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli updated APEXMALHAR-2218: - Summary: RegexParser- Operator to parse byte stream using Regex

[jira] [Updated] (APEXCORE-616) Application fails to start Kerberised cluster

2017-01-20 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli updated APEXCORE-616: -- Summary: Application fails to start Kerberised cluster (was: Application

[jira] [Created] (APEXCORE-616) Application fails to launch on Kerberised cluster

2017-01-20 Thread Venkatesh Kottapalli (JIRA)
Venkatesh Kottapalli created APEXCORE-616: - Summary: Application fails to launch on Kerberised cluster Key: APEXCORE-616 URL: https://issues.apache.org/jira/browse/APEXCORE-616 Project: Apache

[jira] [Comment Edited] (APEXCORE-471) Requests for container allocation are not resubmitted

2016-11-09 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15652496#comment-15652496 ] Venkatesh Kottapalli edited comment on APEXCORE-471 at 11/10/16 12:28 AM

Re: checkpoint statistics

2016-09-26 Thread Venkatesh Kottapalli
+1 for this feature. The size and time to checkpoint the state at operator level will help in tuning and understanding the overheads if any. -Venkatesh. > On Sep 25, 2016, at 10:56 PM, Chinmay Kolhatkar > wrote: > > +1. very useful feature. We should also provide

[jira] [Comment Edited] (APEXMALHAR-2241) The metadata kafka consumer should also pickup the properties setting on the kafka input operator.

2016-09-16 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496849#comment-15496849 ] Venkatesh Kottapalli edited comment on APEXMALHAR-2241 at 9/16/16 5:14 PM

[jira] [Commented] (APEXMALHAR-2241) The metadata kafka consumer should also pickup the properties setting on the kafka input operator.

2016-09-16 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496849#comment-15496849 ] Venkatesh Kottapalli commented on APEXMALHAR-2241: -- Sure Siyuan. I will set

[jira] [Updated] (APEXMALHAR-2239) Null pointer exception in JDBCPojoInputOperator when the field names do not match in Pojo, table

2016-09-15 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli updated APEXMALHAR-2239: - Description: The following exception is thrown

[jira] [Updated] (APEXMALHAR-2239) Null pointer exception in JDBCPojoInputOperator when the field names do not match in Pojo, table

2016-09-15 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli updated APEXMALHAR-2239: - Summary: Null pointer exception in JDBCPojoInputOperator when

[jira] [Updated] (APEXMALHAR-2239) Null pointer exception in JDBCInputOperator when the field names do not match in Pojo, table

2016-09-15 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli updated APEXMALHAR-2239: - Description: The following exception is thrown when the field names

[jira] [Created] (APEXMALHAR-2239) Null pointer exception in JDBCInputOperator when the field names do not match in Pojo, table

2016-09-15 Thread Venkatesh Kottapalli (JIRA)
Venkatesh Kottapalli created APEXMALHAR-2239: Summary: Null pointer exception in JDBCInputOperator when the field names do not match in Pojo, table Key: APEXMALHAR-2239 URL: https://issues.apache.org

Re: [ANNOUNCE] New Apache Apex PMC Member: Chandni Singh

2016-09-12 Thread Venkatesh Kottapalli
Congrats Chandini! -Venkatesh. > On Sep 12, 2016, at 10:48 AM, Sandesh Hegde wrote: > > Congratulations Chandni > > On Mon, Sep 12, 2016 at 10:46 AM Shubham Pathak > wrote: > >> Congratulations Chandni !! >> >> Thanks, >> Shubham >> >> On

[jira] [Updated] (APEXMALHAR-2218) RegexSplitter - Operator to parse byte stream using Regex pattern and emit a POJO

2016-08-31 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli updated APEXMALHAR-2218: - Description: A generic parser which takes the regex pattern

[jira] [Created] (APEXMALHAR-2218) RegexSplitter - Operator to parse byte stream using Regex pattern and emit a POJO

2016-08-31 Thread Venkatesh Kottapalli (JIRA)
Venkatesh Kottapalli created APEXMALHAR-2218: Summary: RegexSplitter - Operator to parse byte stream using Regex pattern and emit a POJO Key: APEXMALHAR-2218 URL: https://issues.apache.org/jira/browse

[jira] [Commented] (APEXCORE-475) change the YARN_APPLICATION_TYPE from DataTorrent to ApacheApex

2016-08-30 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450039#comment-15450039 ] Venkatesh Kottapalli commented on APEXCORE-475: --- Apologies for commenting so late

[jira] [Assigned] (APEXMALHAR-2183) Add user document for CsvFormatter operator

2016-08-24 Thread Venkatesh Kottapalli (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli reassigned APEXMALHAR-2183: Assignee: Venkatesh Kottapalli > Add user docum

Re: Default value for tupleSeperator

2016-08-12 Thread Venkatesh Kottapalli
IMO, since we have an option to configure the line delimiter, leaving it to the user is a good idea as there might be cases where either one of them is used and not both. -Venkatesh. > On Aug 12, 2016, at 6:29 PM, Yogi Devendra wrote: > > Hi, > > Currently, for

Re: anti-affinity - parameter to control the containers of an operator on a node

2016-08-12 Thread Venkatesh Kottapalli
mory and CPU your > operator needs. The scheduler uses that information to find a suitable node > and it is already clear how many containers of an operator fit on a node. > > Maybe you are thinking of another resource that is not managed by YARN? > > Thomas > > On Wed,

[jira] [Created] (APEXMALHAR-2183) Add user document for CsvFormatter operator

2016-08-10 Thread Venkatesh Kottapalli (JIRA)
Venkatesh Kottapalli created APEXMALHAR-2183: Summary: Add user document for CsvFormatter operator Key: APEXMALHAR-2183 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2183 Project

anti-affinity - parameter to control the containers of an operator on a node

2016-08-10 Thread Venkatesh Kottapalli
Hi team, On the anti-affinity rules while deploying containers, do we have a feature which can control the number of containers of the same operator that get deployed on the same node. If the environment is capable of handling, then this will be a good feature to have as it is possible that