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 is
[
https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726769#comment-15726769
]
David Yan commented on APEXCORE-558:
I still think we should not have any color at a
[
https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726779#comment-15726779
]
David Yan commented on APEXCORE-559:
I don't think this feature is warranted at all.
[
https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726796#comment-15726796
]
Sanjay M Pujare commented on APEXCORE-559:
--
Yes this is not the most critical o
[
https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726860#comment-15726860
]
Vlad Rozov commented on APEXCORE-559:
-
As apex supports aliases, it is quite easy to
[
https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726880#comment-15726880
]
Sanjay M Pujare commented on APEXCORE-559:
--
I agree it is easier to do this in
[
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"
>
[
https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726935#comment-15726935
]
Vlad Rozov commented on APEXCORE-559:
-
I think it is not necessary to initialize ~/.
[
https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726969#comment-15726969
]
Vlad Rozov commented on APEXCORE-558:
-
For the CLI help bold should be sufficient.
For the work in the Windowed Operator that is included in the 3.6 release:
There is now an option to use spillable data structures for the state
storage of the Windowed Operator. This enables the Windowed Operator to
store large states and perform efficient checkpointing.
We also did benchmarking
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 is
[
https://issues.apache.org/jira/browse/APEXMALHAR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727102#comment-15727102
]
ASF GitHub Bot commented on APEXMALHAR-2362:
Github user asfgit closed th
[
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
>
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 option to use spillable data
[
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
[
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 wa
[
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
>
[
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
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&styleName=Text&projectId=12318823
User docum
19 matches
Mail list logo