[jira] [Created] (APEXCORE-517) ApexCli is not working with Hadoop web services when BASIC authentication enabled is enabled

Pramod Immaneni created APEXCORE-517: Summary: ApexCli is not working with Hadoop web services when BASIC authentication enabled is enabled Key: APEXCORE-517 URL: https://issues.apache.org/jira/browse/APEXCORE

[jira] [Created] (APEXCORE-519) Add support for DIGEST enabled hadoop web services environment

Pramod Immaneni created APEXCORE-519: Summary: Add support for DIGEST enabled hadoop web services environment Key: APEXCORE-519 URL: https://issues.apache.org/jira/browse/APEXCORE-519 Project: Apa

[jira] [Closed] (APEXCORE-520) Add support for DIGEST enabled hadoop web services environment

[ https://issues.apache.org/jira/browse/APEXCORE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni closed APEXCORE-520. Resolution: Duplicate > Add support for DIGEST enabled hadoop web services environment > -

[jira] [Created] (APEXCORE-520) Add support for DIGEST enabled hadoop web services environment

Pramod Immaneni created APEXCORE-520: Summary: Add support for DIGEST enabled hadoop web services environment Key: APEXCORE-520 URL: https://issues.apache.org/jira/browse/APEXCORE-520 Project: Apa

[jira] [Updated] (APEXMALHAR-2017) Use pre checkpoint notification to optimize operator IO

[ https://issues.apache.org/jira/browse/APEXMALHAR-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXMALHAR-2017: Assignee: Velineni Lakshmi Prasanna (was: Pramod Immaneni) > Use pre checkpoin

[jira] [Commented] (APEXCORE-532) New dynamically added operator does not start with correct windowId.

[ https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490587#comment-15490587 ] Pramod Immaneni commented on APEXCORE-532: -- Does the DAG have other operators o

[jira] [Commented] (APEXCORE-532) New dynamically added operator does not start with correct windowId.

[ https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490615#comment-15490615 ] Pramod Immaneni commented on APEXCORE-532: -- Let me try a couple of things and g

[jira] [Resolved] (APEXCORE-517) ApexCli is not working with Hadoop web services when BASIC authentication is enabled

[ https://issues.apache.org/jira/browse/APEXCORE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-517. -- Resolution: Fixed > ApexCli is not working with Hadoop web services when BASIC authent

[jira] [Created] (APEXMALHAR-2254) File input operator is not idempotent with closing files on replay

Pramod Immaneni created APEXMALHAR-2254: --- Summary: File input operator is not idempotent with closing files on replay Key: APEXMALHAR-2254 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2254

[jira] [Updated] (APEXMALHAR-2254) File input operator is not idempotent with closing files on replay

[ https://issues.apache.org/jira/browse/APEXMALHAR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXMALHAR-2254: Description: With the file input operator, on a replay in a failure scenario, t

[jira] [Commented] (APEXCORE-532) New dynamically added operator does not start with correct windowId.

[ https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514071#comment-15514071 ] Pramod Immaneni commented on APEXCORE-532: -- [~tushargosavi] checking why this i

[jira] [Commented] (APEXCORE-548) ApexCLI does not correctly detect running applications with the same name at launch time

[ https://issues.apache.org/jira/browse/APEXCORE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550024#comment-15550024 ] Pramod Immaneni commented on APEXCORE-548: -- Wouldn't getDisplayName return the

[jira] [Commented] (APEXCORE-548) ApexCLI does not correctly detect running applications with the same name at launch time

[ https://issues.apache.org/jira/browse/APEXCORE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550065#comment-15550065 ] Pramod Immaneni commented on APEXCORE-548: -- Looks like getAppAlias looks at bot

[jira] [Commented] (APEXCORE-548) ApexCLI does not correctly detect running applications with the same name at launch time

[ https://issues.apache.org/jira/browse/APEXCORE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550141#comment-15550141 ] Pramod Immaneni commented on APEXCORE-548: -- I was thinking about that approach

[jira] [Commented] (APEXMALHAR-2263) Offsets in AbstractFileInputOperator should be long rather than int

[ https://issues.apache.org/jira/browse/APEXMALHAR-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583598#comment-15583598 ] Pramod Immaneni commented on APEXMALHAR-2263: - Why can't we have both the

[jira] [Resolved] (APEXMALHAR-2269) AbstractFileInputOperator: During replay, IO errors not handled

[ https://issues.apache.org/jira/browse/APEXMALHAR-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXMALHAR-2269. - Resolution: REMIND For idempotency the failureHandling() method that processe

[jira] [Resolved] (APEXMALHAR-2270) AbstractFileInputOperator: During replay, inputStream should skip tuples

[ https://issues.apache.org/jira/browse/APEXMALHAR-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXMALHAR-2270. - Resolution: Fixed > AbstractFileInputOperator: During replay, inputStream sho

[jira] [Resolved] (APEXMALHAR-2254) File input operator is not idempotent with closing files on replay

[ https://issues.apache.org/jira/browse/APEXMALHAR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXMALHAR-2254. - Resolution: Fixed > File input operator is not idempotent with closing files

[jira] [Created] (APEXMALHAR-2324) Add support for flume

Pramod Immaneni created APEXMALHAR-2324: --- Summary: Add support for flume Key: APEXMALHAR-2324 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2324 Project: Apache Apex Malhar Issu

[jira] [Updated] (APEXMALHAR-2324) Add support for flume

[ https://issues.apache.org/jira/browse/APEXMALHAR-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXMALHAR-2324: Description: Flume support and operators are available in Megh project that Dat

[jira] [Updated] (APEXMALHAR-2324) Add support for flume

[ https://issues.apache.org/jira/browse/APEXMALHAR-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXMALHAR-2324: Description: Flume support and operators are available in Megh project that Dat

[jira] [Created] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

Pramod Immaneni created APEXCORE-570: Summary: Prevent upstream operators from getting too far ahead when downstream operators are slow Key: APEXCORE-570 URL: https://issues.apache.org/jira/browse/APEXCORE-570

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628460#comment-15628460 ] Pramod Immaneni commented on APEXCORE-570: -- Here is an example on how to do thi

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630269#comment-15630269 ] Pramod Immaneni commented on APEXCORE-570: -- For the inter-process case, if the

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630806#comment-15630806 ] Pramod Immaneni commented on APEXCORE-570: -- [~davidyan] that would lead to dead

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649116#comment-15649116 ] Pramod Immaneni commented on APEXCORE-570: -- Also will look at how disabling buf

[jira] [Created] (APEXCORE-574) Operator requests sent by a stats listener are being lost sometimes

Pramod Immaneni created APEXCORE-574: Summary: Operator requests sent by a stats listener are being lost sometimes Key: APEXCORE-574 URL: https://issues.apache.org/jira/browse/APEXCORE-574 Project

[jira] [Resolved] (APEXCORE-574) Operator requests sent by a stats listener are being lost sometimes

[ https://issues.apache.org/jira/browse/APEXCORE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-574. -- Resolution: Invalid This was filed because of a misunderstanding of how the mechanism

[jira] [Created] (APEXMALHAR-2355) Filter POJO operator is missing schema annotation on the output ports

Pramod Immaneni created APEXMALHAR-2355: --- Summary: Filter POJO operator is missing schema annotation on the output ports Key: APEXMALHAR-2355 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2355

[jira] [Commented] (APEXCORE-558) Do not use yellow color to display command strings in help output

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729585#comment-15729585 ] Pramod Immaneni commented on APEXCORE-558: -- Red typically means something is wr

[jira] [Commented] (APEXCORE-577) Visitor API for DAG

[ https://issues.apache.org/jira/browse/APEXCORE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729596#comment-15729596 ] Pramod Immaneni commented on APEXCORE-577: -- Why specifically limit it to client

[jira] [Commented] (APEXCORE-587) Allow access to DAG through the Launcher API

[ https://issues.apache.org/jira/browse/APEXCORE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731038#comment-15731038 ] Pramod Immaneni commented on APEXCORE-587: -- Agree with both of you. But how abo

[jira] [Updated] (APEXCORE-587) Allow access to DAG through the Launcher API

[ https://issues.apache.org/jira/browse/APEXCORE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-587: - Assignee: Pramod Immaneni > Allow access to DAG through the Launcher API > -

[jira] [Commented] (APEXCORE-594) Investigate adding new functionality to apex through user plugins.

[ https://issues.apache.org/jira/browse/APEXCORE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767813#comment-15767813 ] Pramod Immaneni commented on APEXCORE-594: -- The idea is to provide hooks at dif

[jira] [Resolved] (APEXCORE-590) Failed to restart application on MapR

[ https://issues.apache.org/jira/browse/APEXCORE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-590. -- Resolution: Fixed > Failed to restart application on MapR > --

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823182#comment-15823182 ] Pramod Immaneni commented on APEXCORE-570: -- I am not sure what is left to concl

[jira] [Commented] (APEXCORE-609) Container runs out of memory when buffer spooling is disabled

[ https://issues.apache.org/jira/browse/APEXCORE-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823203#comment-15823203 ] Pramod Immaneni commented on APEXCORE-609: -- Today, when spooling is disabled, b

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823292#comment-15823292 ] Pramod Immaneni commented on APEXCORE-570: -- I will go into the topic specific c

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824455#comment-15824455 ] Pramod Immaneni commented on APEXCORE-570: -- "Consider the case of two subscribe

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824628#comment-15824628 ] Pramod Immaneni commented on APEXCORE-570: -- I see your point that you could dis

[jira] [Created] (APEXCORE-614) Upgrade beanutils version to 1.9.2

Pramod Immaneni created APEXCORE-614: Summary: Upgrade beanutils version to 1.9.2 Key: APEXCORE-614 URL: https://issues.apache.org/jira/browse/APEXCORE-614 Project: Apache Apex Core Issue

[jira] [Resolved] (APEXCORE-614) Upgrade beanutils version to 1.9.2

[ https://issues.apache.org/jira/browse/APEXCORE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-614. -- Resolution: Fixed Fix Version/s: 3.5.0 > Upgrade beanutils version to 1.9.2 > -

[jira] [Updated] (APEXCORE-614) Upgrade beanutils version to 1.9.2

[ https://issues.apache.org/jira/browse/APEXCORE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-614: - Issue Type: Improvement (was: Bug) > Upgrade beanutils version to 1.9.2 > -

[jira] [Commented] (APEXCORE-614) Upgrade beanutils version to 1.9.2

[ https://issues.apache.org/jira/browse/APEXCORE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830240#comment-15830240 ] Pramod Immaneni commented on APEXCORE-614: -- https://github.com/apache/apex-core

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

[ https://issues.apache.org/jira/browse/APEXCORE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-616: Assignee: Pramod Immaneni > Application fails to launch on Kerberised cluster > -

[jira] [Created] (APEXCORE-636) Ability to refresh tokens using user's own kerberos credentials in a managed environment where the application is launched using an admin with impersonation

Pramod Immaneni created APEXCORE-636: Summary: Ability to refresh tokens using user's own kerberos  credentials in a managed environment where the application is launched using an admin with impersonation Key: APEXCORE-636

[jira] [Assigned] (APEXCORE-636) Ability to refresh tokens using user's own kerberos credentials in a managed environment where the application is launched using an admin with impersonation

[ https://issues.apache.org/jira/browse/APEXCORE-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-636: Assignee: devendra tagare > Ability to refresh tokens using user's own kerberos c

[jira] [Created] (APEXCORE-646) Allow back pressure to be configurable on a per stream basis

Pramod Immaneni created APEXCORE-646: Summary: Allow back pressure to be configurable on a per stream basis Key: APEXCORE-646 URL: https://issues.apache.org/jira/browse/APEXCORE-646 Project: Apach

[jira] [Commented] (APEXCORE-467) BufferServer should not be deployed in the containers with only Output operators

[ https://issues.apache.org/jira/browse/APEXCORE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298490#comment-15298490 ] Pramod Immaneni commented on APEXCORE-467: -- Remember that dynamic plan changes

[jira] [Resolved] (APEXCORE-460) Token refresh mechanism not considering keytab specified in command line

[ https://issues.apache.org/jira/browse/APEXCORE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-460. -- Resolution: Fixed > Token refresh mechanism not considering keytab specified in comman

[jira] [Comment Edited] (APEXCORE-339) Support ability to tag operators as idempotent or non-idempotent

[ https://issues.apache.org/jira/browse/APEXCORE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225223#comment-15225223 ] Pramod Immaneni edited comment on APEXCORE-339 at 6/7/16 10:54 PM: ---

[jira] [Commented] (APEXCORE-222) Delegate Buffer Server purge to StreamingContainer

[ https://issues.apache.org/jira/browse/APEXCORE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330654#comment-15330654 ] Pramod Immaneni commented on APEXCORE-222: -- Shouldn't this be an option because

<    1   2   3