[jira] [Commented] (APEXMALHAR-2264) Add documentation for jmsInputOperator

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

[GitHub] apex-malhar pull request #425: APEXMALHAR-2264 add jms input operator doc to...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/425 --- 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-528) Output Ports Not Optional by Default During Validation

[ https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514909#comment-15514909 ] Alex McCullough commented on APEXCORE-528: -- Yep, that works. My thought was that if the default

[jira] [Commented] (APEXMALHAR-1818) Integrate Calcite to support SQL

[ https://issues.apache.org/jira/browse/APEXMALHAR-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514919#comment-15514919 ] Julian Hyde commented on APEXMALHAR-1818: - [~chinmay], I watched the demo video and took a

[jira] [Created] (APEXMALHAR-2265) Add entries to mkdocs.yml for recently added operator docs

Munagala V. Ramanath created APEXMALHAR-2265: Summary: Add entries to mkdocs.yml for recently added operator docs Key: APEXMALHAR-2265 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2265

[GitHub] apex-malhar pull request #423: APEXMALHAR-2241 - The metadata kafka consumer...

GitHub user venkateshkottapalli opened a pull request: https://github.com/apache/apex-malhar/pull/423 APEXMALHAR-2241 - The metadata kafka consumer should also pickup the properties setting on the kafka input operator Fixes two issues - * metadata kafka consumer not picking up

[jira] [Commented] (APEXMALHAR-2241) The metadata kafka consumer should also pickup the properties setting on the kafka input operator.

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

[jira] [Resolved] (APEXMALHAR-2264) Add documentation for jmsInputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Munagala V. Ramanath resolved APEXMALHAR-2264. -- Resolution: Fixed Fix Version/s: 3.6.0 Merged > Add

[jira] [Created] (APEXMALHAR-2264) Add documentation for jmsInputOperator

Sanjay M Pujare created APEXMALHAR-2264: --- Summary: Add documentation for jmsInputOperator Key: APEXMALHAR-2264 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2264 Project: Apache Apex

[jira] [Commented] (APEXMALHAR-2130) Scalable windowed storage

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

[GitHub] apex-malhar pull request #424: APEXMALHAR-2130 Spillable implementation for ...

GitHub user davidyan74 opened a pull request: https://github.com/apache/apex-malhar/pull/424 APEXMALHAR-2130 Spillable implementation for WindowedOperator @tweise @brightchen @siyuanh Please review and merge You can merge this pull request into a Git repository by running: $

[jira] [Commented] (APEXMALHAR-2130) Scalable windowed storage

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

[GitHub] apex-malhar pull request #345: APEXMALHAR-2130 REVIEW ONLY (WindowedOperator...

Github user davidyan74 closed the pull request at: https://github.com/apache/apex-malhar/pull/345 --- 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

[jira] [Updated] (APEXCORE-538) Log raw data when RPC message fails to de-serialize

[ https://issues.apache.org/jira/browse/APEXCORE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXCORE-538: -- Fix Version/s: (was: 3.4.1) (was: 3.3.1) > Log raw data when RPC

[jira] [Resolved] (APEXCORE-538) Log raw data when RPC message fails to de-serialize

[ https://issues.apache.org/jira/browse/APEXCORE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-538. --- Resolution: Fixed > Log raw data when RPC message fails to de-serialize >

[jira] [Commented] (APEXMALHAR-2265) Add entries to mkdocs.yml for recently added operator docs

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

Re: Trying to acces live data

Hi Hitesh, Can you collect all logs including app master logs and send it? Run command "yarn logs -applicationId " on cluster to get logs for an application. Also please collect stderr output logs of appMaster. You can find them under "/logs/userlogs///" -Priyanka On Fri, Sep 23, 2016 at 10:55

[jira] [Commented] (APEXMALHAR-2265) Add entries to mkdocs.yml for recently added operator docs

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

[GitHub] apex-core pull request #396: APEXCORE-538 - Log raw data when RPC message fa...

Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/396 --- 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

[jira] [Commented] (APEXCORE-538) Log raw data when RPC message fails to de-serialize

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

[GitHub] apex-malhar pull request #426: APEXMALHAR-2265 Added entries in mkdocs.yml f...

GitHub user amberarrow opened a pull request: https://github.com/apache/apex-malhar/pull/426 APEXMALHAR-2265 Added entries in mkdocs.yml for 2 newly added docs @sashadt Please take a look You can merge this pull request into a Git repository by running: $ git pull

Trying to acces live data

Hi team, Trying to access live data from couchbase using input Operators. It is running fine on my local. The tuples are emitting as Pojo through the output port of inputOperator. But when I upload the .apa file on data torrent, it gets launched but soon it goes into Failed State just after been

[jira] [Resolved] (APEXMALHAR-2265) Add entries to mkdocs.yml for recently added operator docs

[ https://issues.apache.org/jira/browse/APEXMALHAR-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2265. -- Resolution: Fixed Fix Version/s: 3.6.0 > Add entries to mkdocs.yml for

[GitHub] apex-malhar pull request #426: APEXMALHAR-2265 Added entries in mkdocs.yml f...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/426 --- 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

Re: PrintWriter for LogicalPlan

There is a LogicalPlanSerializer in apex engine, which will generate json equivalent of DAG, which can be printed easily. But for verification check if right components are added in DAG by examining dag structure than printing it. - Tushar. On Thu, Sep 22, 2016 at 11:39 AM, Chinmay Kolhatkar

[jira] [Updated] (APEXMALHAR-2255) Use latest couchbase client library

[ https://issues.apache.org/jira/browse/APEXMALHAR-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXMALHAR-2255: Summary: Use latest couchbase client library (was: Use latest java sdk for

Re: PrintWriter for LogicalPlan

Hi Chinmay, take a look at following gist for example. https://gist.github.com/anonymous/8df8e05ffc16e620bbc030e1034da3c4 - Tushar. On Thu, Sep 22, 2016 at 12:05 PM, Chinmay Kolhatkar wrote: > Hi Tushar, > > Thanks for the information. Can you please provide me

[jira] [Commented] (APEXMALHAR-2255) Use latest java sdk for couchbase

[ https://issues.apache.org/jira/browse/APEXMALHAR-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512385#comment-15512385 ] Priyanka Gugale commented on APEXMALHAR-2255: - The request is to upgrade *couchbase java

[jira] [Commented] (APEXCORE-528) Output Ports Not Optional by Default During Validation

[ https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513421#comment-15513421 ] Alex McCullough commented on APEXCORE-528: -- Hey Deepak, I am working on this. I did want to

[jira] [Commented] (APEXCORE-528) Output Ports Not Optional by Default During Validation

[ https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513460#comment-15513460 ] Thomas Weise commented on APEXCORE-528: --- IMO output ports that don't have an annotation should be

Re: Python support

I would like to help in contributing to this feature. On Wed, Sep 21, 2016 at 12:26 AM, Sasha Parfenov wrote: > +1 on both executing Python code in an operator and high level API for > constructing Pipelines in Python. > > There is a large user base of engineers and data

PrintWriter for LogicalPlan

Hi All, For testing of calcite generated DAG, I want to verify whether the correct DAG is created with right operators and streams and whether properties are set properly. Is there any PrintWriter for the LogicalPlan object printing components of DAG? If not, I am planning to write one for

Re: PrintWriter for LogicalPlan

Thanks tushar. I got it working in similar ways: 1. For DAG as JSON String: Map stringObjectMap = LogicalPlanSerializer.convertToMap(dag, true); ObjectMapper mapper = new ObjectMapper(); mapper.enable(SerializationFeature.INDENT_OUTPUT); String s =

Re: PrintWriter for LogicalPlan

Hi Tushar, Thanks for the information. Can you please provide me pointers on how to use it? I can always examine the LogicalPlan structure but for a test case, I think its an overkill, instead if I have a utility which can print LogicalPlan (similar to LogicalPlanSerializer), then its just the

[jira] [Assigned] (APEXCORE-310) apex cli - support to kill the app by appname

[ https://issues.apache.org/jira/browse/APEXCORE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Narkhede reassigned APEXCORE-310: Assignee: Deepak Narkhede > apex cli - support to kill the app by appname >

[jira] [Commented] (APEXCORE-539) DefaultAttributeMap is not thread safe

[ https://issues.apache.org/jira/browse/APEXCORE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513980#comment-15513980 ] Thomas Weise commented on APEXCORE-539: --- It wasn't the original intention to modify the map once

[jira] [Commented] (APEXCORE-539) DefaultAttributeMap is not thread safe

[ https://issues.apache.org/jira/browse/APEXCORE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514021#comment-15514021 ] Vlad Rozov commented on APEXCORE-539: - I see the following exception after I changed

[jira] [Created] (APEXCORE-539) DefaultAttributeMap is not thread safe

Vlad Rozov created APEXCORE-539: --- Summary: DefaultAttributeMap is not thread safe Key: APEXCORE-539 URL: https://issues.apache.org/jira/browse/APEXCORE-539 Project: Apache Apex Core Issue

[jira] [Commented] (APEXCORE-532) New dynamically added operator does not start with correct windowId.

[ https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514071#comment-15514071 ] Pramod Immaneni commented on APEXCORE-532: -- [~tushargosavi] checking why this is broken when it

[jira] [Commented] (APEXMALHAR-2190) Use reusable buffer to serial spillable data structure

[ https://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513930#comment-15513930 ] ASF GitHub Bot commented on APEXMALHAR-2190: GitHub user brightchen reopened a pull

[jira] [Commented] (APEXMALHAR-2190) Use reusable buffer to serial spillable data structure

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

[GitHub] apex-malhar pull request #404: APEXMALHAR-2190 #resolve #comment Use reusabl...

GitHub user brightchen reopened a pull request: https://github.com/apache/apex-malhar/pull/404 APEXMALHAR-2190 #resolve #comment Use reusable buffer to serial spill… …able data structure You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (APEXCORE-532) New dynamically added operator does not start with correct windowId.

[ https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514117#comment-15514117 ] Tushar Gosavi commented on APEXCORE-532: If newly added operator is attached to some operator

[jira] [Updated] (APEXMALHAR-2262) lock on AbstractManagedStateImpl.getValueFromBucketSync is too wide

[ https://issues.apache.org/jira/browse/APEXMALHAR-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bright chen updated APEXMALHAR-2262: Summary: lock on AbstractManagedStateImpl.getValueFromBucketSync is too wide (was:

[jira] [Commented] (APEXCORE-528) Output Ports Not Optional by Default During Validation

[ https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512979#comment-15512979 ] Deepak Narkhede commented on APEXCORE-528: -- Hi Alex, Are you currently working on it. If not,

[jira] [Updated] (APEXMALHAR-2261) Python binding for high level API

[ https://issues.apache.org/jira/browse/APEXMALHAR-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2261: - Labels: roadmap (was: ) > Python binding for high level API >

[jira] [Commented] (APEXCORE-528) Output Ports Not Optional by Default During Validation

[ https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513507#comment-15513507 ] Alex McCullough commented on APEXCORE-528: -- Because when no annotations are added the

[jira] [Created] (APEXCORE-538) Log raw data when RPC message fails to de-serialize

Vlad Rozov created APEXCORE-538: --- Summary: Log raw data when RPC message fails to de-serialize Key: APEXCORE-538 URL: https://issues.apache.org/jira/browse/APEXCORE-538 Project: Apache Apex Core

Re: Python support

I created the following JIRAs: https://issues.apache.org/jira/browse/APEXMALHAR-2260 https://issues.apache.org/jira/browse/APEXMALHAR-2261 On Wed, Sep 21, 2016 at 11:10 PM, Chinmay Kolhatkar wrote: > I would like to help in contributing to this feature. > > On Wed,

[jira] [Commented] (APEXCORE-528) Output Ports Not Optional by Default During Validation

[ https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513525#comment-15513525 ] Alex McCullough commented on APEXCORE-528: --

[jira] [Commented] (APEXCORE-528) Output Ports Not Optional by Default During Validation

[ https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513515#comment-15513515 ] Thomas Weise commented on APEXCORE-528: --- Can you point me to the exact place in the code you are

[jira] [Created] (APEXMALHAR-2263) Offsets in AbstractFileInputOperator should be long rather than int

Munagala V. Ramanath created APEXMALHAR-2263: Summary: Offsets in AbstractFileInputOperator should be long rather than int Key: APEXMALHAR-2263 URL:

Re: Trying to access live data from couchbase

Check Application master logs and stderr output. Thank you, Vlad On 9/22/16 04:09, Hitesh Goyal wrote: Hi team, Trying to access live data from couchbase using input Operators. It is running fine on my local. The tuples are emitting as Pojo through the output port of inputOperator. But

[GitHub] apex-malhar pull request #399: REVIEW ONLY: exposing seeking and iterating o...

Github user davidyan74 closed the pull request at: https://github.com/apache/apex-malhar/pull/399 --- 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

[jira] [Commented] (APEXMALHAR-2192) Implement SpillableByteArrayListMultimapImpl.removeAll(Object key)

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

[jira] [Closed] (APEXMALHAR-2191) Implement a way to get all keys with or without prefix from SpillableByteMapImpl

[ https://issues.apache.org/jira/browse/APEXMALHAR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan closed APEXMALHAR-2191. - > Implement a way to get all keys with or without prefix from > SpillableByteMapImpl >

[jira] [Updated] (APEXMALHAR-2191) Implement a way to get all keys with or without prefix from SpillableByteMapImpl

[ https://issues.apache.org/jira/browse/APEXMALHAR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2191: -- Assignee: (was: David Yan) > Implement a way to get all keys with or without prefix

[jira] [Updated] (APEXMALHAR-2249) Create SpillableSet and SpillableSetMultimap interfaces and implementation

[ https://issues.apache.org/jira/browse/APEXMALHAR-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2249: -- Assignee: (was: David Yan) > Create SpillableSet and SpillableSetMultimap interfaces

[jira] [Closed] (APEXMALHAR-2188) Implement SpillableByteArrayListMultimapImpl.containsEntry

[ https://issues.apache.org/jira/browse/APEXMALHAR-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan closed APEXMALHAR-2188. - > Implement SpillableByteArrayListMultimapImpl.containsEntry >

[GitHub] apex-malhar pull request #377: *Review Only* APEXMALHAR-2192 Added some spil...

Github user davidyan74 closed the pull request at: https://github.com/apache/apex-malhar/pull/377 --- 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

[jira] [Closed] (APEXMALHAR-2192) Implement SpillableByteArrayListMultimapImpl.removeAll(Object key)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan closed APEXMALHAR-2192. - > Implement SpillableByteArrayListMultimapImpl.removeAll(Object key) >

[jira] [Closed] (APEXMALHAR-2189) Implement SpillableArrayListImpl.iterator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan closed APEXMALHAR-2189. - > Implement SpillableArrayListImpl.iterator > - > >

[jira] [Closed] (APEXMALHAR-2231) Implement a Spillable map that takes two keys

[ https://issues.apache.org/jira/browse/APEXMALHAR-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan closed APEXMALHAR-2231. - Assignee: (was: David Yan) > Implement a Spillable map that takes two keys >

[jira] [Closed] (APEXMALHAR-2193) Implement SpillableByteArrayListMultimapImpl.remove(@Nullable Object key, @Nullable Object value)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan closed APEXMALHAR-2193. - > Implement SpillableByteArrayListMultimapImpl.remove(@Nullable Object key, > @Nullable Object

[jira] [Created] (APEXMALHAR-2261) Python binding for high level API

Thomas Weise created APEXMALHAR-2261: Summary: Python binding for high level API Key: APEXMALHAR-2261 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2261 Project: Apache Apex Malhar

[jira] [Updated] (APEXMALHAR-2130) Scalable windowed storage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2130: - Summary: Scalable windowed storage (was: implement scalable windowed storage) >

[jira] [Created] (APEXMALHAR-2260) Python execution for operator logic

Thomas Weise created APEXMALHAR-2260: Summary: Python execution for operator logic Key: APEXMALHAR-2260 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2260 Project: Apache Apex Malhar

[GitHub] apex-core pull request #396: APEXCORE-538 - Log raw data when RPC message fa...

GitHub user vrozov opened a pull request: https://github.com/apache/apex-core/pull/396 APEXCORE-538 - Log raw data when RPC message fails to de-serialize @tweise Please review and cherry-pick. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (APEXMALHAR-2130) implement scalable windowed storage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2130: - Labels: roadmap (was: ) > implement scalable windowed storage >

[jira] [Commented] (APEXMALHAR-2244) Optimize WindowedStorage and Spillable data structures for time series

[ https://issues.apache.org/jira/browse/APEXMALHAR-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513770#comment-15513770 ] Siyuan Hua commented on APEXMALHAR-2244: Each spillable DS implementation use a

[jira] [Commented] (APEXCORE-538) Log raw data when RPC message fails to de-serialize

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

[jira] [Commented] (APEXMALHAR-2248) Create SpillableSet and SpillableSetMultimap interfaces and implementation

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

[GitHub] apex-malhar pull request #408: APEXMALHAR-2248 Added SpillableSet and Spilla...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/408 --- 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] [Updated] (APEXMALHAR-2248) Create SpillableSet and SpillableSetMultimap interfaces and implementation

[ https://issues.apache.org/jira/browse/APEXMALHAR-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2248: --- Fix Version/s: 3.6.0 > Create SpillableSet and SpillableSetMultimap interfaces and

[jira] [Resolved] (APEXMALHAR-2248) Create SpillableSet and SpillableSetMultimap interfaces and implementation

[ https://issues.apache.org/jira/browse/APEXMALHAR-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua resolved APEXMALHAR-2248. Resolution: Fixed > Create SpillableSet and SpillableSetMultimap interfaces and

Re: excluding hadoop dependencies from application package

Definitely worth adding. Ram On Wed, Sep 21, 2016 at 1:20 PM, Pramod Immaneni wrote: > Candidate to be added here? > > https://apex.apache.org/docs/apex/development_best_practices/ > > On Wed, Sep 21, 2016 at 12:24 PM, Munagala Ramanath > wrote: >

Trying to access live data from couchbase

Hi team, Trying to access live data from couchbase using input Operators. It is running fine on my local. The tuples are emitting as Pojo through the output port of inputOperator. But when I upload the .apa file on data torrent, it gets launched but soon it goes into Failed State just after