[VOTE] Apache Apex Core Release 3.5.0 (RC1)

Dear Community, Please vote on the following Apache Apex Core 3.5.0 release candidate. This is a source release with binary artifacts published to Maven. List of all issues fixed: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12335724=Text=12318823 User documentation:

[jira] [Reopened] (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 ] Thomas Weise reopened APEXCORE-456: --- > Explicitly limit Server.Subscriber to one way communication >

[jira] [Updated] (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 ] Thomas Weise updated APEXCORE-456: -- Fix Version/s: (was: 3.5.0) > Explicitly limit Server.Subscriber to one way communication

[jira] [Resolved] (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 ] Thomas Weise resolved APEXCORE-456. --- Resolution: Fixed Fix Version/s: 3.5.0 > Explicitly limit Server.Subscriber to one

[jira] [Updated] (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 ] Thomas Weise updated APEXCORE-456: -- Fix Version/s: (was: 3.5.0) > Explicitly limit Server.Subscriber to one way communication

Re: Malhar release 3.6

Thanks David. Anyone else wants to contribute something to the release notes? It is time to wrap it up. Thanks, Thomas On Tue, Dec 6, 2016 at 3:14 PM, David Yan wrote: > For the work in the Windowed Operator that is included in the 3.6 release: > > There is now an

[jira] [Resolved] (APEXMALHAR-2362) SpillableSetMulitmapImpl.removedSets keeps growing

[ https://issues.apache.org/jira/browse/APEXMALHAR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bright chen resolved APEXMALHAR-2362. - Resolution: Fixed > SpillableSetMulitmapImpl.removedSets keeps growing >

[jira] [Commented] (APEXMALHAR-2362) SpillableSetMulitmapImpl.removedSets keeps growing

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

[GitHub] apex-malhar pull request #519: APEXMALHAR-2362 #resolve clearing the removed...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/519 --- 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] (APEXCORE-558) Do not use yellow color to display command strings in help output

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726969#comment-15726969 ] Vlad Rozov commented on APEXCORE-558: - For the CLI help bold should be sufficient. > Do not use

[jira] [Commented] (APEXCORE-559) Support quit which should behave the same as "exit"

[ https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726935#comment-15726935 ] Vlad Rozov commented on APEXCORE-559: - I think it is not necessary to initialize ~/.dt/clirc with

[jira] [Closed] (APEXCORE-559) Support quit which should behave the same as "exit"

[ https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay M Pujare closed APEXCORE-559. Resolution: Won't Fix > Support quit which should behave the same as "exit" >

[jira] [Commented] (APEXCORE-559) Support quit which should behave the same as "exit"

[ https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726880#comment-15726880 ] Sanjay M Pujare commented on APEXCORE-559: -- I agree it is easier to do this in clirc. If there

[jira] [Commented] (APEXCORE-559) Support quit which should behave the same as "exit"

[ https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726860#comment-15726860 ] Vlad Rozov commented on APEXCORE-559: - As apex supports aliases, it is quite easy to add "quit" as

[jira] [Commented] (APEXCORE-559) Support quit which should behave the same as "exit"

[ https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726796#comment-15726796 ] Sanjay M Pujare commented on APEXCORE-559: -- Yes this is not the most critical or important

[jira] [Commented] (APEXCORE-559) Support quit which should behave the same as "exit"

[ https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726779#comment-15726779 ] David Yan commented on APEXCORE-559: I don't think this feature is warranted at all. However, if

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

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726769#comment-15726769 ] David Yan commented on APEXCORE-558: I still think we should not have any color at all since it's

com.fasterxml.jackson.core.JsonFactory.requiresPropertyOrdering()Z

Dear community, I am currently working on creation of LogParser. While writing unit tests for this parser I got following error : *java.lang.NoSuchMethodError: com.fasterxml.jackson.core.JsonFactory.requiresPropertyOrdering()Z* The same error I saw while running JsonParserTest as well. This