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!!
> >
> >
+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
Venkatesh Kottapalli created APEXMALHAR-2479:
Summary: Create example for RegexParser operator
Key: APEXMALHAR-2479
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2479
Project
[
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
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
[
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
[
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
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
[
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
[
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
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
[
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
+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
[
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
[
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
[
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
[
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
[
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
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
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
[
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
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
[
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
[
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
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
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,
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
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
28 matches
Mail list logo