[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=15225223#comment-15225223 ] Pramod Immaneni edited comment on APEXCORE-339 at 6/7/16 10:54 PM: ---

[jira] [Resolved] (APEXCORE-214) Containers Fail With RPC Timeout

[ https://issues.apache.org/jira/browse/APEXCORE-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-214. -- Resolution: Implemented Already implemented with a setting to change timeout value >

[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=15298490#comment-15298490 ] Pramod Immaneni commented on APEXCORE-467: -- Remember that dynamic plan changes are supported so

[jira] [Commented] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

[ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389829#comment-15389829 ] Pramod Immaneni commented on APEXCORE-494: -- Can you outline the difference between this and

[jira] [Created] (APEXCORE-500) Allow specification of non-heap memory size

Pramod Immaneni created APEXCORE-500: Summary: Allow specification of non-heap memory size Key: APEXCORE-500 URL: https://issues.apache.org/jira/browse/APEXCORE-500 Project: Apache Apex Core

[jira] [Commented] (APEXCORE-505) setup and activate calls in operator block heartbeat loop in container

[ https://issues.apache.org/jira/browse/APEXCORE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419719#comment-15419719 ] Pramod Immaneni commented on APEXCORE-505: -- Taking a look at it > setup and activate calls in

[jira] [Created] (APEXCORE-483) Dependency to httpclient version 3.5 causing problem with newer versions of Hadoop

Pramod Immaneni created APEXCORE-483: Summary: Dependency to httpclient version 3.5 causing problem with newer versions of Hadoop Key: APEXCORE-483 URL: https://issues.apache.org/jira/browse/APEXCORE-483

[jira] [Commented] (APEXCORE-483) Dependency to httpclient version 3.5 causing problem with newer versions of Hadoop

[ https://issues.apache.org/jira/browse/APEXCORE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369382#comment-15369382 ] Pramod Immaneni commented on APEXCORE-483: -- To get this around the problem we will shade the

[jira] [Comment Edited] (APEXCORE-483) Dependency to httpclient version 3.5 causing problem with newer versions of Hadoop

[ https://issues.apache.org/jira/browse/APEXCORE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369382#comment-15369382 ] Pramod Immaneni edited comment on APEXCORE-483 at 7/10/16 1:57 AM: --- To

[jira] [Updated] (APEXCORE-483) Dependency to httpclient version 4.3.5 causing problem with newer versions of Hadoop

[ https://issues.apache.org/jira/browse/APEXCORE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-483: - Summary: Dependency to httpclient version 4.3.5 causing problem with newer versions of

[jira] [Commented] (APEXCORE-448) Make operator name available in OperatorContext

[ https://issues.apache.org/jira/browse/APEXCORE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390707#comment-15390707 ] Pramod Immaneni commented on APEXCORE-448: -- There is another attribute of such read-only ilk,

[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 

[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] [Resolved] (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 resolved APEXCORE-636. -- Resolution: Fixed > Ability to refresh tokens using user's own kerberos credentials

[jira] [Updated] (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 updated APEXCORE-636: - Fix Version/s: 3.6.0 > Ability to refresh tokens using user's own kerberos credentials

[jira] [Resolved] (APEXMALHAR-2394) AbstractFileOutputOperator.rotate(...) does not check if file has already been rotated before computing next rotation

[ https://issues.apache.org/jira/browse/APEXMALHAR-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXMALHAR-2394. - Resolution: Fixed > AbstractFileOutputOperator.rotate(...) does not check if

[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:

[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=15823203#comment-15823203 ] Pramod Immaneni commented on APEXCORE-609: -- Today, when spooling is disabled, because old data

[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=15824455#comment-15824455 ] Pramod Immaneni commented on APEXCORE-570: -- "Consider the case of two subscribers with same

[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=15824628#comment-15824628 ] Pramod Immaneni commented on APEXCORE-570: -- I see your point that you could disable back

[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=15823182#comment-15823182 ] Pramod Immaneni commented on APEXCORE-570: -- I am not sure what is left to conclude the

[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

[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=15830240#comment-15830240 ] Pramod Immaneni commented on APEXCORE-614: -- https://github.com/apache/apex-core/pull/394 >

[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] [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] [Commented] (APEXCORE-577) Visitor API for DAG

[ https://issues.apache.org/jira/browse/APEXCORE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892255#comment-15892255 ] Pramod Immaneni commented on APEXCORE-577: -- This lifecycle seems very localized and

[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=15892272#comment-15892272 ] Pramod Immaneni commented on APEXCORE-577: -- Also I suggest calling this something like

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

[ https://issues.apache.org/jira/browse/APEXCORE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892255#comment-15892255 ] Pramod Immaneni edited comment on APEXCORE-577 at 3/2/17 2:00 PM: -- This

[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:

[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:

[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:

[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] [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=15490615#comment-15490615 ] Pramod Immaneni commented on APEXCORE-532: -- Let me try a couple of things and get back to you

[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

[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

[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=15550141#comment-15550141 ] Pramod Immaneni commented on APEXCORE-548: -- I was thinking about that approach but where I saw

[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=15550065#comment-15550065 ] Pramod Immaneni commented on APEXCORE-548: -- Looks like getAppAlias looks at both properties and

[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=15550024#comment-15550024 ] Pramod Immaneni commented on APEXCORE-548: -- Wouldn't getDisplayName return the annotated name

[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=15514071#comment-15514071 ] Pramod Immaneni commented on APEXCORE-532: -- [~tushargosavi] checking why this is broken when it

[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,

[jira] [Commented] (APEXCORE-515) Refresh tokens failing in some scenarios with a login failure message

[ https://issues.apache.org/jira/browse/APEXCORE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433868#comment-15433868 ] Pramod Immaneni commented on APEXCORE-515: -- This is happening when the principal has a group

[jira] [Created] (APEXCORE-515) Refresh tokens failing in some scenarios with a login failure message

Pramod Immaneni created APEXCORE-515: Summary: Refresh tokens failing in some scenarios with a login failure message Key: APEXCORE-515 URL: https://issues.apache.org/jira/browse/APEXCORE-515

[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=15649116#comment-15649116 ] Pramod Immaneni commented on APEXCORE-570: -- Also will look at how disabling buffer spooling can

[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

[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] [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

[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=15583598#comment-15583598 ] Pramod Immaneni commented on APEXMALHAR-2263: - Why can't we have both the long and int

[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] [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

[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=15630269#comment-15630269 ] Pramod Immaneni commented on APEXCORE-570: -- For the inter-process case, if the downstream

[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:

[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=15628460#comment-15628460 ] Pramod Immaneni commented on APEXCORE-570: -- Here is an example on how to do this from within

[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

[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

[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

[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=15630806#comment-15630806 ] Pramod Immaneni commented on APEXCORE-570: -- [~davidyan] that would lead to deadlock because old

[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=15729596#comment-15729596 ] Pramod Immaneni commented on APEXCORE-577: -- Why specifically limit it to client side

[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=15729585#comment-15729585 ] Pramod Immaneni commented on APEXCORE-558: -- Red typically means something is wrong, wouldn't

[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] [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-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=15731038#comment-15731038 ] Pramod Immaneni commented on APEXCORE-587: -- Agree with both of you. But how about adding

[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=15823292#comment-15823292 ] Pramod Immaneni commented on APEXCORE-570: -- I will go into the topic specific comments first

[jira] [Resolved] (APEXCORE-649) Infrastructure for user define stram event listeners.

[ https://issues.apache.org/jira/browse/APEXCORE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-649. -- Resolution: Fixed Fix Version/s: 3.6.0 > Infrastructure for user define stram

[jira] [Updated] (APEXCORE-609) Support for back pressure in buffer server when spooling is disabled (out of memory issue)

[ https://issues.apache.org/jira/browse/APEXCORE-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-609: - Summary: Support for back pressure in buffer server when spooling is disabled (out of

[jira] [Created] (APEXCORE-671) DTConfiguration utility class ValueEntry access level was changed

Pramod Immaneni created APEXCORE-671: Summary: DTConfiguration utility class ValueEntry access level was changed Key: APEXCORE-671 URL: https://issues.apache.org/jira/browse/APEXCORE-671 Project:

[jira] [Assigned] (APEXCORE-671) DTConfiguration utility class ValueEntry access level was changed

[ https://issues.apache.org/jira/browse/APEXCORE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-671: Assignee: Pramod Immaneni > DTConfiguration utility class ValueEntry access

[jira] [Assigned] (APEXCORE-668) Remove CustomControlTuple type from Buffer Server

[ https://issues.apache.org/jira/browse/APEXCORE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-668: Assignee: Pramod Immaneni > Remove CustomControlTuple type from Buffer Server >

[jira] [Commented] (APEXCORE-673) Publish Javadoc for master branches on git push

[ https://issues.apache.org/jira/browse/APEXCORE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931020#comment-15931020 ] Pramod Immaneni commented on APEXCORE-673: -- Would this be to a public or some internal

[jira] [Created] (APEXMALHAR-2473) Support for global cache meta information in db CacheManager

Pramod Immaneni created APEXMALHAR-2473: --- Summary: Support for global cache meta information in db CacheManager Key: APEXMALHAR-2473 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2473

[jira] [Commented] (APEXMALHAR-2473) Support for global cache meta information in db CacheManager

[ https://issues.apache.org/jira/browse/APEXMALHAR-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954555#comment-15954555 ] Pramod Immaneni commented on APEXMALHAR-2473: - The CacheManager can allow the user to

[jira] [Created] (APEXMALHAR-2475) CacheStore needn't expire data if it read-only data

Pramod Immaneni created APEXMALHAR-2475: --- Summary: CacheStore needn't expire data if it read-only data Key: APEXMALHAR-2475 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2475 Project:

[jira] [Updated] (APEXMALHAR-2473) Support for global cache meta information in db CacheManager

[ https://issues.apache.org/jira/browse/APEXMALHAR-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXMALHAR-2473: Description: Currently db CacheManager has no knowledge of characteristics of

[jira] [Created] (APEXMALHAR-2474) FSLoader only returns value at the beginning

Pramod Immaneni created APEXMALHAR-2474: --- Summary: FSLoader only returns value at the beginning Key: APEXMALHAR-2474 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2474 Project: Apache

[jira] [Resolved] (APEXCORE-575) Improve application relaunch time.

[ https://issues.apache.org/jira/browse/APEXCORE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-575. -- Resolution: Fixed > Improve application relaunch time. >

[jira] [Created] (APEXCORE-699) Investigate versioning for plugins

Pramod Immaneni created APEXCORE-699: Summary: Investigate versioning for plugins Key: APEXCORE-699 URL: https://issues.apache.org/jira/browse/APEXCORE-699 Project: Apache Apex Core

[jira] [Assigned] (APEXCORE-699) Investigate versioning for plugins

[ https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-699: Assignee: Tushar Gosavi > Investigate versioning for plugins >

[jira] [Resolved] (APEXCORE-690) Embedded app launcher does not apply HEARTBEAT_MONITORING setting

[ https://issues.apache.org/jira/browse/APEXCORE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-690. -- Resolution: Fixed > Embedded app launcher does not apply HEARTBEAT_MONITORING setting

[jira] [Updated] (APEXCORE-575) Improve application relaunch time.

[ https://issues.apache.org/jira/browse/APEXCORE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-575: - Fix Version/s: 3.6.0 > Improve application relaunch time. >

[jira] [Closed] (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 closed APEXCORE-460. > Token refresh mechanism not considering keytab specified in command line >

[jira] [Updated] (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 updated APEXCORE-460: - Fix Version/s: 3.5.0 > Token refresh mechanism not considering keytab specified in

[jira] [Updated] (APEXCORE-246) Add capability in the engine to let the operator know about the next checkpoint window

[ https://issues.apache.org/jira/browse/APEXCORE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-246: - Fix Version/s: 3.4.0 > Add capability in the engine to let the operator know about the

[jira] [Closed] (APEXCORE-246) Add capability in the engine to let the operator know about the next checkpoint window

[ https://issues.apache.org/jira/browse/APEXCORE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni closed APEXCORE-246. > Add capability in the engine to let the operator know about the next > checkpoint window >

[jira] [Closed] (APEXCORE-360) Add capability in the engine to let the operator know about the next checkpoint window

[ https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni closed APEXCORE-360. > Add capability in the engine to let the operator know about the next > checkpoint window >

[jira] [Reopened] (APEXCORE-360) Add capability in the engine to let the operator know about the next checkpoint window

[ https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reopened APEXCORE-360: -- > Add capability in the engine to let the operator know about the next > checkpoint

[jira] [Updated] (APEXCORE-360) Add capability in the engine to let the operator know about the next checkpoint window

[ https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-360: - Fix Version/s: (was: 3.5.0) 3.4.0 > Add capability in the engine

[jira] [Resolved] (APEXCORE-360) Add capability in the engine to let the operator know about the next checkpoint window

[ https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-360. -- Resolution: Fixed > Add capability in the engine to let the operator know about the

[jira] [Closed] (APEXCORE-360) Add capability in the engine to let the operator know about the next checkpoint window

[ https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni closed APEXCORE-360. > Add capability in the engine to let the operator know about the next > checkpoint window >

[jira] [Updated] (APEXCORE-360) Add capability in the engine to let the operator know about the next checkpoint window

[ https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-360: - Fix Version/s: 3.5.0 > Add capability in the engine to let the operator know about the

[jira] [Resolved] (APEXCORE-686) AppPackage fails when .apa contains zero length stored entry

[ https://issues.apache.org/jira/browse/APEXCORE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-686. -- Resolution: Fixed > AppPackage fails when .apa contains zero length stored entry >

[jira] [Created] (APEXCORE-706) Drop blocks that have already been read so that the list size does not keep growing

Pramod Immaneni created APEXCORE-706: Summary: Drop blocks that have already been read so that the list size does not keep growing Key: APEXCORE-706 URL: https://issues.apache.org/jira/browse/APEXCORE-706

[jira] [Created] (APEXCORE-707) Allow configurability on a per-stream basis using an attribute

Pramod Immaneni created APEXCORE-707: Summary: Allow configurability on a per-stream basis using an attribute Key: APEXCORE-707 URL: https://issues.apache.org/jira/browse/APEXCORE-707 Project:

[jira] [Assigned] (APEXCORE-707) Allow configurability on a per-stream basis using an attribute

[ https://issues.apache.org/jira/browse/APEXCORE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-707: Assignee: Pramod Immaneni > Allow configurability on a per-stream basis using an

[jira] [Assigned] (APEXCORE-706) Drop blocks that have already been read so that the list size does not keep growing

[ https://issues.apache.org/jira/browse/APEXCORE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-706: Assignee: Pramod Immaneni > Drop blocks that have already been read so that the

[jira] [Created] (APEXCORE-708) Allow number of blocks when bp kicks in to be specified

Pramod Immaneni created APEXCORE-708: Summary: Allow number of blocks when bp kicks in to be specified Key: APEXCORE-708 URL: https://issues.apache.org/jira/browse/APEXCORE-708 Project: Apache

[jira] [Commented] (APEXCORE-699) Investigate versioning for plugins

[ https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972063#comment-15972063 ] Pramod Immaneni commented on APEXCORE-699: -- Thanks for checking this. What if the version that

[jira] [Updated] (APEXCORE-700) Make the plugin registration interface uniform

[ https://issues.apache.org/jira/browse/APEXCORE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-700: - Fix Version/s: 3.6.0 > Make the plugin registration interface uniform >

[jira] [Created] (APEXCORE-710) Plugin manager does not report exceptions from plugins

Pramod Immaneni created APEXCORE-710: Summary: Plugin manager does not report exceptions from plugins Key: APEXCORE-710 URL: https://issues.apache.org/jira/browse/APEXCORE-710 Project: Apache Apex

[jira] [Updated] (APEXCORE-699) Investigate versioning for plugins

[ https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-699: - Fix Version/s: 3.6.0 > Investigate versioning for plugins >

[jira] [Assigned] (APEXCORE-664) Large number of operator requests can overflow client buffers

[ https://issues.apache.org/jira/browse/APEXCORE-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-664: Assignee: Munagala V. Ramanath > Large number of operator requests can overflow

  1   2   3   >