[jira] [Updated] (APEXMALHAR-2139) UniqueCounter changes

[Thomas Weise (JIRA)]

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

Thomas Weise updated APEXMALHAR-2139:
-
Assignee: Aayushi Acharya

> UniqueCounter changes
> -
>
> Key: APEXMALHAR-2139
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2139
> Project: Apache Apex Malhar
>  Issue Type: Improvement
>Reporter: Aayushi Acharya
>Assignee: Aayushi Acharya
> Fix For: 3.5.0
>
>
> 1.Update the unique counter operator from Malhar 
> https://github.com/apache/apex-malhar/blob/master/library/src/main/java/com/datatorrent/lib/algo/UniqueCounter.java
>  to emit one tuple at a time vs dumping a map.
> 2.Emit only the keys for which values changed or were added in a given window.
> 3.Add test cases for 1 and 2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Malhar 3.5.0 release

[Yogi Devendra]

https://github.com/apache/apex-malhar/pull/372 is open for APEXMALHAR-2195.

I have incorporated the review comments from @gauravgopi123, @tweise
I have updated fix version to 3.5.0 to reflect this ticket in the query.

Can someone please review and merge this for 3.5.0?

~ Yogi

On 25 August 2016 at 21:41, Chaitanya Chebolu 
wrote:

> Hi Thomas,
>
>I will fix APEXMALHAR-2134.
>
> Regards,
> Chaitanya
>
> On Thu, Aug 25, 2016 at 9:13 PM, Thomas Weise 
> wrote:
>
> > We are almost ready to get the RC out.
> >
> > Can someone fix APEXMALHAR-2134 for the release?
> >
> >
> > On Wed, Aug 17, 2016 at 12:56 PM, Thomas Weise 
> > wrote:
> >
> > > Friendly reminder.. There are still a few unresolved tickets for 3.5:
> > >
> > > https://issues.apache.org/jira/issues/?jql=fixVersion%
> > > 20%3D%203.5.0%20AND%20project%20%3D%20APEXMALHAR%20AND%
> > 20resolution%20%3D%
> > > 20Unresolved%20ORDER%20BY%20priority%20DESC
> > >
> > > Please remove the fix version unless you expect to complete the work in
> > > the next few days.
> > >
> > > And we need to complete the PR for high level API:
> > >
> > > https://issues.apache.org/jira/browse/APEXMALHAR-2142
> > >
> > > Thanks,
> > > Thomas
> > >
> > >
> > > On Fri, Aug 5, 2016 at 2:12 AM, Chaitanya Chebolu <
> > > chaita...@datatorrent.com> wrote:
> > >
> > >> APEXMALHAR-2100. PR is open: https://github.com/apache/apex
> > >> -malhar/pull/330
> > >>
> > >> Regards,
> > >> Chaitanya
> > >>
> > >> On Fri, Aug 5, 2016 at 1:10 PM, Priyanka Gugale <
> > priya...@datatorrent.com
> > >> >
> > >> wrote:
> > >>
> > >> > APEXMALHAR-2171
> > >> > PR is open: https://github.com/apache/apex-malhar/pull/358
> > >> >
> > >> > -Priyanka
> > >> >
> > >> > On Fri, Aug 5, 2016 at 12:32 PM, Yogi Devendra <
> > >> > devendra.vyavah...@gmail.com
> > >> > > wrote:
> > >> >
> > >> > > Fix for APEXMALHAR-2176
> > >> > > PR open: https://github.com/apache/apex-malhar/pull/361
> > >> > >
> > >> > > ~ Yogi
> > >> > >
> > >> > > On 1 August 2016 at 11:59, Chinmay Kolhatkar <
> > chin...@datatorrent.com
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > > > APEXMALHAR-2128 is already done. Somehow the status did not go
> to
> > >> > > resolved.
> > >> > > > Changed it now.
> > >> > > >
> > >> > > > On Fri, Jul 29, 2016 at 1:53 PM, Yogi Devendra <
> > >> > > > devendra.vyavah...@gmail.com
> > >> > > > > wrote:
> > >> > > >
> > >> > > > > APEXMALHAR-2116
> > >> > > > > https://github.com/apache/apex-malhar/pull/326
> > >> > > > >
> > >> > > > > @Ram
> > >> > > > > Your review comments are incorporated. Could you please have a
> > >> look
> > >> > at
> > >> > > > > this?
> > >> > > > >
> > >> > > > > ~ Yogi
> > >> > > > >
> > >> > > > > On 29 July 2016 at 13:49, Thomas Weise <
> tho...@datatorrent.com>
> > >> > wrote:
> > >> > > > >
> > >> > > > > > Hi,
> > >> > > > > >
> > >> > > > > > I would suggest to target the 3.5.0 release with an RC out
> > >> perhaps
> > >> > 2
> > >> > > > > weeks
> > >> > > > > > from now, as there is a good amount of work that we should
> > make
> > >> > > > available
> > >> > > > > > to the users:
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > https://issues.apache.org/jira/browse/APEXMALHAR/
> > >> > > > fixforversion/12335815/?selectedTab=com.atlassian.
> > >> > > > jira.jira-projects-plugin:version-issues-panel
> > >> > > > > >
> > >> > > > > > I also think that the following should go in:
> > >> > > > > >
> > >> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2128
> > >> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2142
> > >> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2063
> > >> > > > > >
> > >> > > > > > Any other candidates?
> > >> > > > > >
> > >> > > > > > There are quite a few other PRs open:
> > >> > > > > >
> > >> > > > > > https://github.com/apache/apex-malhar/pulls
> > >> > > > > >
> > >> > > > > > Would be good to complete some more reviews for this
> release.
> > >> > > > > >
> > >> > > > > > Thanks,
> > >> > > > > > Thomas
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>

[jira] [Updated] (APEXMALHAR-2195) LineReaderContext gives incorrect results for files not ending with the newline

[Yogi Devendra (JIRA)]

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

Yogi Devendra updated APEXMALHAR-2195:
--
Fix Version/s: 3.5.0

> LineReaderContext gives incorrect results for files not ending with the 
> newline
> ---
>
> Key: APEXMALHAR-2195
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2195
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Yogi Devendra
>Assignee: Yogi Devendra
>Priority: Minor
> Fix For: 3.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (APEXMALHAR-2204) Implement managed state delete

[Thomas Weise (JIRA)]

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

Thomas Weise updated APEXMALHAR-2204:
-
Description: We need a delete operation that actually removes the entry. 
Currently user needs to use a special "DELETED" value as workaround and space 
won't be reclaimed.

> Implement managed state delete
> --
>
> Key: APEXMALHAR-2204
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2204
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Siyuan Hua
>Priority: Critical
>
> We need a delete operation that actually removes the entry. Currently user 
> needs to use a special "DELETED" value as workaround and space won't be 
> reclaimed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2200) Enable checkstyle for demos

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on APEXMALHAR-2200:


GitHub user ShunxinLu opened a pull request:

https://github.com/apache/apex-malhar/pull/382

APEXMALHAR-2200 Enabled checkstyle for demos. Fixed checkstyle errors.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ShunxinLu/apex-malhar APEXMALHAR-2200

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/382.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #382


commit fa0c4952d719af1be67c3f28c65e7c5b28ef45ed
Author: Shunxin 
Date:   2016-08-26T01:01:02Z

APEXMALHAR-2200 Enabled checkstyle for demos. Fixed checkstyle errors.




> Enable checkstyle for demos
> ---
>
> Key: APEXMALHAR-2200
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2200
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Shunxin Lu
>
> It is turned off in the parent pom, which will cause new modules to be under 
> the radar. Should be enabled and then turned off for legacy modules that 
> cannot be fixed easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] apex-malhar pull request #382: APEXMALHAR-2200 Enabled checkstyle for demos....

[ShunxinLu]

GitHub user ShunxinLu opened a pull request:

https://github.com/apache/apex-malhar/pull/382

APEXMALHAR-2200 Enabled checkstyle for demos. Fixed checkstyle errors.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ShunxinLu/apex-malhar APEXMALHAR-2200

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/382.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #382


commit fa0c4952d719af1be67c3f28c65e7c5b28ef45ed
Author: Shunxin 
Date:   2016-08-26T01:01:02Z

APEXMALHAR-2200 Enabled checkstyle for demos. Fixed checkstyle errors.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[David Yan (JIRA)]

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

David Yan updated APEXMALHAR-2191:
--
Description: 
WindowedKeyedStorage is basically a Map>, and we need the 
capability of getting all K's given a window, and getting V given a window and 
K.

Currently, the spillable implementation of WindowedKeyedStorage uses two 
spillable data structures -- SpillableByteMapImpl, V> and 
SpillableArrayListMultimapImpl.  This will not work because we need 
to be able to remove a key from a window, which SpillableArrayList does not 
support, and having two separate spillable data structures if it can be 
achieved by just one should be avoided in general. 

We will implement the solution that supports prefix scanning (given a window, 
return all keys), which requires the keys to be stored in order in managed 
state.

Traversing all keys in the spillable map is needed by WindowStateMap. The 
WindowedOperator needs a way to traverse all windows in its state when firing a 
trigger. However, this is less urgent since the Window meta info is small and 
should fit in memory even with millions of windows. This is more for the 
checkpointing efficiency.



  was:This is needed by the spillable implementation of WindowStateMap. The 
WindowedOperator needs a way to traverse all windows in its state.


> Implement a way to get all keys with or without prefix from 
> SpillableByteMapImpl
> 
>
> Key: APEXMALHAR-2191
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2191
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>Assignee: David Yan
>Priority: Critical
>
> WindowedKeyedStorage is basically a Map>, and we need the 
> capability of getting all K's given a window, and getting V given a window 
> and K.
> Currently, the spillable implementation of WindowedKeyedStorage uses two 
> spillable data structures -- SpillableByteMapImpl, V> and 
> SpillableArrayListMultimapImpl.  This will not work because we 
> need to be able to remove a key from a window, which SpillableArrayList does 
> not support, and having two separate spillable data structures if it can be 
> achieved by just one should be avoided in general. 
> We will implement the solution that supports prefix scanning (given a window, 
> return all keys), which requires the keys to be stored in order in managed 
> state.
> Traversing all keys in the spillable map is needed by WindowStateMap. The 
> WindowedOperator needs a way to traverse all windows in its state when firing 
> a trigger. However, this is less urgent since the Window meta info is small 
> and should fit in memory even with millions of windows. This is more for the 
> checkpointing efficiency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[David Yan (JIRA)]

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

David Yan updated APEXMALHAR-2191:
--
Summary: Implement a way to get all keys with or without prefix from 
SpillableByteMapImpl  (was: Implement a way to get all keys from 
SpillableByteMapImpl)

> Implement a way to get all keys with or without prefix from 
> SpillableByteMapImpl
> 
>
> Key: APEXMALHAR-2191
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2191
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>Assignee: David Yan
>Priority: Critical
>
> This is needed by the spillable implementation of WindowStateMap. The 
> WindowedOperator needs a way to traverse all windows in its state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[David Yan (JIRA)]

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

David Yan updated APEXMALHAR-2191:
--
Priority: Critical  (was: Major)

> Implement a way to get all keys from SpillableByteMapImpl
> -
>
> Key: APEXMALHAR-2191
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2191
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>Assignee: David Yan
>Priority: Critical
>
> This is needed by the spillable implementation of WindowStateMap. The 
> WindowedOperator needs a way to traverse all windows in its state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (APEXMALHAR-2202) Move accumulations to correct package

[Thomas Weise (JIRA)]

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

Thomas Weise resolved APEXMALHAR-2202.
--
   Resolution: Fixed
Fix Version/s: 3.5.0

> Move accumulations to correct package
> -
>
> Key: APEXMALHAR-2202
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2202
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Shunxin Lu
> Fix For: 3.5.0
>
>
> They are currently under org.apache.apex.malhar.lib.window.impl.accumulation 
> but these are classes that the user would use directly. The better place 
> might be org.apache.apex.malhar.lib.window.accumulation 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (APEXMALHAR-2204) Implement managed state delete

[Thomas Weise (JIRA)]

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

Thomas Weise updated APEXMALHAR-2204:
-
Priority: Critical  (was: Major)

> Implement managed state delete
> --
>
> Key: APEXMALHAR-2204
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2204
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Siyuan Hua
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (APEXMALHAR-2204) Implement managed state delete

[Thomas Weise (JIRA)]

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

Thomas Weise updated APEXMALHAR-2204:
-
Assignee: Siyuan Hua  (was: Thomas Weise)

> Implement managed state delete
> --
>
> Key: APEXMALHAR-2204
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2204
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Siyuan Hua
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (APEXMALHAR-2204) Implement managed state delete

[Thomas Weise (JIRA)]

Thomas Weise created APEXMALHAR-2204:


 Summary: Implement managed state delete
 Key: APEXMALHAR-2204
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2204
 Project: Apache Apex Malhar
  Issue Type: Task
Reporter: Thomas Weise
Assignee: Thomas Weise






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Thomas Weise (JIRA)]

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

Thomas Weise updated APEXMALHAR-2193:
-
Assignee: (was: David Yan)

> Implement SpillableByteArrayListMultimapImpl.remove(@Nullable Object key, 
> @Nullable Object value)
> -
>
> Key: APEXMALHAR-2193
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2193
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>
> This is needed by SpillableSessionWindowedStorage. It needs a way to remove 
> the session window given the key in its internal keyToWindowsMap



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Thomas Weise (JIRA)]

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

Thomas Weise updated APEXMALHAR-2188:
-
Assignee: (was: David Yan)

> Implement SpillableByteArrayListMultimapImpl.containsEntry
> --
>
> Key: APEXMALHAR-2188
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2188
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>
> This method is needed by SpillableWindowedKeyedStorage.put(). It needs to 
> find out whether the key already exists in the window before pushing to the 
> Spillable ArrayList. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Thomas Weise (JIRA)]

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

Thomas Weise commented on APEXMALHAR-2189:
--

If we support key prefix scan in spillable map, then we will not need this for 
window state management. 

> Implement SpillableArrayListImpl.iterator
> -
>
> Key: APEXMALHAR-2189
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2189
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>
> This is needed by the spiillable storage implementation of WindowedOperator 
> so that it can iterate through all the keys in the window to determine 
> whether or not to fire a trigger.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Thomas Weise (JIRA)]

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

Thomas Weise updated APEXMALHAR-2189:
-
Assignee: (was: David Yan)

> Implement SpillableArrayListImpl.iterator
> -
>
> Key: APEXMALHAR-2189
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2189
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>
> This is needed by the spiillable storage implementation of WindowedOperator 
> so that it can iterate through all the keys in the window to determine 
> whether or not to fire a trigger.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2191) Implement a way to get all keys from SpillableByteMapImpl

[Thomas Weise (JIRA)]

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

Thomas Weise commented on APEXMALHAR-2191:
--

We need ability to iterate over keys with or without prefix. If the underlying 
storage orders keys, prefix scan is cheap.

> Implement a way to get all keys from SpillableByteMapImpl
> -
>
> Key: APEXMALHAR-2191
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2191
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>Assignee: David Yan
>
> This is needed by the spillable implementation of WindowStateMap. The 
> WindowedOperator needs a way to traverse all windows in its state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Thomas Weise (JIRA)]

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

Thomas Weise commented on APEXMALHAR-2193:
--

@timothyfarkas can you please comment on this issue? Removing entries from 
ArrayList is expensive, should we use a different data structure?

> Implement SpillableByteArrayListMultimapImpl.remove(@Nullable Object key, 
> @Nullable Object value)
> -
>
> Key: APEXMALHAR-2193
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2193
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: David Yan
>Assignee: David Yan
>
> This is needed by SpillableSessionWindowedStorage. It needs a way to remove 
> the session window given the key in its internal keyToWindowsMap



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (APEXMALHAR-2201) Suppress console output in Stream API tests

[Shunxin Lu (JIRA)]

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

Shunxin Lu reassigned APEXMALHAR-2201:
--

Assignee: Shunxin Lu

> Suppress console output in Stream API tests
> ---
>
> Key: APEXMALHAR-2201
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2201
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Shunxin Lu
>
> There is quite a bit of console output in the CI. It would be nice to 
> suppress that when running as unit test, we are not interested what gets 
> printed to the console but what the test asserts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (APEXMALHAR-2200) Enable checkstyle for demos

[Shunxin Lu (JIRA)]

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

Shunxin Lu reassigned APEXMALHAR-2200:
--

Assignee: Shunxin Lu

> Enable checkstyle for demos
> ---
>
> Key: APEXMALHAR-2200
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2200
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Shunxin Lu
>
> It is turned off in the parent pom, which will cause new modules to be under 
> the radar. Should be enabled and then turned off for legacy modules that 
> cannot be fixed easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2202) Move accumulations to correct package

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on APEXMALHAR-2202:


GitHub user ShunxinLu opened a pull request:

https://github.com/apache/apex-malhar/pull/381

APEXMALHAR-2202 Moved accumulations to org.apache.apex.malhar.lib.win…

…dow.accumulation.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ShunxinLu/apex-malhar APEXMALHAR-2202

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/381.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #381


commit 2b2d5bca91b23569e04cbc51a541126588eaab44
Author: Shunxin 
Date:   2016-08-25T20:37:46Z

APEXMALHAR-2202 Moved accumulations to 
org.apache.apex.malhar.lib.window.accumulation.




> Move accumulations to correct package
> -
>
> Key: APEXMALHAR-2202
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2202
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Shunxin Lu
>
> They are currently under org.apache.apex.malhar.lib.window.impl.accumulation 
> but these are classes that the user would use directly. The better place 
> might be org.apache.apex.malhar.lib.window.accumulation 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] apex-malhar pull request #380: APEXMALHAR-2199 Added the support chroot zook...

[chaithu14]

GitHub user chaithu14 opened a pull request:

https://github.com/apache/apex-malhar/pull/380

APEXMALHAR-2199 Added the support chroot zookeeper path in Kafka Input 
Operator



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chaithu14/incubator-apex-malhar 
APEXMALHAR-2199-zkPath

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/380.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #380


commit 82a6acbbd4c46e3e940d25366a2ca84c7dea4b8e
Author: chaitanya 
Date:   2016-08-25T18:58:31Z

APEXMALHAR-2199 Added the support chroot zookeeper path in Kafka Input 
Operator




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (APEXCORE-169) instantiating DTLoggerFactory during test causes incorrect logging behavior

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on APEXCORE-169:
-

GitHub user vrozov opened a pull request:

https://github.com/apache/apex-core/pull/375

APEXCORE-169 - instantiating DTLoggerFactory during test causes incorrect 
logging behavior

@tweise, @chandnisingh Please review

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vrozov/apex-core APEXCORE-169

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-core/pull/375.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #375


commit 36d84109476181eb5f1ab7326d253d278084a36f
Author: Vlad Rozov 
Date:   2016-08-25T18:25:31Z

APEXCORE-169 - instantiating DTLoggerFactory during test causes incorrect 
logging behavior




> instantiating DTLoggerFactory during test causes incorrect logging behavior
> ---
>
> Key: APEXCORE-169
> URL: https://issues.apache.org/jira/browse/APEXCORE-169
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>
> After DTLoggerFactory is instantiated in maven build, log levels in 
> log4j.properties are ignored.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (APEXMALHAR-2202) Move accumulations to correct package

[Shunxin Lu (JIRA)]

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

Shunxin Lu reassigned APEXMALHAR-2202:
--

Assignee: Shunxin Lu

> Move accumulations to correct package
> -
>
> Key: APEXMALHAR-2202
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2202
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>Assignee: Shunxin Lu
>
> They are currently under org.apache.apex.malhar.lib.window.impl.accumulation 
> but these are classes that the user would use directly. The better place 
> might be org.apache.apex.malhar.lib.window.accumulation 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (APEXMALHAR-2202) Move accumulations to correct package

[Thomas Weise (JIRA)]

Thomas Weise created APEXMALHAR-2202:


 Summary: Move accumulations to correct package
 Key: APEXMALHAR-2202
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2202
 Project: Apache Apex Malhar
  Issue Type: Task
Reporter: Thomas Weise


They are currently under org.apache.apex.malhar.lib.window.impl.accumulation 
but these are classes that the user would use directly. The better place might 
be org.apache.apex.malhar.lib.window.accumulation 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2201) Suppress console output in Stream API tests

[Thomas Weise (JIRA)]

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

Thomas Weise commented on APEXMALHAR-2201:
--

See https://github.com/apache/apex-malhar/pull/339

> Suppress console output in Stream API tests
> ---
>
> Key: APEXMALHAR-2201
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2201
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>
> There is quite a bit of console output in the CI. It would be nice to 
> suppress that when running as unit test, we are not interested what gets 
> printed to the console but what the test asserts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (APEXMALHAR-2201) Suppress console output in Stream API tests

[Thomas Weise (JIRA)]

Thomas Weise created APEXMALHAR-2201:


 Summary: Suppress console output in Stream API tests
 Key: APEXMALHAR-2201
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2201
 Project: Apache Apex Malhar
  Issue Type: Task
Reporter: Thomas Weise


There is quite a bit of console output in the CI. It would be nice to suppress 
that when running as unit test, we are not interested what gets printed to the 
console but what the test asserts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2200) Enable checkstyle for demos

[Thomas Weise (JIRA)]

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

Thomas Weise commented on APEXMALHAR-2200:
--

See https://github.com/apache/apex-malhar/pull/339

> Enable checkstyle for demos
> ---
>
> Key: APEXMALHAR-2200
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2200
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Thomas Weise
>
> It is turned off in the parent pom, which will cause new modules to be under 
> the radar. Should be enabled and then turned off for legacy modules that 
> cannot be fixed easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2134) Catch NullPointerException if some Kafka partition has no leader broker

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on APEXMALHAR-2134:


GitHub user chaithu14 opened a pull request:

https://github.com/apache/apex-malhar/pull/379

APEXMALHAR-2134 Fix the NullPointerException, if the kafka partition has no 
leader broker



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chaithu14/incubator-apex-malhar 
APEXMALHAR-2134-NP-LB

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/379.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #379


commit 8b662fb11f0b77373d302c58b4522011806bbfa9
Author: chaitanya 
Date:   2016-08-25T17:41:17Z

APEXMALHAR-2134 Fix the NullPointerException, if the kafka partition has no 
leader broker




> Catch NullPointerException if some Kafka partition has no leader broker
> ---
>
> Key: APEXMALHAR-2134
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2134
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Siyuan Hua
>Assignee: Chaitanya
>  Labels: newbie
> Fix For: 3.5.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Kafka partition could have no leader broker some time and we need to catch 
> exception and skip that partition for the time until new leader is elected
> Here is the exception we see in the stacktrace
> 2016-07-05 14:00:46,087 ERROR kafka.SimpleKafkaConsumer 
> (SimpleKafkaConsumer.java:run(481)) - Exception {}
> java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
> at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
> at 
> com.datatorrent.contrib.kafka.SimpleKafkaConsumer$MetaDataMonitorTask.monitorMetadata(SimpleKafkaConsumer.java:511)
> at 
> com.datatorrent.contrib.kafka.SimpleKafkaConsumer$MetaDataMonitorTask.run(SimpleKafkaConsumer.java:477)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> 2016-07-05 14:01:15,999 ERROR kafka.SimpleKafkaConsumer 
> (SimpleKafkaConsumer.java:run(481)) - Exception {}
> java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
> at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
> at 
> com.datatorrent.contrib.kafka.SimpleKafkaConsumer$MetaDataMonitorTask.monitorMetadata(SimpleKafkaConsumer.java:511)
> at 
> com.datatorrent.contrib.kafka.SimpleKafkaConsumer$MetaDataMonitorTask.run(SimpleKafkaConsumer.java:477)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] apex-malhar pull request #379: APEXMALHAR-2134 Fix the NullPointerException,...

[chaithu14]

GitHub user chaithu14 opened a pull request:

https://github.com/apache/apex-malhar/pull/379

APEXMALHAR-2134 Fix the NullPointerException, if the kafka partition has no 
leader broker



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chaithu14/incubator-apex-malhar 
APEXMALHAR-2134-NP-LB

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/379.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #379


commit 8b662fb11f0b77373d302c58b4522011806bbfa9
Author: chaitanya 
Date:   2016-08-25T17:41:17Z

APEXMALHAR-2134 Fix the NullPointerException, if the kafka partition has no 
leader broker




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (APEXMALHAR-2183) Add user document for CsvFormatter operator

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on APEXMALHAR-2183:


Github user venkateshkottapalli closed the pull request at:

https://github.com/apache/apex-malhar/pull/378


> Add user document for CsvFormatter operator
> ---
>
> Key: APEXMALHAR-2183
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2183
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Venkatesh Kottapalli
>Assignee: Venkatesh Kottapalli
>  Labels: newbie
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Add user documentation for CsvFormatter operator



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] apex-malhar pull request #378: APEXMALHAR-2183 Documentation for CsvFormatte...

[venkateshkottapalli]

Github user venkateshkottapalli closed the pull request at:

https://github.com/apache/apex-malhar/pull/378


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (APEXMALHAR-2142) High-level API window support

[Thomas Weise (JIRA)]

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

Thomas Weise resolved APEXMALHAR-2142.
--
Resolution: Fixed

> High-level API window support
> -
>
> Key: APEXMALHAR-2142
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2142
> Project: Apache Apex Malhar
>  Issue Type: New Feature
>Reporter: Siyuan Hua
>Assignee: Siyuan Hua
>  Labels: roadmap
> Fix For: 3.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2142) High-level API window support

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on APEXMALHAR-2142:


Github user asfgit closed the pull request at:

https://github.com/apache/apex-malhar/pull/339


> High-level API window support
> -
>
> Key: APEXMALHAR-2142
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2142
> Project: Apache Apex Malhar
>  Issue Type: New Feature
>Reporter: Siyuan Hua
>Assignee: Siyuan Hua
>  Labels: roadmap
> Fix For: 3.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] apex-malhar pull request #339: APEXMALHAR-2142 Windowed Stream First Impleme...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/apex-malhar/pull/339


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Malhar 3.5.0 release

[Chaitanya Chebolu]

Hi Thomas,

   I will fix APEXMALHAR-2134.

Regards,
Chaitanya

On Thu, Aug 25, 2016 at 9:13 PM, Thomas Weise 
wrote:

> We are almost ready to get the RC out.
>
> Can someone fix APEXMALHAR-2134 for the release?
>
>
> On Wed, Aug 17, 2016 at 12:56 PM, Thomas Weise 
> wrote:
>
> > Friendly reminder.. There are still a few unresolved tickets for 3.5:
> >
> > https://issues.apache.org/jira/issues/?jql=fixVersion%
> > 20%3D%203.5.0%20AND%20project%20%3D%20APEXMALHAR%20AND%
> 20resolution%20%3D%
> > 20Unresolved%20ORDER%20BY%20priority%20DESC
> >
> > Please remove the fix version unless you expect to complete the work in
> > the next few days.
> >
> > And we need to complete the PR for high level API:
> >
> > https://issues.apache.org/jira/browse/APEXMALHAR-2142
> >
> > Thanks,
> > Thomas
> >
> >
> > On Fri, Aug 5, 2016 at 2:12 AM, Chaitanya Chebolu <
> > chaita...@datatorrent.com> wrote:
> >
> >> APEXMALHAR-2100. PR is open: https://github.com/apache/apex
> >> -malhar/pull/330
> >>
> >> Regards,
> >> Chaitanya
> >>
> >> On Fri, Aug 5, 2016 at 1:10 PM, Priyanka Gugale <
> priya...@datatorrent.com
> >> >
> >> wrote:
> >>
> >> > APEXMALHAR-2171
> >> > PR is open: https://github.com/apache/apex-malhar/pull/358
> >> >
> >> > -Priyanka
> >> >
> >> > On Fri, Aug 5, 2016 at 12:32 PM, Yogi Devendra <
> >> > devendra.vyavah...@gmail.com
> >> > > wrote:
> >> >
> >> > > Fix for APEXMALHAR-2176
> >> > > PR open: https://github.com/apache/apex-malhar/pull/361
> >> > >
> >> > > ~ Yogi
> >> > >
> >> > > On 1 August 2016 at 11:59, Chinmay Kolhatkar <
> chin...@datatorrent.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > APEXMALHAR-2128 is already done. Somehow the status did not go to
> >> > > resolved.
> >> > > > Changed it now.
> >> > > >
> >> > > > On Fri, Jul 29, 2016 at 1:53 PM, Yogi Devendra <
> >> > > > devendra.vyavah...@gmail.com
> >> > > > > wrote:
> >> > > >
> >> > > > > APEXMALHAR-2116
> >> > > > > https://github.com/apache/apex-malhar/pull/326
> >> > > > >
> >> > > > > @Ram
> >> > > > > Your review comments are incorporated. Could you please have a
> >> look
> >> > at
> >> > > > > this?
> >> > > > >
> >> > > > > ~ Yogi
> >> > > > >
> >> > > > > On 29 July 2016 at 13:49, Thomas Weise 
> >> > wrote:
> >> > > > >
> >> > > > > > Hi,
> >> > > > > >
> >> > > > > > I would suggest to target the 3.5.0 release with an RC out
> >> perhaps
> >> > 2
> >> > > > > weeks
> >> > > > > > from now, as there is a good amount of work that we should
> make
> >> > > > available
> >> > > > > > to the users:
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > https://issues.apache.org/jira/browse/APEXMALHAR/
> >> > > > fixforversion/12335815/?selectedTab=com.atlassian.
> >> > > > jira.jira-projects-plugin:version-issues-panel
> >> > > > > >
> >> > > > > > I also think that the following should go in:
> >> > > > > >
> >> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2128
> >> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2142
> >> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2063
> >> > > > > >
> >> > > > > > Any other candidates?
> >> > > > > >
> >> > > > > > There are quite a few other PRs open:
> >> > > > > >
> >> > > > > > https://github.com/apache/apex-malhar/pulls
> >> > > > > >
> >> > > > > > Would be good to complete some more reviews for this release.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > Thomas
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>

[jira] [Created] (APEXMALHAR-2200) Enable checkstyle for demos

[Thomas Weise (JIRA)]

Thomas Weise created APEXMALHAR-2200:


 Summary: Enable checkstyle for demos
 Key: APEXMALHAR-2200
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2200
 Project: Apache Apex Malhar
  Issue Type: Task
Reporter: Thomas Weise


It is turned off in the parent pom, which will cause new modules to be under 
the radar. Should be enabled and then turned off for legacy modules that cannot 
be fixed easily.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2154) Update kafka 0.9 input operator to use new CheckpointNotificationListener

[Siyuan Hua (JIRA)]

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

Siyuan Hua commented on APEXMALHAR-2154:


I don't think so




> Update kafka 0.9 input operator to use new CheckpointNotificationListener
> -
>
> Key: APEXMALHAR-2154
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2154
> Project: Apache Apex Malhar
>  Issue Type: Improvement
>Reporter: Siyuan Hua
>Assignee: Chaitanya
> Fix For: 3.5.0
>
>
> CheckpointListener interface has been deprecated. We should upgrade the 
> operator to use the new one



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Malhar 3.5.0 release

[Thomas Weise]

We are almost ready to get the RC out.

Can someone fix APEXMALHAR-2134 for the release?


On Wed, Aug 17, 2016 at 12:56 PM, Thomas Weise 
wrote:

> Friendly reminder.. There are still a few unresolved tickets for 3.5:
>
> https://issues.apache.org/jira/issues/?jql=fixVersion%
> 20%3D%203.5.0%20AND%20project%20%3D%20APEXMALHAR%20AND%20resolution%20%3D%
> 20Unresolved%20ORDER%20BY%20priority%20DESC
>
> Please remove the fix version unless you expect to complete the work in
> the next few days.
>
> And we need to complete the PR for high level API:
>
> https://issues.apache.org/jira/browse/APEXMALHAR-2142
>
> Thanks,
> Thomas
>
>
> On Fri, Aug 5, 2016 at 2:12 AM, Chaitanya Chebolu <
> chaita...@datatorrent.com> wrote:
>
>> APEXMALHAR-2100. PR is open: https://github.com/apache/apex
>> -malhar/pull/330
>>
>> Regards,
>> Chaitanya
>>
>> On Fri, Aug 5, 2016 at 1:10 PM, Priyanka Gugale > >
>> wrote:
>>
>> > APEXMALHAR-2171
>> > PR is open: https://github.com/apache/apex-malhar/pull/358
>> >
>> > -Priyanka
>> >
>> > On Fri, Aug 5, 2016 at 12:32 PM, Yogi Devendra <
>> > devendra.vyavah...@gmail.com
>> > > wrote:
>> >
>> > > Fix for APEXMALHAR-2176
>> > > PR open: https://github.com/apache/apex-malhar/pull/361
>> > >
>> > > ~ Yogi
>> > >
>> > > On 1 August 2016 at 11:59, Chinmay Kolhatkar > >
>> > > wrote:
>> > >
>> > > > APEXMALHAR-2128 is already done. Somehow the status did not go to
>> > > resolved.
>> > > > Changed it now.
>> > > >
>> > > > On Fri, Jul 29, 2016 at 1:53 PM, Yogi Devendra <
>> > > > devendra.vyavah...@gmail.com
>> > > > > wrote:
>> > > >
>> > > > > APEXMALHAR-2116
>> > > > > https://github.com/apache/apex-malhar/pull/326
>> > > > >
>> > > > > @Ram
>> > > > > Your review comments are incorporated. Could you please have a
>> look
>> > at
>> > > > > this?
>> > > > >
>> > > > > ~ Yogi
>> > > > >
>> > > > > On 29 July 2016 at 13:49, Thomas Weise 
>> > wrote:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > I would suggest to target the 3.5.0 release with an RC out
>> perhaps
>> > 2
>> > > > > weeks
>> > > > > > from now, as there is a good amount of work that we should make
>> > > > available
>> > > > > > to the users:
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > https://issues.apache.org/jira/browse/APEXMALHAR/
>> > > > fixforversion/12335815/?selectedTab=com.atlassian.
>> > > > jira.jira-projects-plugin:version-issues-panel
>> > > > > >
>> > > > > > I also think that the following should go in:
>> > > > > >
>> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2128
>> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2142
>> > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2063
>> > > > > >
>> > > > > > Any other candidates?
>> > > > > >
>> > > > > > There are quite a few other PRs open:
>> > > > > >
>> > > > > > https://github.com/apache/apex-malhar/pulls
>> > > > > >
>> > > > > > Would be good to complete some more reviews for this release.
>> > > > > >
>> > > > > > Thanks,
>> > > > > > Thomas
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

[jira] [Resolved] (APEXMALHAR-2154) Update kafka 0.9 input operator to use new CheckpointNotificationListener

[Thomas Weise (JIRA)]

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

Thomas Weise resolved APEXMALHAR-2154.
--
Resolution: Fixed

> Update kafka 0.9 input operator to use new CheckpointNotificationListener
> -
>
> Key: APEXMALHAR-2154
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2154
> Project: Apache Apex Malhar
>  Issue Type: Improvement
>Reporter: Siyuan Hua
>Assignee: Chaitanya
> Fix For: 3.5.0
>
>
> CheckpointListener interface has been deprecated. We should upgrade the 
> operator to use the new one



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)