[jira] [Closed] (APEXCORE-453) Intermittent failure of DelayOperatorTest.testFibonacci test case

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-453.
---
Resolution: Fixed

> Intermittent failure of DelayOperatorTest.testFibonacci test case
> -
>
> Key: APEXCORE-453
> URL: https://issues.apache.org/jira/browse/APEXCORE-453
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Sandeep Deshmukh
>Assignee: David Yan
>Priority: Minor
> Fix For: 3.3.1, 3.5.0
>
>
> The test case DelayOperatorTest.testFibonacci fails intermittently. I compile 
> and ran test cases 5 times and the test case failed couple of times.
> Hint: Observed this when the machine was loaded.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXCORE-677) Avoid starting StramLocalCluster in StreamingContainerManagerTest.testAppDataSources

[Vlad Rozov (JIRA)]

Vlad Rozov created APEXCORE-677:
---

 Summary: Avoid starting StramLocalCluster in 
StreamingContainerManagerTest.testAppDataSources
 Key: APEXCORE-677
 URL: https://issues.apache.org/jira/browse/APEXCORE-677
 Project: Apache Apex Core
  Issue Type: Improvement
Reporter: Vlad Rozov
Assignee: Vlad Rozov
Priority: Trivial


testAppDataSources does not wait for the StramLocalCluster to be initialized, 
so it does not need to start it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-697) Use MiniYARNCluster for unit tests

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-697.
---
Resolution: Invalid

The JIRA is way too abstract. If there is a concrete unit test that should use 
MiniYarnCluster or MiniDFSCluster please file JIRA for that unit test.

> Use MiniYARNCluster for unit tests
> --
>
> Key: APEXCORE-697
> URL: https://issues.apache.org/jira/browse/APEXCORE-697
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Sandesh
>
> MiniYARNCluster & MiniDFSCluster can be used in unit tests.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXCORE-698) Extend checkstyle rules to handle few additional code style issues

[Vlad Rozov (JIRA)]

Vlad Rozov created APEXCORE-698:
---

 Summary: Extend checkstyle rules to handle few additional code 
style issues
 Key: APEXCORE-698
 URL: https://issues.apache.org/jira/browse/APEXCORE-698
 Project: Apache Apex Core
  Issue Type: Task
Reporter: Vlad Rozov
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-695) Remove unnecessary interface modifiers

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-695.
-
   Resolution: Done
Fix Version/s: 3.6.0

> Remove unnecessary interface modifiers
> --
>
> Key: APEXCORE-695
> URL: https://issues.apache.org/jira/browse/APEXCORE-695
> Project: Apache Apex Core
>  Issue Type: Task
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Minor
> Fix For: 3.6.0
>
>
> public modifier is redundant in interfaces



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950217#comment-15950217
 ] 

Vlad Rozov commented on APEXCORE-686:
-

The solution is to use ZipArchiveInputStream instead of JarInputStream that 
allows to support such files.

> AppPackage fails when .apa contains zero length stored entry
> 
>
> Key: APEXCORE-686
> URL: https://issues.apache.org/jira/browse/APEXCORE-686
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
> Fix For: 3.6.0
>
>
> JarInputStream/ZipInputStream does not support valid formats of .jar/.zip file
> {noformat}
> java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
>   at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:309)
>   at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:121)
>   at java.util.jar.JarInputStream.(JarInputStream.java:83)
>   at java.util.jar.JarInputStream.(JarInputStream.java:62)
>   at com.datatorrent.stram.client.AppPackage.(AppPackage.java:215)
>   at com.datatorrent.stram.client.AppPackage.(AppPackage.java:196)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXMALHAR-2284) POJOInnerJoinOperatorTest fails in Travis CI

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXMALHAR-2284:
---
Priority: Minor  (was: Blocker)

> POJOInnerJoinOperatorTest fails in Travis CI
> 
>
> Key: APEXMALHAR-2284
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2284
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Thomas Weise
>Assignee: Chaitanya
>Priority: Minor
>
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/166322754/log.txt
> {code}
> Failed tests: 
>   POJOInnerJoinOperatorTest.testEmitMultipleTuplesFromStream2:337 Number of 
> tuple emitted  expected:<2> but was:<4>
>   POJOInnerJoinOperatorTest.testInnerJoinOperator:184 Number of tuple emitted 
>  expected:<1> but was:<2>
>   POJOInnerJoinOperatorTest.testMultipleValues:236 Number of tuple emitted  
> expected:<2> but was:<3>
>   POJOInnerJoinOperatorTest.testUpdateStream1Values:292 Number of tuple 
> emitted  expected:<1> but was:<2>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXMALHAR-2284) POJOInnerJoinOperatorTest fails in Travis CI

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952246#comment-15952246
 ] 

Vlad Rozov commented on APEXMALHAR-2284:


Lowered priority from blocker. If this is an operator problem, please file new 
JIRA with proper title, description, and priority. In case it is the specific 
test issue, the test can be disabled till it is fixed.

> POJOInnerJoinOperatorTest fails in Travis CI
> 
>
> Key: APEXMALHAR-2284
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2284
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Thomas Weise
>Assignee: Chaitanya
>Priority: Minor
>
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/166322754/log.txt
> {code}
> Failed tests: 
>   POJOInnerJoinOperatorTest.testEmitMultipleTuplesFromStream2:337 Number of 
> tuple emitted  expected:<2> but was:<4>
>   POJOInnerJoinOperatorTest.testInnerJoinOperator:184 Number of tuple emitted 
>  expected:<1> but was:<2>
>   POJOInnerJoinOperatorTest.testMultipleValues:236 Number of tuple emitted  
> expected:<2> but was:<3>
>   POJOInnerJoinOperatorTest.testUpdateStream1Values:292 Number of tuple 
> emitted  expected:<1> but was:<2>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-656) Upgrade org.apache.httpcomponents.httpclient

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-656:

Description: Upgrade org.apache.httpcomponents.httpclient dependency to the 
latest 4.3.x version. Please see 
[https://dist.apache.org/repos/dist/release/httpcomponents/httpclient/RELEASE_NOTES-4.3.x.txt.]

> Upgrade org.apache.httpcomponents.httpclient
> 
>
> Key: APEXCORE-656
> URL: https://issues.apache.org/jira/browse/APEXCORE-656
> Project: Apache Apex Core
>  Issue Type: Dependency upgrade
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Trivial
> Fix For: 3.6.0
>
>
> Upgrade org.apache.httpcomponents.httpclient dependency to the latest 4.3.x 
> version. Please see 
> [https://dist.apache.org/repos/dist/release/httpcomponents/httpclient/RELEASE_NOTES-4.3.x.txt.]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-656) Upgrade org.apache.httpcomponents.httpclient

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-656:

Description: Upgrade org.apache.httpcomponents.httpclient dependency to the 
latest 4.3.x version. Please see 
[https://dist.apache.org/repos/dist/release/httpcomponents/httpclient/RELEASE_NOTES-4.3.x.txt].
  (was: Upgrade org.apache.httpcomponents.httpclient dependency to the latest 
4.3.x version. Please see 
[https://dist.apache.org/repos/dist/release/httpcomponents/httpclient/RELEASE_NOTES-4.3.x.txt.])

> Upgrade org.apache.httpcomponents.httpclient
> 
>
> Key: APEXCORE-656
> URL: https://issues.apache.org/jira/browse/APEXCORE-656
> Project: Apache Apex Core
>  Issue Type: Dependency upgrade
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Trivial
> Fix For: 3.6.0
>
>
> Upgrade org.apache.httpcomponents.httpclient dependency to the latest 4.3.x 
> version. Please see 
> [https://dist.apache.org/repos/dist/release/httpcomponents/httpclient/RELEASE_NOTES-4.3.x.txt].



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXMALHAR-2469) Upgrade org.apache.httpcomponents.httpclient

[Vlad Rozov (JIRA)]

Vlad Rozov created APEXMALHAR-2469:
--

 Summary: Upgrade org.apache.httpcomponents.httpclient
 Key: APEXMALHAR-2469
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2469
 Project: Apache Apex Malhar
  Issue Type: Dependency upgrade
Reporter: Vlad Rozov
Assignee: Vlad Rozov
Priority: Trivial


Upgrade org.apache.httpcomponents.httpclient optional dependency to the latest 
4.3.x version. Please see 
[https://dist.apache.org/repos/dist/release/httpcomponents/httpclient/RELEASE_NOTES-4.3.x.txt].



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-660) Documentation for Control tuple support changes

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-660:

Fix Version/s: (was: 3.6.0)

> Documentation for Control tuple support changes
> ---
>
> Key: APEXCORE-660
> URL: https://issues.apache.org/jira/browse/APEXCORE-660
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Bhupesh Chawda
>Assignee: Bhupesh Chawda
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-456) Explicitly limit Server.Subscriber to one way communication

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-456.
-
   Resolution: Fixed
Fix Version/s: 3.6.0

> Explicitly limit Server.Subscriber to one way communication
> ---
>
> Key: APEXCORE-456
> URL: https://issues.apache.org/jira/browse/APEXCORE-456
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
> Fix For: 3.6.0
>
>
> In the DAG data always flows from upstream to downstream operators and buffer 
> server Server.Subscriber class may explicitly shutdown input stream, does not 
> need to allocate read buffer and listen to OP_READ events. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-658) Replace dt. prefix with apex. for configuration keys

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-658.
-
   Resolution: Fixed
Fix Version/s: 3.6.0

> Replace dt. prefix with apex. for configuration keys  
> --
>
> Key: APEXCORE-658
> URL: https://issues.apache.org/jira/browse/APEXCORE-658
> Project: Apache Apex Core
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Thomas Weise
> Fix For: 3.6.0
>
>
> Users should be able to configure their applications with keys that use apex. 
> as prefix and this is how it should be shown in examples also. It should be  
> possible to make this change w/o breaking backward compatibility.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXCORE-695) Remove unnecessary interface modifiers

[Vlad Rozov (JIRA)]

Vlad Rozov created APEXCORE-695:
---

 Summary: Remove unnecessary interface modifiers
 Key: APEXCORE-695
 URL: https://issues.apache.org/jira/browse/APEXCORE-695
 Project: Apache Apex Core
  Issue Type: Task
Reporter: Vlad Rozov
Assignee: Vlad Rozov
Priority: Minor


public modifier is redundant in interfaces



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-691) Use type inference for generic instance creation

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-691.
-
Resolution: Done

> Use type inference for generic instance creation
> 
>
> Key: APEXCORE-691
> URL: https://issues.apache.org/jira/browse/APEXCORE-691
> Project: Apache Apex Core
>  Issue Type: Task
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Minor
> Fix For: 3.6.0
>
>
> The current Java language level allows using type inference for generic 
> instance creation making constructs like
> {noformat}
> Map  map = new HashMap();
> {noformat}
> unnecessary.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXCORE-696) Provide an ability to open and close output ports

[Vlad Rozov (JIRA)]

Vlad Rozov created APEXCORE-696:
---

 Summary: Provide an ability to open and close output ports
 Key: APEXCORE-696
 URL: https://issues.apache.org/jira/browse/APEXCORE-696
 Project: Apache Apex Core
  Issue Type: New Feature
Reporter: Vlad Rozov


https://lists.apache.org/thread.html/a2f4bb88ccbb38b3bc9f371a51139609e9a2e6c96e541012b836b6ca@%3Cdev.apex.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXCORE-694) Use correct annotation for nullable and not nullable arguments

[Vlad Rozov (JIRA)]

Vlad Rozov created APEXCORE-694:
---

 Summary: Use correct annotation for nullable and not nullable 
arguments
 Key: APEXCORE-694
 URL: https://issues.apache.org/jira/browse/APEXCORE-694
 Project: Apache Apex Core
  Issue Type: Improvement
Reporter: Vlad Rozov
Priority: Minor


jsr305 suggests usage of javax.annotation.Nonnull. Usage of 
javax.validation.constraints.NotNull should be avoided.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-683) Apex client should support application packages on HDFS

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-683.
-
   Resolution: Implemented
Fix Version/s: 3.6.0

> Apex client should support application packages on HDFS
> ---
>
> Key: APEXCORE-683
> URL: https://issues.apache.org/jira/browse/APEXCORE-683
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
> Fix For: 3.6.0
>
>
> apex client supports only local file system, it is natural for native yarn 
> application to support hdfs and other dfs file systems:
> {noformat}
> hdfs dfs -ls hdfs:///user/vrozov
> Found 4 items
> drwx--   - vrozov supergroup  0 2016-12-24 16:00 
> hdfs:///user/vrozov/.Trash
> drwxrwxrwx   - vrozov supergroup  0 2017-02-28 19:20 
> hdfs:///user/vrozov/.flink
> -rw-r--r--   3 vrozov supergroup   18862977 2017-03-25 09:20 
> hdfs:///user/vrozov/appPackage.apa
> drwxrwxrwx   - vrozov supergroup  0 2016-10-25 21:49 
> hdfs:///user/vrozov/datatorrent
> [vrozov@node0 apex]$ apex
> Apex CLI 3.6.0-SNAPSHOT 25.03.2017 @ 09:17:45 PDT rev: b4a4e05 branch: master
> apex> get-app-package-info  hdfs:///user/vrozov/appPackage.apa
> java.io.FileNotFoundException: hdfs:/user/vrozov/appPackage.apa (No such file 
> or directory)
>   at java.util.zip.ZipFile.open(Native Method)
>   at java.util.zip.ZipFile.(ZipFile.java:215)
>   at java.util.zip.ZipFile.(ZipFile.java:145)
>   at java.util.jar.JarFile.(JarFile.java:154)
>   at java.util.jar.JarFile.(JarFile.java:118)
>   at com.datatorrent.stram.client.AppPackage.(AppPackage.java:185)
>   at com.datatorrent.stram.client.AppPackage.(AppPackage.java:258)
>   at 
> com.datatorrent.stram.cli.ApexCli.newAppPackageInstance(ApexCli.java:467)
>   at 
> com.datatorrent.stram.cli.ApexCli$GetAppPackageInfoCommand.execute(ApexCli.java:3502)
>   at com.datatorrent.stram.cli.ApexCli$3.run(ApexCli.java:1520)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-493) Purge the checkpoints from the containers

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-493.
-
Resolution: Won't Do

> Purge the checkpoints from the containers
> -
>
> Key: APEXCORE-493
> URL: https://issues.apache.org/jira/browse/APEXCORE-493
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Sandesh
>Assignee: Sandesh
>
> Currently, purging of the checkpoints happens from the Stram, but it could be 
> done in StreamingContainers.
> Idea is to reduce the responsibilities of the Stram and to distribute the 
> work across the containers.
> Purging during Dynamic partitions can still be done in Stram.
> Inspiration -
> https://issues.apache.org/jira/browse/APEXCORE-222



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-371) Update ASF and incubator logos on apex web site

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-371:

Component/s: Website

> Update ASF and incubator logos on apex web site
> ---
>
> Key: APEXCORE-371
> URL: https://issues.apache.org/jira/browse/APEXCORE-371
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Vlad Rozov
>Assignee: Sasha Parfenov
>Priority: Minor
>
> Please see http://apache.org/foundation/press/kit/
> For incubator logo, we may point to
> http://incubator.apache.org/images/egg-logo2.png



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-371) Update ASF and incubator logos on apex web site

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-371.
---
Resolution: Done

> Update ASF and incubator logos on apex web site
> ---
>
> Key: APEXCORE-371
> URL: https://issues.apache.org/jira/browse/APEXCORE-371
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Vlad Rozov
>Assignee: Sasha Parfenov
>Priority: Minor
>
> Please see http://apache.org/foundation/press/kit/
> For incubator logo, we may point to
> http://incubator.apache.org/images/egg-logo2.png



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-371) Update ASF and incubator logos on apex web site

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-371:
-

> Update ASF and incubator logos on apex web site
> ---
>
> Key: APEXCORE-371
> URL: https://issues.apache.org/jira/browse/APEXCORE-371
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Vlad Rozov
>Assignee: Sasha Parfenov
>Priority: Minor
>
> Please see http://apache.org/foundation/press/kit/
> For incubator logo, we may point to
> http://incubator.apache.org/images/egg-logo2.png



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-215) Release vote build/test/verification instructions

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-215:
-

> Release vote build/test/verification instructions
> -
>
> Key: APEXCORE-215
> URL: https://issues.apache.org/jira/browse/APEXCORE-215
> Project: Apache Apex Core
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Sandeep Deshmukh
>
> Add a page to the web site that explains contributors how to test a release 
> candidate.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-455) Create documentation for delegation token refresh for applications in secure mode

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-455:

Issue Type: Task  (was: Improvement)

> Create documentation for delegation token refresh for applications in secure 
> mode
> -
>
> Key: APEXCORE-455
> URL: https://issues.apache.org/jira/browse/APEXCORE-455
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Reporter: Pramod Immaneni
>Assignee: Pramod Immaneni
>
> In secure mode applications can refresh their delegation tokens. This is not 
> documented and so are the associated settings. Add this documentation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-455) Create documentation for delegation token refresh for applications in secure mode

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-455.
---

> Create documentation for delegation token refresh for applications in secure 
> mode
> -
>
> Key: APEXCORE-455
> URL: https://issues.apache.org/jira/browse/APEXCORE-455
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Reporter: Pramod Immaneni
>Assignee: Pramod Immaneni
>
> In secure mode applications can refresh their delegation tokens. This is not 
> documented and so are the associated settings. Add this documentation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-457) Add documentation for security options for STRAM web services

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-457.
---

> Add documentation for security options for STRAM web services
> -
>
> Key: APEXCORE-457
> URL: https://issues.apache.org/jira/browse/APEXCORE-457
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 3.4.0
>Reporter: Pramod Immaneni
>Assignee: Pramod Immaneni
>
> Security can be enabled for STRAM web services. Add documentation for the 
> available options and how security works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-457) Add documentation for security options for STRAM web services

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-457:

Issue Type: Task  (was: Bug)

> Add documentation for security options for STRAM web services
> -
>
> Key: APEXCORE-457
> URL: https://issues.apache.org/jira/browse/APEXCORE-457
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 3.4.0
>Reporter: Pramod Immaneni
>Assignee: Pramod Immaneni
>
> Security can be enabled for STRAM web services. Add documentation for the 
> available options and how security works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-455) Create documentation for delegation token refresh for applications in secure mode

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-455:

Component/s: Documentation

> Create documentation for delegation token refresh for applications in secure 
> mode
> -
>
> Key: APEXCORE-455
> URL: https://issues.apache.org/jira/browse/APEXCORE-455
> Project: Apache Apex Core
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Pramod Immaneni
>Assignee: Pramod Immaneni
>
> In secure mode applications can refresh their delegation tokens. This is not 
> documented and so are the associated settings. Add this documentation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-215) Release vote build/test/verification instructions

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-215.
---
Resolution: Done

> Release vote build/test/verification instructions
> -
>
> Key: APEXCORE-215
> URL: https://issues.apache.org/jira/browse/APEXCORE-215
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Thomas Weise
>Assignee: Sandeep Deshmukh
>
> Add a page to the web site that explains contributors how to test a release 
> candidate.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-215) Release vote build/test/verification instructions

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-215:

Component/s: Website

> Release vote build/test/verification instructions
> -
>
> Key: APEXCORE-215
> URL: https://issues.apache.org/jira/browse/APEXCORE-215
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Thomas Weise
>Assignee: Sandeep Deshmukh
>
> Add a page to the web site that explains contributors how to test a release 
> candidate.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-320) Create "Who We Are" page

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-320:

Component/s: Website

> Create "Who We Are" page
> 
>
> Key: APEXCORE-320
> URL: https://issues.apache.org/jira/browse/APEXCORE-320
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chris Nauroth
>Assignee: Thomas Weise
>  Labels: tlp
>
> CS10
> The project maintains a public list of its contributors who have decision
> power -- the project's PMC (Project Management Committee) consists of
> those contributors.
> I couldn't find a "Who We Are" page at apex.incubator.apache.org.  I think
> the information is accurate in the incubation status page though.
> Example: https://hadoop.apache.org/who.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-320) Create "Who We Are" page

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-320:
-

> Create "Who We Are" page
> 
>
> Key: APEXCORE-320
> URL: https://issues.apache.org/jira/browse/APEXCORE-320
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chris Nauroth
>Assignee: Thomas Weise
>  Labels: tlp
>
> CS10
> The project maintains a public list of its contributors who have decision
> power -- the project's PMC (Project Management Committee) consists of
> those contributors.
> I couldn't find a "Who We Are" page at apex.incubator.apache.org.  I think
> the information is accurate in the incubation status page though.
> Example: https://hadoop.apache.org/who.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-424) Please delete old releases from mirroring system

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-424.
---

> Please delete old releases from mirroring system
> 
>
> Key: APEXCORE-424
> URL: https://issues.apache.org/jira/browse/APEXCORE-424
> Project: Apache Apex Core
>  Issue Type: Task
> Environment: 
> https://dist.apache.org/repos/dist/release/incubator/apex/
> https://dist.apache.org/repos/dist/release/incubator/apex/malhar/
>Reporter: Sebb
>Assignee: Thomas Weise
>Priority: Minor
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases?
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-387) Add ponymail forum link to apex website

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-387:

Priority: Minor  (was: Major)

> Add ponymail forum link to apex website
> ---
>
> Key: APEXCORE-387
> URL: https://issues.apache.org/jira/browse/APEXCORE-387
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>Priority: Minor
>
> Add ponymail forum link to apex website



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-387) Add ponymail forum link to apex website

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-387:

Component/s: Website

> Add ponymail forum link to apex website
> ---
>
> Key: APEXCORE-387
> URL: https://issues.apache.org/jira/browse/APEXCORE-387
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>
> Add ponymail forum link to apex website



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-424) Please delete old releases from mirroring system

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-424.
-
Resolution: Done

> Please delete old releases from mirroring system
> 
>
> Key: APEXCORE-424
> URL: https://issues.apache.org/jira/browse/APEXCORE-424
> Project: Apache Apex Core
>  Issue Type: Task
> Environment: 
> https://dist.apache.org/repos/dist/release/incubator/apex/
> https://dist.apache.org/repos/dist/release/incubator/apex/malhar/
>Reporter: Sebb
>Assignee: Thomas Weise
>Priority: Minor
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases?
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-387) Add ponymail forum link to apex website

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-387:
-

> Add ponymail forum link to apex website
> ---
>
> Key: APEXCORE-387
> URL: https://issues.apache.org/jira/browse/APEXCORE-387
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>
> Add ponymail forum link to apex website



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-424) Please delete old releases from mirroring system

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-424:

Issue Type: Task  (was: Bug)

> Please delete old releases from mirroring system
> 
>
> Key: APEXCORE-424
> URL: https://issues.apache.org/jira/browse/APEXCORE-424
> Project: Apache Apex Core
>  Issue Type: Task
> Environment: 
> https://dist.apache.org/repos/dist/release/incubator/apex/
> https://dist.apache.org/repos/dist/release/incubator/apex/malhar/
>Reporter: Sebb
>Assignee: Thomas Weise
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases?
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-424) Please delete old releases from mirroring system

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-424:
-

> Please delete old releases from mirroring system
> 
>
> Key: APEXCORE-424
> URL: https://issues.apache.org/jira/browse/APEXCORE-424
> Project: Apache Apex Core
>  Issue Type: Bug
> Environment: 
> https://dist.apache.org/repos/dist/release/incubator/apex/
> https://dist.apache.org/repos/dist/release/incubator/apex/malhar/
>Reporter: Sebb
>Assignee: Thomas Weise
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases?
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-424) Please delete old releases from mirroring system

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-424:

Priority: Minor  (was: Major)

> Please delete old releases from mirroring system
> 
>
> Key: APEXCORE-424
> URL: https://issues.apache.org/jira/browse/APEXCORE-424
> Project: Apache Apex Core
>  Issue Type: Task
> Environment: 
> https://dist.apache.org/repos/dist/release/incubator/apex/
> https://dist.apache.org/repos/dist/release/incubator/apex/malhar/
>Reporter: Sebb
>Assignee: Thomas Weise
>Priority: Minor
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases?
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-514) Apache Apex website update

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-514.
---

> Apache Apex website update
> --
>
> Key: APEXCORE-514
> URL: https://issues.apache.org/jira/browse/APEXCORE-514
> Project: Apache Apex Core
>  Issue Type: Improvement
>  Components: Website
>Reporter: Michelle Xiao
>Assignee: Michelle Xiao
>Priority: Minor
>  Labels: features
>
> Update Apache Apex website:
> 1. Nav bar: add "Powered By Apex" and "Roadmap"; add an anchor Contributing 
> and a  link to Newest Apex Questions on Stack Overflow under Community;
> 2. Home page: add another "Download" after Github under Apache Apex section;
> 3. Docs page: add top navigation tabs linking to each section in this page, 
> navigation tab includes all section titles in this page



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-534) Improve setup instructions in contributor guidelines

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-534:
-

> Improve setup instructions in contributor guidelines
> 
>
> Key: APEXCORE-534
> URL: https://issues.apache.org/jira/browse/APEXCORE-534
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Reporter: Thomas Weise
>Assignee: Thomas Weise
>
> Improve instructions for newcomers to get started contributing. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-534) Improve setup instructions in contributor guidelines

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-534.
---
Resolution: Fixed

> Improve setup instructions in contributor guidelines
> 
>
> Key: APEXCORE-534
> URL: https://issues.apache.org/jira/browse/APEXCORE-534
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Reporter: Thomas Weise
>Assignee: Thomas Weise
>
> Improve instructions for newcomers to get started contributing. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-514) Apache Apex website update

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-514:

Component/s: Website

> Apache Apex website update
> --
>
> Key: APEXCORE-514
> URL: https://issues.apache.org/jira/browse/APEXCORE-514
> Project: Apache Apex Core
>  Issue Type: Improvement
>  Components: Website
>Reporter: Michelle Xiao
>Assignee: Michelle Xiao
>  Labels: features
>
> Update Apache Apex website:
> 1. Nav bar: add "Powered By Apex" and "Roadmap"; add an anchor Contributing 
> and a  link to Newest Apex Questions on Stack Overflow under Community;
> 2. Home page: add another "Download" after Github under Apache Apex section;
> 3. Docs page: add top navigation tabs linking to each section in this page, 
> navigation tab includes all section titles in this page



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-534) Improve setup instructions in contributor guidelines

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-534:

Component/s: Documentation

> Improve setup instructions in contributor guidelines
> 
>
> Key: APEXCORE-534
> URL: https://issues.apache.org/jira/browse/APEXCORE-534
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Reporter: Thomas Weise
>Assignee: Thomas Weise
>
> Improve instructions for newcomers to get started contributing. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-526:

Component/s: Documentation

> Publish javadoc for releases on ASF infrastructure 
> ---
>
> Key: APEXCORE-526
> URL: https://issues.apache.org/jira/browse/APEXCORE-526
> Project: Apache Apex Core
>  Issue Type: Documentation
>  Components: Documentation
>Reporter: Thomas Weise
>Assignee: Munagala V. Ramanath
>
> Every release should have the javadocs published and we should have it linked 
> from the download page, as is the case with user docs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-526:
-

> Publish javadoc for releases on ASF infrastructure 
> ---
>
> Key: APEXCORE-526
> URL: https://issues.apache.org/jira/browse/APEXCORE-526
> Project: Apache Apex Core
>  Issue Type: Documentation
>  Components: Documentation
>Reporter: Thomas Weise
>Assignee: Munagala V. Ramanath
>
> Every release should have the javadocs published and we should have it linked 
> from the download page, as is the case with user docs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-370) Add self-assessment project maturity model to website

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-370:
-

> Add self-assessment project maturity model to website
> -
>
> Key: APEXCORE-370
> URL: https://issues.apache.org/jira/browse/APEXCORE-370
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>  Labels: tlp
>
> Add self-assessment project maturity model to apex website
> This should be used on: 
> https://community.apache.org/apache-way/apache-project-maturity-model.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-354) Add forum link for mailing lists

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-354:

Priority: Minor  (was: Major)

> Add forum link for mailing lists  
> --
>
> Key: APEXCORE-354
> URL: https://issues.apache.org/jira/browse/APEXCORE-354
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>Priority: Minor
>
> Add nabble forum links to maling list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-354) Add forum link for mailing lists

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-354:

Component/s: Website

> Add forum link for mailing lists  
> --
>
> Key: APEXCORE-354
> URL: https://issues.apache.org/jira/browse/APEXCORE-354
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>Priority: Minor
>
> Add nabble forum links to maling list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-354) Add forum link for mailing lists

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-354.
---
Resolution: Done

> Add forum link for mailing lists  
> --
>
> Key: APEXCORE-354
> URL: https://issues.apache.org/jira/browse/APEXCORE-354
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>Priority: Minor
>
> Add nabble forum links to maling list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (APEXCORE-180) Create a style guide for APEX

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reassigned APEXCORE-180:
---

   Assignee: Chandni Singh
Component/s: Website
 Issue Type: Task  (was: Sub-task)

> Create a style guide for APEX
> -
>
> Key: APEXCORE-180
> URL: https://issues.apache.org/jira/browse/APEXCORE-180
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chandni Singh
>Assignee: Chandni Singh
>  Labels: newbie
>
> Need a style guide for APEX



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-180) Create a style guide for APEX

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-180.
---
Resolution: Done

> Create a style guide for APEX
> -
>
> Key: APEXCORE-180
> URL: https://issues.apache.org/jira/browse/APEXCORE-180
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chandni Singh
>Assignee: Chandni Singh
>  Labels: newbie
>
> Need a style guide for APEX



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-427) Unit test testAppDataPush fails on Travis

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-427:

 Priority: Minor  (was: Major)
Fix Version/s: 3.4.0

> Unit test testAppDataPush fails on Travis
> -
>
> Key: APEXCORE-427
> URL: https://issues.apache.org/jira/browse/APEXCORE-427
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: David Yan
>Assignee: David Yan
>Priority: Minor
> Fix For: 3.4.0
>
>
> The unit test fails with this exception:
> {code}
> 2016-04-11 21:16:58,679 [main] WARN  stram.StreamingContainerManager 
> setupWsClient - Cannot establish websocket connection to localhost:51513
> java.util.concurrent.ExecutionException: 
> java.util.concurrent.TimeoutException: No response received after 500
>   at 
> com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:252)
>   at 
> com.datatorrent.common.util.PubSubWebSocketClient.openConnection(PubSubWebSocketClient.java:194)
>   at 
> com.datatorrent.stram.util.SharedPubSubWebSocketClient.setup(SharedPubSubWebSocketClient.java:75)
>   at 
> com.datatorrent.stram.StreamingContainerManager.setupWsClient(StreamingContainerManager.java:559)
>   at 
> com.datatorrent.stram.StreamingContainerManager.init(StreamingContainerManager.java:436)
>   at 
> com.datatorrent.stram.StreamingContainerManager.(StreamingContainerManager.java:420)
>   at 
> com.datatorrent.stram.StreamingContainerManager.(StreamingContainerManager.java:406)
>   at 
> com.datatorrent.stram.StramLocalCluster.(StramLocalCluster.java:299)
>   at 
> com.datatorrent.stram.StreamingContainerManagerTest.testAppDataPush(StreamingContainerManagerTest.java:955)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createReqestAndRun(JUnitCoreWrapper.java:139)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:111)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:84)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:138)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
> 

[jira] [Closed] (APEXCORE-427) Unit test testAppDataPush fails on Travis

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-427.
---

> Unit test testAppDataPush fails on Travis
> -
>
> Key: APEXCORE-427
> URL: https://issues.apache.org/jira/browse/APEXCORE-427
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: David Yan
>Assignee: David Yan
>Priority: Minor
> Fix For: 3.4.0
>
>
> The unit test fails with this exception:
> {code}
> 2016-04-11 21:16:58,679 [main] WARN  stram.StreamingContainerManager 
> setupWsClient - Cannot establish websocket connection to localhost:51513
> java.util.concurrent.ExecutionException: 
> java.util.concurrent.TimeoutException: No response received after 500
>   at 
> com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:252)
>   at 
> com.datatorrent.common.util.PubSubWebSocketClient.openConnection(PubSubWebSocketClient.java:194)
>   at 
> com.datatorrent.stram.util.SharedPubSubWebSocketClient.setup(SharedPubSubWebSocketClient.java:75)
>   at 
> com.datatorrent.stram.StreamingContainerManager.setupWsClient(StreamingContainerManager.java:559)
>   at 
> com.datatorrent.stram.StreamingContainerManager.init(StreamingContainerManager.java:436)
>   at 
> com.datatorrent.stram.StreamingContainerManager.(StreamingContainerManager.java:420)
>   at 
> com.datatorrent.stram.StreamingContainerManager.(StreamingContainerManager.java:406)
>   at 
> com.datatorrent.stram.StramLocalCluster.(StramLocalCluster.java:299)
>   at 
> com.datatorrent.stram.StreamingContainerManagerTest.testAppDataPush(StreamingContainerManagerTest.java:955)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createReqestAndRun(JUnitCoreWrapper.java:139)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:111)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:84)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:138)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> 

[jira] [Closed] (APEXCORE-387) Add ponymail forum link to apex website

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-387.
---
Resolution: Done

> Add ponymail forum link to apex website
> ---
>
> Key: APEXCORE-387
> URL: https://issues.apache.org/jira/browse/APEXCORE-387
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>Priority: Minor
>
> Add ponymail forum link to apex website



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-526:

Issue Type: Task  (was: Documentation)

> Publish javadoc for releases on ASF infrastructure 
> ---
>
> Key: APEXCORE-526
> URL: https://issues.apache.org/jira/browse/APEXCORE-526
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Reporter: Thomas Weise
>Assignee: Munagala V. Ramanath
>
> Every release should have the javadocs published and we should have it linked 
> from the download page, as is the case with user docs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-526.
---
Resolution: Done

> Publish javadoc for releases on ASF infrastructure 
> ---
>
> Key: APEXCORE-526
> URL: https://issues.apache.org/jira/browse/APEXCORE-526
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Documentation
>Reporter: Thomas Weise
>Assignee: Munagala V. Ramanath
>
> Every release should have the javadocs published and we should have it linked 
> from the download page, as is the case with user docs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-370) Add self-assessment project maturity model to website

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-370.
---
Resolution: Done

> Add self-assessment project maturity model to website
> -
>
> Key: APEXCORE-370
> URL: https://issues.apache.org/jira/browse/APEXCORE-370
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>  Labels: tlp
>
> Add self-assessment project maturity model to apex website
> This should be used on: 
> https://community.apache.org/apache-way/apache-project-maturity-model.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-370) Add self-assessment project maturity model to website

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-370:

Component/s: Website

> Add self-assessment project maturity model to website
> -
>
> Key: APEXCORE-370
> URL: https://issues.apache.org/jira/browse/APEXCORE-370
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>  Labels: tlp
>
> Add self-assessment project maturity model to apex website
> This should be used on: 
> https://community.apache.org/apache-way/apache-project-maturity-model.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-514) Apache Apex website update

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-514:

Priority: Minor  (was: Major)

> Apache Apex website update
> --
>
> Key: APEXCORE-514
> URL: https://issues.apache.org/jira/browse/APEXCORE-514
> Project: Apache Apex Core
>  Issue Type: Improvement
>  Components: Website
>Reporter: Michelle Xiao
>Assignee: Michelle Xiao
>Priority: Minor
>  Labels: features
>
> Update Apache Apex website:
> 1. Nav bar: add "Powered By Apex" and "Roadmap"; add an anchor Contributing 
> and a  link to Newest Apex Questions on Stack Overflow under Community;
> 2. Home page: add another "Download" after Github under Apache Apex section;
> 3. Docs page: add top navigation tabs linking to each section in this page, 
> navigation tab includes all section titles in this page



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-457) Add documentation for security options for STRAM web services

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-457:

Component/s: Documentation

> Add documentation for security options for STRAM web services
> -
>
> Key: APEXCORE-457
> URL: https://issues.apache.org/jira/browse/APEXCORE-457
> Project: Apache Apex Core
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 3.4.0
>Reporter: Pramod Immaneni
>Assignee: Pramod Immaneni
>
> Security can be enabled for STRAM web services. Add documentation for the 
> available options and how security works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-320) Create "Who We Are" page

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-320.
---
Resolution: Done

> Create "Who We Are" page
> 
>
> Key: APEXCORE-320
> URL: https://issues.apache.org/jira/browse/APEXCORE-320
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Chris Nauroth
>Assignee: Thomas Weise
>  Labels: tlp
>
> CS10
> The project maintains a public list of its contributors who have decision
> power -- the project's PMC (Project Management Committee) consists of
> those contributors.
> I couldn't find a "Who We Are" page at apex.incubator.apache.org.  I think
> the information is accurate in the incubation status page though.
> Example: https://hadoop.apache.org/who.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (APEXCORE-354) Add forum link for mailing lists

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reopened APEXCORE-354:
-

> Add forum link for mailing lists  
> --
>
> Key: APEXCORE-354
> URL: https://issues.apache.org/jira/browse/APEXCORE-354
> Project: Apache Apex Core
>  Issue Type: Task
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>
> Add nabble forum links to maling list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-309) Site unable to update releases due to fetch-versions errors

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-309.
---

> Site unable to update releases due to fetch-versions errors
> ---
>
> Key: APEXCORE-309
> URL: https://issues.apache.org/jira/browse/APEXCORE-309
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Sasha Parfenov
>Assignee: Sasha Parfenov
>
> When running following release update command for incubator-apex-site 
> repository
> {code}
> gulp fetch-versions
> {code}
> following errors can be seen:
> {code}
> [13:13:26] Using gulpfile ~/workspace/incubator-apex-site/gulpfile.js
> [13:13:26] Starting 'fetch-versions'...
> /Users/sasha/workspace/incubator-apex-site/gulpfile.js:354
> if (parts[1].replace(/^refs\/tags\/v?/, '') === release.versio
> ^
> TypeError: Cannot read property 'replace' of undefined
> at /Users/sasha/workspace/incubator-apex-site/gulpfile.js:354:29
> at ChildProcess.exithandler (child_process.js:742:7)
> at ChildProcess.emit (events.js:110:17)
> at maybeClose (child_process.js:1015:16)
> at Socket. (child_process.js:1183:11)
> at Socket.emit (events.js:107:17)
> at Pipe.close (net.js:485:12)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-311) Fix release date formatting

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-311.
---

> Fix release date formatting
> ---
>
> Key: APEXCORE-311
> URL: https://issues.apache.org/jira/browse/APEXCORE-311
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Sasha Parfenov
>Assignee: Sasha Parfenov
>Priority: Minor
>
> Current release date formatting on apex site, does not provide correct zero 
> padding for months or days, making it harder to read and identify individual 
> dates in a list of releases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (APEXCORE-123) Node Locality doesn't work with CDH

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reassigned APEXCORE-123:
---

Assignee: (was: gaurav gupta)

> Node Locality doesn't work with CDH
> ---
>
> Key: APEXCORE-123
> URL: https://issues.apache.org/jira/browse/APEXCORE-123
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: gaurav gupta
>
> Node Locality doesn't work on CDH. Stram App Master keeps on asking for 
> resources from RM.
> 2014-07-28 17:11:37,879 INFO com.datatorrent.stram.StreamingAppMasterService: 
> Asking RM for containers: [Capability[]Priority[0], 
> Capability[]Priority[1]]
> 2014-07-28 17:11:37,880 INFO com.datatorrent.stram.StreamingAppMasterService: 
> Requested container: Capability[]Priority[0]
> 2014-07-28 17:11:37,880 INFO org.apache.hadoop.yarn.util.RackResolver: 
> Resolved node23 to /default-rack
> 2014-07-28 17:11:37,885 INFO com.datatorrent.stram.StreamingAppMasterService: 
> Requested container: Capability[]Priority[1]
> 2014-07-28 17:11:37,885 INFO org.apache.hadoop.yarn.util.RackResolver: 
> Resolved node23 to /default-rack
> 2014-07-28 17:12:08,930 INFO com.datatorrent.stram.StreamingAppMasterService: 
> Asking RM for containers: [Capability[]Priority[1], 
> Capability[]Priority[0]]
> 2014-07-28 17:12:08,930 INFO com.datatorrent.stram.StreamingAppMasterService: 
> Requested container: Capability[]Priority[1]
> 2014-07-28 17:12:08,930 INFO org.apache.hadoop.yarn.util.RackResolver: 
> Resolved node23 to /default-rack
> 2014-07-28 17:12:08,930 INFO com.datatorrent.stram.StreamingAppMasterService: 
> Requested container: Capability[]Priority[0]
> 2014-07-28 17:12:08,930 INFO org.apache.hadoop.yarn.util.RackResolver: 
> Resolved node23 to /default-rack



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970001#comment-15970001
 ] 

Vlad Rozov commented on APEXCORE-699:
-

It will be good to have VersionInfo defined as {byte major; byte minor; byte 
patch} and getVersion() to return VersionInfo instead of int. getVersion should 
also pass platform plugin API version to getVersion() and the plugin can throw 
an incompatible exception (for example).

> Investigate versioning for plugins
> --
>
> Key: APEXCORE-699
> URL: https://issues.apache.org/jira/browse/APEXCORE-699
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Pramod Immaneni
>Assignee: Tushar Gosavi
>Priority: Minor
>
> Having versioning information in the plugin would help in dealing with 
> compatibility with older plugins when the plugin interface changes. This 
> needs to be investigated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-316) Upstream operator continues to use DefaultStatefulStreamCode even when different StreamCodec set

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-316.
-
Resolution: Cannot Reproduce
  Assignee: (was: Timothy Farkas)

Please reopen with reproducible scenario

> Upstream operator continues to use DefaultStatefulStreamCode even when 
> different StreamCodec set
> 
>
> Key: APEXCORE-316
> URL: https://issues.apache.org/jira/browse/APEXCORE-316
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Timothy Farkas
>
> This happens when the StreamCodec attribute is set of when the getStreamCodec 
> method of an input port is overriden. The only way to get things to work is 
> to always use/extend DefaultStatefulStreamCodec.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977647#comment-15977647
 ] 

Vlad Rozov commented on APEXCORE-699:
-

I guess that the proper way to support compatible Plugin interface 
modifications and versioning is to extend an existing interface. For example, 
if a new version of a Plugin introduces new method foo(), the new version 
should be defined as
{code}
interface PluginV2 extends Plugin {
  void foo();
}
{code}

On the other side, plugins should be able to check engine version and prevent 
the platform from loading plugin if the platform does not meet version 
requirements. Such information can be passed using PluginContext and does not 
require Plugin interface changes.

With the proposed design, will it be OK to exclude Plugin versioning changes 
from 3.6.0 release?

> Investigate versioning for plugins
> --
>
> Key: APEXCORE-699
> URL: https://issues.apache.org/jira/browse/APEXCORE-699
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Pramod Immaneni
>Assignee: Tushar Gosavi
>Priority: Minor
> Fix For: 3.6.0
>
>
> Having versioning information in the plugin would help in dealing with 
> compatibility with older plugins when the plugin interface changes. This 
> needs to be investigated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-702) Mark ApexPlugin as Evolving

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-702.
-
   Resolution: Fixed
Fix Version/s: 3.6.0

> Mark ApexPlugin as Evolving
> ---
>
> Key: APEXCORE-702
> URL: https://issues.apache.org/jira/browse/APEXCORE-702
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Tushar Gosavi
>Assignee: Tushar Gosavi
>Priority: Minor
> Fix For: 3.6.0
>
>
> Make ApexPlugin and related classes as Evolving and this part of code is new 
> and might change in future.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-709) Refactor changes done through APEXCORE-575

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-709.
-
Resolution: Fixed

> Refactor changes done through APEXCORE-575
> --
>
> Key: APEXCORE-709
> URL: https://issues.apache.org/jira/browse/APEXCORE-709
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Tushar Gosavi
>Assignee: Tushar Gosavi
>Priority: Minor
> Fix For: 3.6.0
>
>
> Handle additional review comments on pull request 422.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-143) Graceful shutdown of test applications

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-143:

Fix Version/s: (was: 3.6.0)

> Graceful shutdown of test applications
> --
>
> Key: APEXCORE-143
> URL: https://issues.apache.org/jira/browse/APEXCORE-143
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Priyanka Nambiar
>Assignee: Vlad Rozov
>Priority: Minor
>
> During writing application tests, when we call shutdown on Controller 
> (specifically StramLocalCluster controller) it doesn't call teardown of 
> operators like it happens when application is terminated from UI or CLI.
> As teardown of operators is not called, if operator is suppose to do any 
> operation w.t.r. resources it doesn't happen. And if tests depends on that it 
> could fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-692) Apex Dev Setup doc should reference download page

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-692:

Fix Version/s: (was: 3.6.0)

> Apex Dev Setup doc should reference download page
> -
>
> Key: APEXCORE-692
> URL: https://issues.apache.org/jira/browse/APEXCORE-692
> Project: Apache Apex Core
>  Issue Type: Documentation
>  Components: Documentation
>Reporter: Dean Lockgaard
>Assignee: Dean Lockgaard
>Priority: Minor
>
> In the Sandbox section of the Apache Apex Development Environment Setup 
> documentation 
> (https://apex.apache.org/docs/apex/apex_development_setup/#sandbox), 
> instructions are provided for a vendor-specific Sandbox.
> These instructions should be changed to reference the Apache Apex Sandbox 
> instead (https://hub.docker.com/r/apacheapex/sandbox).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-634) Apex Platform unable to set unifier attributes for modules in DAG

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-634:

Priority: Minor  (was: Major)

> Apex Platform unable to set unifier attributes for modules in DAG
> -
>
> Key: APEXCORE-634
> URL: https://issues.apache.org/jira/browse/APEXCORE-634
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Deepak Narkhede
>Assignee: Deepak Narkhede
>Priority: Minor
> Fix For: 3.6.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-634) Apex Platform unable to set unifier attributes for modules in DAG

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-634.
-
Resolution: Fixed

> Apex Platform unable to set unifier attributes for modules in DAG
> -
>
> Key: APEXCORE-634
> URL: https://issues.apache.org/jira/browse/APEXCORE-634
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Deepak Narkhede
>Assignee: Deepak Narkhede
> Fix For: 3.6.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (APEXCORE-388) Links to 3rd party pages should follow guidelines defined at http://www.apache.org/foundation/marks/linking

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov closed APEXCORE-388.
---

> Links to 3rd party pages should follow guidelines defined at 
> http://www.apache.org/foundation/marks/linking 
> 
>
> Key: APEXCORE-388
> URL: https://issues.apache.org/jira/browse/APEXCORE-388
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Hitesh Shah
>Assignee: Sasha Parfenov
>
> For examples, links to DataTorrent on the 
> http://apex.incubator.apache.org/downloads.html page should have the nofollow 
> attribute. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXCORE-703) Window processing timeout for finished/undeployed container

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970233#comment-15970233
 ] 

Vlad Rozov commented on APEXCORE-703:
-

[~thw] I don't see undeployed operators being removed from the plan immediately 
and the state of such operators is not updated, so they are still considered to 
be ACTIVE and are subject to the blocked operators check. Why 
StreamingContainerManager does not set the state of an operator to INACTIVE 
when it is added to the list of operators to undeploy?
{noformat}
case SHUTDOWN:
  // schedule operator deactivation against the windowId
  // will be processed once window is committed and all dependent 
operators completed processing
  long windowId = oper.stats.currentWindowId.get();
  if (ohb.windowStats != null && !ohb.windowStats.isEmpty()) {
windowId = ohb.windowStats.get(ohb.windowStats.size() - 
1).windowId;
  }
  LOG.debug("Operator {} deactivated at window {}", oper, windowId);
  synchronized (this.shutdownOperators) {
Set deactivatedOpers = 
this.shutdownOperators.get(windowId);
if (deactivatedOpers == null) {
  this.shutdownOperators.put(windowId, deactivatedOpers = new 
HashSet<>());
}
deactivatedOpers.add(oper);
  }
  sca.undeployOpers.add(oper.getId());
  ---> can we mark operator as inactive here? 
  slowestUpstreamOp.remove(oper);
  // record operator stop event
  recordEventAsync(new StramEvent.StopOperatorEvent(oper.getName(), 
oper.getId(), oper.getContainer().getExternalId()));
  break;
{noformat} 

> Window processing timeout for finished/undeployed container
> ---
>
> Key: APEXCORE-703
> URL: https://issues.apache.org/jira/browse/APEXCORE-703
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Daniel Halperin
>
> Using Apex 3.5.0 with Apache Beam, I have a 10-container pipeline. The first 
> container, id #1, finishes and gets undeployed at 12:41:10 PM.
> Then, 60s later (at 12:42:10 PM), Apex decides that container is blocked 
> because no data has been received for 60s, declares failure, and restarts it.
> This would seem to be a bug -- shouldn't finished and undeployed operators be 
> deregistered from the timeout logic that is detecting stuck operators?
> Log below
> {code}
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Undeploy request: [1]
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> undeploy
> INFO: Undeploy complete.
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198930012, last window id change time 1492198869957, window 
> processing timeout millis 6
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateCheckpoints
> INFO: Blocked operator PTOperator[id=1,name=TextIO.Read/Read] container 
> PTContainer[id=1(container-6),state=ACTIVE] time 60055ms
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Received shutdown request
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StramLocalCluster run
> INFO: Container container-6 restart.
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> scheduleContainerRestart
> INFO: Initiating recovery for container-6@localhost
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198931015, last window id change time 1492198869957, window 
> processing timeout millis 6
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXCORE-703) Window processing timeout for finished/undeployed container

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970240#comment-15970240
 ] 

Vlad Rozov commented on APEXCORE-703:
-

Why not to have a state that indicates that an operator is undeployed, but 
can't be removed from the plan till the checkpoint barrier is reached? Can't 
INACTIVE play such role? If not, can we introduce a new state? While 
shutdownOperators may be used to exclude an operator from being marked as 
blocked, the state is already used to mark only ACTIVE operators as blocked.

> Window processing timeout for finished/undeployed container
> ---
>
> Key: APEXCORE-703
> URL: https://issues.apache.org/jira/browse/APEXCORE-703
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Daniel Halperin
>
> Using Apex 3.5.0 with Apache Beam, I have a 10-container pipeline. The first 
> container, id #1, finishes and gets undeployed at 12:41:10 PM.
> Then, 60s later (at 12:42:10 PM), Apex decides that container is blocked 
> because no data has been received for 60s, declares failure, and restarts it.
> This would seem to be a bug -- shouldn't finished and undeployed operators be 
> deregistered from the timeout logic that is detecting stuck operators?
> Log below
> {code}
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Undeploy request: [1]
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> undeploy
> INFO: Undeploy complete.
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198930012, last window id change time 1492198869957, window 
> processing timeout millis 6
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateCheckpoints
> INFO: Blocked operator PTOperator[id=1,name=TextIO.Read/Read] container 
> PTContainer[id=1(container-6),state=ACTIVE] time 60055ms
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Received shutdown request
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StramLocalCluster run
> INFO: Container container-6 restart.
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> scheduleContainerRestart
> INFO: Initiating recovery for container-6@localhost
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198931015, last window id change time 1492198869957, window 
> processing timeout millis 6
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-511) DAG.addOperator, addStream and addModule should check for null and empty names

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-511.
-
   Resolution: Implemented
Fix Version/s: 3.6.0

> DAG.addOperator, addStream and addModule should check for null and empty names
> --
>
> Key: APEXCORE-511
> URL: https://issues.apache.org/jira/browse/APEXCORE-511
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Vlad Rozov
>Assignee: Oliver Winke
>Priority: Minor
>  Labels: newbie
> Fix For: 3.6.0
>
>
> Operators, Streams and Modules should have valid not empty names.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXCORE-703) Window processing timeout for finished/undeployed container

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970454#comment-15970454
 ] 

Vlad Rozov commented on APEXCORE-703:
-

I believe that the second test case is already covered for example in 
AtMostOnceTest.testLinearInputOperatorRecovery. Let me know if you think that a 
separate unit test in StreamingContainerManagerTest is required. I open PR to 
make sure that we agree on the proposed fix and will add 2 or 3 additional unit 
tests. One that simulates the bug and another in 
StreamingContainerManagerTest.testOperatorShutdown.

> Window processing timeout for finished/undeployed container
> ---
>
> Key: APEXCORE-703
> URL: https://issues.apache.org/jira/browse/APEXCORE-703
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Daniel Halperin
>Assignee: Vlad Rozov
> Fix For: 3.6.0
>
>
> Using Apex 3.5.0 with Apache Beam, I have a 10-container pipeline. The first 
> container, id #1, finishes and gets undeployed at 12:41:10 PM.
> Then, 60s later (at 12:42:10 PM), Apex decides that container is blocked 
> because no data has been received for 60s, declares failure, and restarts it.
> This would seem to be a bug -- shouldn't finished and undeployed operators be 
> deregistered from the timeout logic that is detecting stuck operators?
> Log below
> {code}
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Undeploy request: [1]
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> undeploy
> INFO: Undeploy complete.
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198930012, last window id change time 1492198869957, window 
> processing timeout millis 6
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateCheckpoints
> INFO: Blocked operator PTOperator[id=1,name=TextIO.Read/Read] container 
> PTContainer[id=1(container-6),state=ACTIVE] time 60055ms
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Received shutdown request
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StramLocalCluster run
> INFO: Container container-6 restart.
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> scheduleContainerRestart
> INFO: Initiating recovery for container-6@localhost
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198931015, last window id change time 1492198869957, window 
> processing timeout millis 6
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXCORE-703) Window processing timeout for finished/undeployed container

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970407#comment-15970407
 ] 

Vlad Rozov commented on APEXCORE-703:
-

I don't see why INACTIVE operators can not be redeployed and marked as ACTIVE 
in a case of a recovery. They are still part of the plan anyway.

> Window processing timeout for finished/undeployed container
> ---
>
> Key: APEXCORE-703
> URL: https://issues.apache.org/jira/browse/APEXCORE-703
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Daniel Halperin
>
> Using Apex 3.5.0 with Apache Beam, I have a 10-container pipeline. The first 
> container, id #1, finishes and gets undeployed at 12:41:10 PM.
> Then, 60s later (at 12:42:10 PM), Apex decides that container is blocked 
> because no data has been received for 60s, declares failure, and restarts it.
> This would seem to be a bug -- shouldn't finished and undeployed operators be 
> deregistered from the timeout logic that is detecting stuck operators?
> Log below
> {code}
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Undeploy request: [1]
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> undeploy
> INFO: Undeploy complete.
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198930012, last window id change time 1492198869957, window 
> processing timeout millis 6
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateCheckpoints
> INFO: Blocked operator PTOperator[id=1,name=TextIO.Read/Read] container 
> PTContainer[id=1(container-6),state=ACTIVE] time 60055ms
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Received shutdown request
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StramLocalCluster run
> INFO: Container container-6 restart.
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> scheduleContainerRestart
> INFO: Initiating recovery for container-6@localhost
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198931015, last window id change time 1492198869957, window 
> processing timeout millis 6
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXCORE-703) Window processing timeout for finished/undeployed container

[Vlad Rozov (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970413#comment-15970413
 ] 

Vlad Rozov commented on APEXCORE-703:
-

I'll open a PR. Do you have a suggestion for additional unit tests?

> Window processing timeout for finished/undeployed container
> ---
>
> Key: APEXCORE-703
> URL: https://issues.apache.org/jira/browse/APEXCORE-703
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Daniel Halperin
>Assignee: Vlad Rozov
>
> Using Apex 3.5.0 with Apache Beam, I have a 10-container pipeline. The first 
> container, id #1, finishes and gets undeployed at 12:41:10 PM.
> Then, 60s later (at 12:42:10 PM), Apex decides that container is blocked 
> because no data has been received for 60s, declares failure, and restarts it.
> This would seem to be a bug -- shouldn't finished and undeployed operators be 
> deregistered from the timeout logic that is detecting stuck operators?
> Log below
> {code}
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Undeploy request: [1]
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> undeploy
> INFO: Undeploy complete.
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198930012, last window id change time 1492198869957, window 
> processing timeout millis 6
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateCheckpoints
> INFO: Blocked operator PTOperator[id=1,name=TextIO.Read/Read] container 
> PTContainer[id=1(container-6),state=ACTIVE] time 60055ms
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Received shutdown request
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StramLocalCluster run
> INFO: Container container-6 restart.
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> scheduleContainerRestart
> INFO: Initiating recovery for container-6@localhost
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198931015, last window id change time 1492198869957, window 
> processing timeout millis 6
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (APEXCORE-703) Window processing timeout for finished/undeployed container

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov reassigned APEXCORE-703:
---

Assignee: Vlad Rozov

> Window processing timeout for finished/undeployed container
> ---
>
> Key: APEXCORE-703
> URL: https://issues.apache.org/jira/browse/APEXCORE-703
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Daniel Halperin
>Assignee: Vlad Rozov
>
> Using Apex 3.5.0 with Apache Beam, I have a 10-container pipeline. The first 
> container, id #1, finishes and gets undeployed at 12:41:10 PM.
> Then, 60s later (at 12:42:10 PM), Apex decides that container is blocked 
> because no data has been received for 60s, declares failure, and restarts it.
> This would seem to be a bug -- shouldn't finished and undeployed operators be 
> deregistered from the timeout logic that is detecting stuck operators?
> Log below
> {code}
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Undeploy request: [1]
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> undeploy
> INFO: Undeploy complete.
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198930012, last window id change time 1492198869957, window 
> processing timeout millis 6
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateCheckpoints
> INFO: Blocked operator PTOperator[id=1,name=TextIO.Read/Read] container 
> PTContainer[id=1(container-6),state=ACTIVE] time 60055ms
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Received shutdown request
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StramLocalCluster run
> INFO: Container container-6 restart.
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> scheduleContainerRestart
> INFO: Initiating recovery for container-6@localhost
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198931015, last window id change time 1492198869957, window 
> processing timeout millis 6
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-709) Refactor changes done through APEXCORE-575

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-709:

Fix Version/s: 3.6.0

> Refactor changes done through APEXCORE-575
> --
>
> Key: APEXCORE-709
> URL: https://issues.apache.org/jira/browse/APEXCORE-709
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Tushar Gosavi
>Assignee: Tushar Gosavi
>Priority: Minor
> Fix For: 3.6.0
>
>
> Handle additional review comments on pull request 422.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-703) Window processing timeout for finished/undeployed container

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-703.
-
Resolution: Fixed

> Window processing timeout for finished/undeployed container
> ---
>
> Key: APEXCORE-703
> URL: https://issues.apache.org/jira/browse/APEXCORE-703
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Daniel Halperin
>Assignee: Vlad Rozov
> Fix For: 3.6.0
>
>
> Using Apex 3.5.0 with Apache Beam, I have a 10-container pipeline. The first 
> container, id #1, finishes and gets undeployed at 12:41:10 PM.
> Then, 60s later (at 12:42:10 PM), Apex decides that container is blocked 
> because no data has been received for 60s, declares failure, and restarts it.
> This would seem to be a bug -- shouldn't finished and undeployed operators be 
> deregistered from the timeout logic that is detecting stuck operators?
> Log below
> {code}
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Undeploy request: [1]
> Apr 14, 2017 12:41:10 PM com.datatorrent.stram.engine.StreamingContainer 
> undeploy
> INFO: Undeploy complete.
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198930012, last window id change time 1492198869957, window 
> processing timeout millis 6
> Apr 14, 2017 12:42:10 PM com.datatorrent.stram.StreamingContainerManager 
> updateCheckpoints
> INFO: Blocked operator PTOperator[id=1,name=TextIO.Read/Read] container 
> PTContainer[id=1(container-6),state=ACTIVE] time 60055ms
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.engine.StreamingContainer 
> processHeartbeatResponse
> INFO: Received shutdown request
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StramLocalCluster run
> INFO: Container container-6 restart.
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> scheduleContainerRestart
> INFO: Initiating recovery for container-6@localhost
> Apr 14, 2017 12:42:11 PM com.datatorrent.stram.StreamingContainerManager 
> updateRecoveryCheckpoints
> WARNING: Marking operator PTOperator[id=1,name=TextIO.Read/Read] blocked 
> committed window , recovery window , current 
> time 1492198931015, last window id change time 1492198869957, window 
> processing timeout millis 6
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-699:

Fix Version/s: (was: 3.6.0)

> Investigate versioning for plugins
> --
>
> Key: APEXCORE-699
> URL: https://issues.apache.org/jira/browse/APEXCORE-699
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Pramod Immaneni
>Assignee: Tushar Gosavi
>Priority: Minor
>
> Having versioning information in the plugin would help in dealing with 
> compatibility with older plugins when the plugin interface changes. This 
> needs to be investigated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-655) Support LATEST as archetype version when creating a project

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-655.
-
   Resolution: Implemented
Fix Version/s: 3.6.0

> Support LATEST as archetype version when creating a project 
> 
>
> Key: APEXCORE-655
> URL: https://issues.apache.org/jira/browse/APEXCORE-655
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Thomas Weise
>Priority: Minor
> Fix For: 3.6.0
>
>
> Rather than keep on replacing the Apex archetype version number in various 
> examples, Maven supports LATEST to refer to the latest released archetype 
> version. 
> This requires a change to decouple resolution of Apex dependency version from 
> archetype version to replace the Apex version when the archetype is created 
> vs. when the project is created.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-426) Support work preserving AM recovery

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-426.
-
   Resolution: Fixed
Fix Version/s: 3.6.0

> Support work preserving AM recovery
> ---
>
> Key: APEXCORE-426
> URL: https://issues.apache.org/jira/browse/APEXCORE-426
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Thomas Weise
>Assignee: Sandesh
>  Labels: apex-hadoop-version
> Fix For: 3.6.0
>
>
> On app master failure, the streaming containers should continue running. 
> As of 2.2, YARN will automatically terminate all containers and the 
> replacement app master will relaunch them. Once we move to a newer minimum 
> Hadoop version, we should leverage work preserving restart.
> The mechanism in Apex containers to locate the new master process are already 
> in place.
>  
> Test Cases:
> 1. Kill the app-master - only app-master container id should change, all the 
> other containers id should remain same.
> 2. Kill the app-master and few other containers, make sure that killed 
> containers are recovered.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXCORE-656) Upgrade org.apache.httpcomponents

[Vlad Rozov (JIRA)]

Vlad Rozov created APEXCORE-656:
---

 Summary: Upgrade org.apache.httpcomponents
 Key: APEXCORE-656
 URL: https://issues.apache.org/jira/browse/APEXCORE-656
 Project: Apache Apex Core
  Issue Type: Improvement
Reporter: Vlad Rozov
Assignee: Vlad Rozov
Priority: Trivial






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-656) Upgrade org.apache.httpcomponents.httpclient

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-656:

Summary: Upgrade org.apache.httpcomponents.httpclient  (was: Upgrade 
org.apache.httpcomponents)

> Upgrade org.apache.httpcomponents.httpclient
> 
>
> Key: APEXCORE-656
> URL: https://issues.apache.org/jira/browse/APEXCORE-656
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Trivial
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-677) Avoid starting StramLocalCluster in StreamingContainerManagerTest.testAppDataSources

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-677.
-
   Resolution: Fixed
Fix Version/s: 3.6.0

> Avoid starting StramLocalCluster in 
> StreamingContainerManagerTest.testAppDataSources
> 
>
> Key: APEXCORE-677
> URL: https://issues.apache.org/jira/browse/APEXCORE-677
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Trivial
> Fix For: 3.6.0
>
>
> testAppDataSources does not wait for the StramLocalCluster to be initialized, 
> so it does not need to start it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (APEXCORE-656) Upgrade org.apache.httpcomponents.httpclient

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov resolved APEXCORE-656.
-
   Resolution: Implemented
Fix Version/s: 3.6.0

> Upgrade org.apache.httpcomponents.httpclient
> 
>
> Key: APEXCORE-656
> URL: https://issues.apache.org/jira/browse/APEXCORE-656
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Trivial
> Fix For: 3.6.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXCORE-691) Use type inference for generic instance creation

[Vlad Rozov (JIRA)]

Vlad Rozov created APEXCORE-691:
---

 Summary: Use type inference for generic instance creation
 Key: APEXCORE-691
 URL: https://issues.apache.org/jira/browse/APEXCORE-691
 Project: Apache Apex Core
  Issue Type: Task
Reporter: Vlad Rozov
Assignee: Vlad Rozov
Priority: Minor


The current Java language level allows using type inference for generic 
instance creation making constructs like
{noformat}
Map  map = new HashMap();
{noformat}
unnecessary.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-699:

Priority: Minor  (was: Major)

> Investigate versioning for plugins
> --
>
> Key: APEXCORE-699
> URL: https://issues.apache.org/jira/browse/APEXCORE-699
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Pramod Immaneni
>Assignee: Tushar Gosavi
>Priority: Minor
>
> Having versioning information in the plugin would help in dealing with 
> compatibility with older plugins when the plugin interface changes. This 
> needs to be investigated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-700:

Priority: Minor  (was: Major)

> Make the plugin registration interface uniform
> --
>
> Key: APEXCORE-700
> URL: https://issues.apache.org/jira/browse/APEXCORE-700
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Pramod Immaneni
>Assignee: Pramod Immaneni
>Priority: Minor
>
> The user-facing plugin registration for DAG setup plugins is slightly 
> different from runtime plugins. It would be better to have a uniform way to 
> do this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-700:

Issue Type: Sub-task  (was: Improvement)
Parent: APEXCORE-594

> Make the plugin registration interface uniform
> --
>
> Key: APEXCORE-700
> URL: https://issues.apache.org/jira/browse/APEXCORE-700
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Pramod Immaneni
>Assignee: Pramod Immaneni
>
> The user-facing plugin registration for DAG setup plugins is slightly 
> different from runtime plugins. It would be better to have a uniform way to 
> do this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-699:

Issue Type: Sub-task  (was: Improvement)
Parent: APEXCORE-594

> Investigate versioning for plugins
> --
>
> Key: APEXCORE-699
> URL: https://issues.apache.org/jira/browse/APEXCORE-699
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Pramod Immaneni
>Assignee: Tushar Gosavi
>
> Having versioning information in the plugin would help in dealing with 
> compatibility with older plugins when the plugin interface changes. This 
> needs to be investigated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (APEXCORE-702) Mark ApexPlugin as Evolving

[Vlad Rozov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Rozov updated APEXCORE-702:

Issue Type: Sub-task  (was: Bug)
Parent: APEXCORE-594

> Mark ApexPlugin as Evolving
> ---
>
> Key: APEXCORE-702
> URL: https://issues.apache.org/jira/browse/APEXCORE-702
> Project: Apache Apex Core
>  Issue Type: Sub-task
>Reporter: Tushar Gosavi
>Assignee: Tushar Gosavi
>
> Make ApexPlugin and related classes as Evolving and this part of code is new 
> and might change in future.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)