Re: old versions in https://dist.apache.org/repos/dist/release/apex/

Should we limit [1 ] to the latest core and the latest malhar according to [2 ] and point links for older releases on the download page to [3

Re: binary releases

+1. Should we create one single binary distribution that includes core and examples from malhar or have binary distribution of the core and sample applications as two separate binary distributions/downloads? Thank you, Vlad On 5/5/17 17:03, Pramod Immaneni wrote: I wanted to see how the

[jira] [Updated] (APEXMALHAR-2484) BlockWriter for writing the part files into the specified directory

[ https://issues.apache.org/jira/browse/APEXMALHAR-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Ganelin updated APEXMALHAR-2484: - Fix Version/s: 3.8.0 > BlockWriter for writing the part files into the specified

[jira] [Resolved] (APEXMALHAR-2484) BlockWriter for writing the part files into the specified directory

[ https://issues.apache.org/jira/browse/APEXMALHAR-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Ganelin resolved APEXMALHAR-2484. -- Resolution: Fixed > BlockWriter for writing the part files into the specified

Re: binary releases

Hi, Just be aware that it may require different LICENSE and NOTICE and the contents of the binary are likely to different to the source release. [1] Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#binary

Re: binary releases

We should, it is good for the community. Thks Amol E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre* www.datatorrent.com On Fri, May 5, 2017 at 5:03 PM, Pramod Immaneni wrote: > I wanted to see how the community felt about also publishing binaries as

binary releases

I wanted to see how the community felt about also publishing binaries as part of the release. Hadoop, for example, has been doing this http://hadoop.apache.org/releases.html https://dist.apache.org/repos/dist/release/hadoop/common/hadoop-2.8.0/ Thanks

[GitHub] apex-malhar pull request #616: APEXMALHAR-2487 Added support for Snappy comp...

GitHub user ilganeli opened a pull request: https://github.com/apache/apex-malhar/pull/616 APEXMALHAR-2487 Added support for Snappy compression in FilterStreamProvider * Based on existing code to output Gzip or CipherText this patch adds support for writing data out as

[jira] [Commented] (APEXMALHAR-2487) Malhar should support outputting data in Snappy compression

[ https://issues.apache.org/jira/browse/APEXMALHAR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999009#comment-15999009 ] ASF GitHub Bot commented on APEXMALHAR-2487: GitHub user ilganeli opened a pull request:

Re: Write access to Apex/Malhar GH

Hey Ilya, I used the command line to merge PRs as it needs to go back to the apache repository. Thanks On Fri, May 5, 2017 at 2:35 PM, Ganelin, Ilya wrote: > Hello, all – I was attempting to close out one of the open PRs and it > seems I may not have write access

[GitHub] apex-malhar pull request #615: APEXMALHAR-2487 Added support for Snappy comp...

Github user ilganeli closed the pull request at: https://github.com/apache/apex-malhar/pull/615 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Commented] (APEXMALHAR-2487) Malhar should support outputting data in Snappy compression

[ https://issues.apache.org/jira/browse/APEXMALHAR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999000#comment-15999000 ] ASF GitHub Bot commented on APEXMALHAR-2487: Github user ilganeli closed the pull request

Re: old versions in https://dist.apache.org/repos/dist/release/apex/

It is (should be) available from the Apache archive. Thank you, Vlad On 5/5/17 09:47, Pramod Immaneni wrote: Is core 3.4.0 not available anymore even though there is a link on the download page? On Fri, May 5, 2017 at 8:47 AM, Thomas Weise > wrote:

Re: old versions in https://dist.apache.org/repos/dist/release/apex/

Is core 3.4.0 not available anymore even though there is a link on the download page? On Fri, May 5, 2017 at 8:47 AM, Thomas Weise wrote: > See https://github.com/apache/apex-site#updating-downloads-page > > added 3.6.1 > > Any thoughts on when to remove 3.2.2, 3.3.1 and

Re: old versions in https://dist.apache.org/repos/dist/release/apex/

See https://github.com/apache/apex-site#updating-downloads-page added 3.6.1 Any thoughts on when to remove 3.2.2, 3.3.1 and other old patch versions in JIRA that won't see a future release? On Fri, May 5, 2017 at 7:18 AM, Vlad Rozov wrote: > My understanding is that

Re: old versions in https://dist.apache.org/repos/dist/release/apex/

My understanding is that it is not fully automatic and involves manual step in updating and committing the "release.json" file and only after that step the download page will be regenerated. Do I miss anything? Any reason 3.6.1 was not added to JIRA? Thank you, Vlad On 5/5/17 07:09, Thomas

Re: old versions in https://dist.apache.org/repos/dist/release/apex/

I removed 3.4.0 since due to change in archive file name it does not match the download page structure. It will automatically go away when the download page is regenerated. On Fri, May 5, 2017 at 6:59 AM, Vlad Rozov wrote: > apex core 3.4.0 is listed on the download

Re: old versions in https://dist.apache.org/repos/dist/release/apex/

apex core 3.4.0 is listed on the download page and it is not part of https://dist.apache.org/repos/dist/release/apex/ version 3.6.1 is missing in JIRA. Thank you, Vlad On 5/5/17 06:55, Thomas Weise wrote: Yes, we should keep them as otherwise they will also not be listed on downloads. On

Re: old versions in https://dist.apache.org/repos/dist/release/apex/

Yes, we should keep them as otherwise they will also not be listed on downloads. On Fri, May 5, 2017 at 6:53 AM, Vlad Rozov wrote: > I removed 3.5.0 RC1 from dev. Do we need to keep apex 3.5.0 and malhar > 3.5.0 and 3.6.0 in release? > > Thank you, > > Vlad > > On

old versions in https://dist.apache.org/repos/dist/release/apex/

I removed 3.5.0 RC1 from dev. Do we need to keep apex 3.5.0 and malhar 3.5.0 and 3.6.0 in release? Thank you, Vlad On 5/5/17 06:41, Thomas Weise wrote: Move of RC to release is done and new JIRA version added. On Fri, May 5, 2017 at 6:34 AM, Vlad Rozov wrote:

Re: release activties

Move of RC to release is done and new JIRA version added. On Fri, May 5, 2017 at 6:34 AM, Vlad Rozov wrote: > I'll help with moving RC candidate from dev to release. Do you have > permission to publish artifacts to maven? > > Thank you, > > Vlad > > On 5/5/17 06:21,

Re: release activties

I'll help with moving RC candidate from dev to release. Do you have permission to publish artifacts to maven? Thank you, Vlad On 5/5/17 06:21, Thomas Weise wrote: You should be able to complete the release activities except the JIRA version. What do you mean by "release svn repository"?

release activties

You should be able to complete the release activities except the JIRA version. What do you mean by "release svn repository"? Also, release process states that you should turn off JIRA notifications when closing issues (to not flood mailing list). Subject of closing vote should start with

Re: [VOTE] Apache Apex Core Release 3.6.0 (RC1)

I do not seems to have permissions to create versions in JIRA as specified release steps (http://apex.apache.org/release.html). Can someone create new release tags for 3.7.0 and 3.6.1. Thank You, -Tushar. On Fri, May 5, 2017 at 3:04 PM, Tushar Gosavi wrote: > As a

[jira] [Closed] (APEXCORE-585) Latency should be calculated only after the first window has been complete

[ https://issues.apache.org/jira/browse/APEXCORE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-585. -- Closing after 3.6.0 release > Latency should be calculated only after the first window has been

[jira] [Closed] (APEXCORE-715) Remove unnecessary @Evolving annotation in engine

[ https://issues.apache.org/jira/browse/APEXCORE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-715. -- Closing after 3.6.0 release > Remove unnecessary @Evolving annotation in engine >

[jira] [Closed] (APEXCORE-617) InputNodeTest intermittently fails with ConcurrentModificationException

[ https://issues.apache.org/jira/browse/APEXCORE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-617. -- Closing after 3.6.0 release > InputNodeTest intermittently fails with

[jira] [Closed] (APEXCORE-641) Subscribers/DataListeners may not be scheduled to execute even when they have data to process

[ https://issues.apache.org/jira/browse/APEXCORE-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-641. -- Closing after 3.6.0 release > Subscribers/DataListeners may not be scheduled to execute even

[jira] [Closed] (APEXCORE-596) Committed method on operators not called when stream locality is THREAD_LOCAL

[ https://issues.apache.org/jira/browse/APEXCORE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-596. -- Closing after 3.6.0 release > Committed method on operators not called when stream locality is

[jira] [Closed] (APEXCORE-662) Raise StramEvent for heartbeat miss

[ https://issues.apache.org/jira/browse/APEXCORE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-662. -- Closing after 3.6.0 release > Raise StramEvent for heartbeat miss >

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

[ https://issues.apache.org/jira/browse/APEXCORE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-683. -- Closing after 3.6.0 release > Apex client should support application packages on HDFS >

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

[ https://issues.apache.org/jira/browse/APEXCORE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-655. -- Closing after 3.6.0 release > Support RELEASE as archetype version when creating a project >

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

[ https://issues.apache.org/jira/browse/APEXCORE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-511. -- Closing after 3.6.0 release > DAG.addOperator, addStream and addModule should check for null and

[jira] [Closed] (APEXCORE-701) Upgrade Malhar version in archetype to 3.7.0

[ https://issues.apache.org/jira/browse/APEXCORE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-701. -- Closing after 3.6.0 release > Upgrade Malhar version in archetype to 3.7.0 >

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

[ https://issues.apache.org/jira/browse/APEXCORE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-671. -- Closing after 3.6.0 release > DTConfiguration utility class ValueEntry access level was changed

[jira] [Closed] (APEXCORE-644) get-app-package-operators with parent option does not work

[ https://issues.apache.org/jira/browse/APEXCORE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-644. -- Closing after 3.6.0 release > get-app-package-operators with parent option does not work >

[jira] [Closed] (APEXCORE-294) Graceful application shutdown

[ https://issues.apache.org/jira/browse/APEXCORE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-294. -- Closing after 3.6.0 release > Graceful application shutdown > - > >

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

[ https://issues.apache.org/jira/browse/APEXCORE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-575. -- Closing after 3.6.0 release > Improve application relaunch time. >

[jira] [Closed] (APEXCORE-594) Plugin support in Apex

[ https://issues.apache.org/jira/browse/APEXCORE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-594. -- Closing after 3.6.0 release > Plugin support in Apex > -- > >

[jira] [Closed] (APEXCORE-627) Unit test AtMostOnceTest intermittently fails

[ https://issues.apache.org/jira/browse/APEXCORE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-627. -- Closing after 3.6.0 release > Unit test AtMostOnceTest intermittently fails >

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

[ https://issues.apache.org/jira/browse/APEXCORE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-616. -- Closing after 3.6.0 release > Application fails to start Kerberised cluster >

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

[ https://issues.apache.org/jira/browse/APEXCORE-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-702. -- Closing after 3.6.0 release > Mark ApexPlugin as Evolving > --- > >

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

[ https://issues.apache.org/jira/browse/APEXCORE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-590. -- Closing after 3.6.0 release > Failed to restart application on MapR >

[jira] [Closed] (APEXCORE-608) Streaming Containers use stale RPC proxy after connection is closed

[ https://issues.apache.org/jira/browse/APEXCORE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-608. -- Closing after 3.6.0 release > Streaming Containers use stale RPC proxy after connection is

[jira] [Closed] (APEXCORE-678) Shutdown of application should start from input nodes

[ https://issues.apache.org/jira/browse/APEXCORE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-678. -- Closing after 3.6.0 release > Shutdown of application should start from input nodes >

[jira] [Closed] (APEXCORE-674) Change access specifier of DTConfiguration.ValueEntry to private

[ https://issues.apache.org/jira/browse/APEXCORE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-674. -- Closing after 3.6.0 release > Change access specifier of DTConfiguration.ValueEntry to private >

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

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-570. -- Closing after 3.6.0 release > Prevent upstream operators from getting too far ahead when

[jira] [Closed] (APEXCORE-654) Recovery window is not updated when Delay Operator is used along with Partitioned Operators

[ https://issues.apache.org/jira/browse/APEXCORE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-654. -- Closing after 3.6.0 release > Recovery window is not updated when Delay Operator is used along

[jira] [Closed] (APEXCORE-579) Custom control tuple support

[ https://issues.apache.org/jira/browse/APEXCORE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-579. -- Closing after 3.6.0 release > Custom control tuple support > > >

[jira] [Closed] (APEXCORE-605) Suppress bootstrap compiler warning

[ https://issues.apache.org/jira/browse/APEXCORE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-605. -- Closing after 3.6.0 release > Suppress bootstrap compiler warning >

[jira] [Closed] (APEXCORE-592) Returning description field in defaultProperties during apex cli call get-app-package-info

[ https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-592. -- Closing after 3.6.0 release > Returning description field in defaultProperties during apex cli

[jira] [Closed] (APEXCORE-624) Shutdown does not work because of incorrect logic in the AppMaster

[ https://issues.apache.org/jira/browse/APEXCORE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-624. -- Closing after 3.6.0 release > Shutdown does not work because of incorrect logic in the AppMaster

[jira] [Closed] (APEXCORE-663) Application restart not working.

[ https://issues.apache.org/jira/browse/APEXCORE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-663. -- Closing after 3.6.0 release > Application restart not working. >

[jira] [Closed] (APEXCORE-563) Have a pointer to log file name and offset in container/operator failure events

[ https://issues.apache.org/jira/browse/APEXCORE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-563. -- Closing after 3.6.0 release > Have a pointer to log file name and offset in container/operator

[jira] [Closed] (APEXCORE-680) Review container heartbeat timeout log level messages

[ https://issues.apache.org/jira/browse/APEXCORE-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-680. -- Closing after 3.6.0 release > Review container heartbeat timeout log level messages >

[jira] [Closed] (APEXCORE-577) Plugin support to inspect DAG before launch.

[ https://issues.apache.org/jira/browse/APEXCORE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-577. -- Closing after 3.6.0 release > Plugin support to inspect DAG before launch. >

[jira] [Closed] (APEXCORE-583) Buffer Server LogicalNode should not be reused by Subscribers

[ https://issues.apache.org/jira/browse/APEXCORE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-583. -- Closing after 3.6.0 release > Buffer Server LogicalNode should not be reused by Subscribers >

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

[ https://issues.apache.org/jira/browse/APEXCORE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-700. -- Closing after 3.6.0 release > Make the plugin registration interface uniform >

[jira] [Closed] (APEXCORE-597) BufferServer needs to shutdown all created execution services

[ https://issues.apache.org/jira/browse/APEXCORE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-597. -- Closing after 3.6.0 release > BufferServer needs to shutdown all created execution services >

[jira] [Closed] (APEXCORE-591) SubscribeRequestTuple has wrong buffer size when mask is zero

[ https://issues.apache.org/jira/browse/APEXCORE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-591. -- Closing after 3.6.0 release > SubscribeRequestTuple has wrong buffer size when mask is zero >

[jira] [Closed] (APEXCORE-645) StramLocalCluster does not wait for master thread termination

[ https://issues.apache.org/jira/browse/APEXCORE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-645. -- Closing after 3.6.0 release > StramLocalCluster does not wait for master thread termination >

[jira] [Closed] (APEXCORE-598) Embedded mode execution does not use APPLICATION_PATH for checkpointing

[ https://issues.apache.org/jira/browse/APEXCORE-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-598. -- Closing after 3.6.0 release > Embedded mode execution does not use APPLICATION_PATH for

[jira] [Closed] (APEXCORE-572) Remove dependency on hadoop-common test.jar

[ https://issues.apache.org/jira/browse/APEXCORE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-572. -- Closing after 3.6.0 release > Remove dependency on hadoop-common test.jar >

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

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-558. -- Closing after 3.6.0 release > Do not use yellow color to display command strings in help output

[jira] [Closed] (APEXCORE-610) Avoid multiple getBytes() calls in Tuple.writeString

[ https://issues.apache.org/jira/browse/APEXCORE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-610. -- Closing after 3.6.0 release > Avoid multiple getBytes() calls in Tuple.writeString >

[jira] [Closed] (APEXCORE-676) Show description for DefaultProperties only when user requests it

[ https://issues.apache.org/jira/browse/APEXCORE-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-676. -- Closing after 3.6.0 release > Show description for DefaultProperties only when user requests it

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

[ https://issues.apache.org/jira/browse/APEXCORE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-456. -- Closing after 3.6.0 release > Explicitly limit Server.Subscriber to one way communication >

[jira] [Closed] (APEXCORE-687) Update docs, change supported Hadoop version to 2.6

[ https://issues.apache.org/jira/browse/APEXCORE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-687. -- Closing after 3.6.0 release > Update docs, change supported Hadoop version to 2.6 >

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

[ https://issues.apache.org/jira/browse/APEXCORE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-695. -- Closing after 3.6.0 release > Remove unnecessary interface modifiers >

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

[ https://issues.apache.org/jira/browse/APEXCORE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-690. -- Closing after 3.6.0 release > Embedded app launcher does not apply HEARTBEAT_MONITORING setting

[jira] [Closed] (APEXCORE-604) Extend DAG API to allow accessing DAG objects.

[ https://issues.apache.org/jira/browse/APEXCORE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-604. -- Closing after 3.6.0 release > Extend DAG API to allow accessing DAG objects. >

[jira] [Closed] (APEXCORE-593) apex cli get-app-package-info could not retrieve properties defined in properties.xml

[ https://issues.apache.org/jira/browse/APEXCORE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-593. -- Closing after 3.6.0 release > apex cli get-app-package-info could not retrieve properties

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

[ https://issues.apache.org/jira/browse/APEXCORE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-471. -- Closing after 3.6.0 release > Requests for container allocation are not resubmitted >

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

[ https://issues.apache.org/jira/browse/APEXCORE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-691. -- Closing after 3.6.0 release > Use type inference for generic instance creation >

[jira] [Closed] (APEXCORE-634) Unifier attributes are not set for modules in DAG

[ https://issues.apache.org/jira/browse/APEXCORE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-634. -- Closing after 3.6.0 release > Unifier attributes are not set for modules in DAG >

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

[ https://issues.apache.org/jira/browse/APEXCORE-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-677. -- Closing after 3.6.0 release > Avoid starting StramLocalCluster in >

[jira] [Closed] (APEXCORE-611) Stram Event Log Levels

[ https://issues.apache.org/jira/browse/APEXCORE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-611. -- Closing after 3.6.0 release > Stram Event Log Levels > -- > >

[jira] [Closed] (APEXCORE-580) Interface for processing and emitting control tuples

[ https://issues.apache.org/jira/browse/APEXCORE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-580. -- Closing after 3.6.0 release > Interface for processing and emitting control tuples >

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

[ https://issues.apache.org/jira/browse/APEXCORE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-692. -- Closing after 3.6.0 release > Apex Dev Setup doc should reference download page >

[jira] [Closed] (APEXCORE-504) Possible race condition in StreamingContainerAgent.getStreamCodec()

[ https://issues.apache.org/jira/browse/APEXCORE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-504. -- Closing after 3.6.0 release > Possible race condition in

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

[ https://issues.apache.org/jira/browse/APEXCORE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-686. -- Closing after 3.6.0 release > AppPackage fails when .apa contains zero length stored entry >

[jira] [Closed] (APEXCORE-595) Master incorrectly updates committedWindowId when all partitions are terminated.

[ https://issues.apache.org/jira/browse/APEXCORE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-595. -- Closing after 3.6.0 release > Master incorrectly updates committedWindowId when all partitions

[jira] [Closed] (APEXCORE-581) Delivery of Custom Control Tuples

[ https://issues.apache.org/jira/browse/APEXCORE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-581. -- Closing after 3.6.0 release > Delivery of Custom Control Tuples >

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

[ https://issues.apache.org/jira/browse/APEXCORE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-709. -- Closing after 3.6.0 release > Refactor changes done through APEXCORE-575 >

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

[ https://issues.apache.org/jira/browse/APEXCORE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-649. -- Closing after 3.6.0 release > Infrastructure for user define stram event listeners. >

[jira] [Closed] (APEXCORE-522) Promote singleton usage pattern for String2String, Long2String and other StringCodecs

[ https://issues.apache.org/jira/browse/APEXCORE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-522. -- Closing after 3.6.0 release > Promote singleton usage pattern for String2String, Long2String and

[jira] [Closed] (APEXCORE-480) Change the container log name from dt.log to apex.log

[ https://issues.apache.org/jira/browse/APEXCORE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-480. -- Closing after 3.6.0 release > Change the container log name from dt.log to apex.log >

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

[ https://issues.apache.org/jira/browse/APEXCORE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-658. -- Closing after 3.6.0 release > Replace dt. prefix with apex. for configuration keys >

[jira] [Closed] (APEXCORE-648) Unnecessary byte array copy in DefaultStatefulStreamCodec.toDataStatePair()

[ https://issues.apache.org/jira/browse/APEXCORE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi closed APEXCORE-648. -- Closing after 3.6.0 release > Unnecessary byte array copy in

Re: [VOTE] Apache Apex Core Release 3.6.0 (RC1)

As a committer, I do not have write permissions to release svn repository. Need help from PMC member to update the release repository. Any volunteers?? Also one more clarification needed with respect to updating semantic versioning check. Does it needs to be done for both release-3.6.0 and master

Re: [VOTE] Apache Apex Core Release 3.6.0 (RC1)

The vote is concluded and passes. Thanks everyone for voting and verifying the release. binding +1 (4) Vlad Rozov Thomas Weise Amol Kekre Pramod Immaneni non-binding +1 (2) Bhupesh Chawda Chaitanya Chebolu No other votes. Will complete the release activities. Thanks, Tushar. On Thu, May