[
https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565218#comment-15565218
]
Alex McCullough commented on APEXCORE-528:
--
The code for this is done. There is
Github user brightchen closed the pull request at:
https://github.com/apache/apex-malhar/pull/404
---
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 featur
[
https://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565679#comment-15565679
]
ASF GitHub Bot commented on APEXMALHAR-2190:
Github user brightchen close
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 https://gi
[
https://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565680#comment-15565680
]
ASF GitHub Bot commented on APEXMALHAR-2190:
GitHub user brightchen reope
[
https://issues.apache.org/jira/browse/APEXMALHAR-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Munagala V. Ramanath updated APEXMALHAR-2274:
-
Description:
When there are a large number of files in the monitored
Yes, it should be accessible to project. How do we restrict it to dev@
only? Is there a convention to share this data open outside dev@?
Thks
Amol
On Mon, Oct 10, 2016 at 6:59 PM, Thomas Weise wrote:
> +1 this will be very valuable
>
> How would the data be accessible to the project?
>
>
> On
+Michelle (since for some reason since she didn't receive the last email
from Sasha).
Hi Thomas/David,
Can either of you guys take the lead on summarizing the changes that
Michelle should make on the Apex website? Since we are still receiving
feedback on what the changes should look like, its bet
Hi,
The comments were not made on the JIRA and maybe that's why Michelle did
not see it. The summary looks good:
https://issues.apache.org/jira/browse/APEXCORE-514
I also like the suggestion of dropping "Home". Let's keep it with that for
this iteration. We can make more changes later.
Thanks
Should we also remove the 4 buttons under Apache Apex as they are
repetitive?
On Tue, Oct 11, 2016 at 9:55 AM, Thomas Weise wrote:
> Hi,
>
> The comments were not made on the JIRA and maybe that's why Michelle did
> not see it. The summary looks good:
>
> https://issues.apache.org/jira/browse/AP
I'm for it, but I'm also for moving forward with what was already
summarized and do it in next round if more discussion is needed.
For next batch I would also like to remove "Announcements" - it's covered
on the home page. And upcoming meetups needs to be removed from home page
as well, that has t
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566027#comment-15566027
]
Thomas Weise commented on APEXCORE-514:
---
The Github top level item should link to
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566050#comment-15566050
]
Michelle Xiao commented on APEXCORE-514:
upate:
1. Nav bar:
a. change Docs to
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566050#comment-15566050
]
Michelle Xiao edited comment on APEXCORE-514 at 10/11/16 5:38 PM:
I'm fine if you want to make those changes in the next round. Just want to
let you know that Michelle won't be able to get to the next set of changes
before mid to end of November. She will focusing on the new DT website
starting this week.
On Tue, Oct 11, 2016 at 10:11 AM, Thomas Weise
wrote:
>
>From what I know, there is an admin user for each account (and
corresponding tracking code) on google analytics.
https://support.google.com/analytics/answer/1008080
They also have user management for adding/removing users to this account,
but not sure if we can add an email alias there.
https:/
Maybe add one user that is accessible to the PMC?
On Tue, Oct 11, 2016 at 10:59 AM, Ashwin Chandra Putta <
ashwinchand...@gmail.com> wrote:
> From what I know, there is an admin user for each account (and
> corresponding tracking code) on google analytics.
>
> https://support.google.com/analytic
Well, if that is so let's remove the buttons and put them back if someone
really wants them :-)
Other small changes can be also be made by other community members.
On Tue, Oct 11, 2016 at 10:58 AM, Kartavya Jain
wrote:
> I'm fine if you want to make those changes in the next round. Just want to
[
https://issues.apache.org/jira/browse/APEXCORE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-549:
-
Assignee: (was: Sandesh)
> Check for problematic hadoop jars at launch time
> --
[
https://issues.apache.org/jira/browse/APEXCORE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566187#comment-15566187
]
ASF GitHub Bot commented on APEXCORE-552:
-
GitHub user davidyan74 opened a pull
GitHub user davidyan74 opened a pull request:
https://github.com/apache/apex-core/pull/409
APEXCORE-552 #resolve added support for application tags
@PramodSSImmaneni please merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dav
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566050#comment-15566050
]
Michelle Xiao edited comment on APEXCORE-514 at 10/11/16 6:44 PM:
Sure, sounds good. I guess, it might need to be a Google Account. This is
what the user management says: "User e-mail that is registered in Google
accounts"
Regards,
Ashwin.
On Tue, Oct 11, 2016 at 11:13 AM, Thomas Weise wrote:
> Maybe add one user that is accessible to the PMC?
>
>
> On Tue, O
If you are going to manage it, how about you add the folks that are
interested in it on-demand?
On Tue, Oct 11, 2016 at 11:55 AM, Ashwin Chandra Putta <
ashwinchand...@gmail.com> wrote:
> Sure, sounds good. I guess, it might need to be a Google Account. This is
> what the user management says: "
Perfect, I just created an UA tracking code. I will create a JIRA and add
it there so we can add it to apex website.
Regards,
Ashwin.
On Tue, Oct 11, 2016 at 12:55 PM, Thomas Weise wrote:
> If you are going to manage it, how about you add the folks that are
> interested in it on-demand?
>
>
> O
Ashwin Chandra Putta created APEXCORE-553:
-
Summary: Add google analytics tracking to apex website
Key: APEXCORE-553
URL: https://issues.apache.org/jira/browse/APEXCORE-553
Project: Apache Apex
Here is the JIRA: https://issues.apache.org/jira/browse/APEXCORE-553
Regards,
Ashwin.
On Tue, Oct 11, 2016 at 2:18 PM, Ashwin Chandra Putta <
ashwinchand...@gmail.com> wrote:
> Perfect, I just created an UA tracking code. I will create a JIRA and add
> it there so we can add it to apex website.
[
https://issues.apache.org/jira/browse/APEXMALHAR-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise moved APEXCORE-554 to APEXMALHAR-2287:
---
Workflow: Default workflow, editable Closed status (was:
Thomas Weise created APEXCORE-554:
-
Summary: Missing documentation for Kafka 0.9 operators
Key: APEXCORE-554
URL: https://issues.apache.org/jira/browse/APEXCORE-554
Project: Apache Apex Core
[
https://issues.apache.org/jira/browse/APEXMALHAR-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2287:
-
Description: We need documentation under
http://apex.apache.org/docs/malhar/operators
[
https://issues.apache.org/jira/browse/APEXMALHAR-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2287:
-
Affects Version/s: 3.5.0
> Missing documentation for Kafka 0.9 operators
> --
Thomas Weise created APEXMALHAR-2288:
Summary: Kafka 0.8.x input operator doc outdated and incomplete
Key: APEXMALHAR-2288
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2288
Project: Apache
[
https://issues.apache.org/jira/browse/APEXMALHAR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2288:
-
Description:
http://apex.apache.org/docs/malhar/operators/kafkaInputOperator/
The do
Thomas Weise created APEXCORE-555:
-
Summary: Update application developer guide
Key: APEXCORE-555
URL: https://issues.apache.org/jira/browse/APEXCORE-555
Project: Apache Apex Core
Issue Type:
[
https://issues.apache.org/jira/browse/APEXCORE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXCORE-555:
--
Description:
http://apex.apache.org/docs/apex/application_development/
Quite some of it is ou
Github user mattqzhang closed the pull request at:
https://github.com/apache/apex-malhar/pull/448
---
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 featur
GitHub user mattqzhang reopened a pull request:
https://github.com/apache/apex-malhar/pull/448
APEXMALHAR-2254-2269-2270 Fix bugs on replay tuple skipping and idempâ¦
@PramodSSImmaneni please review it.
You can merge this pull request into a Git repository by running:
$ git pu
[
https://issues.apache.org/jira/browse/APEXMALHAR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566954#comment-15566954
]
ASF GitHub Bot commented on APEXMALHAR-2254:
GitHub user mattqzhang reope
[
https://issues.apache.org/jira/browse/APEXMALHAR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566953#comment-15566953
]
ASF GitHub Bot commented on APEXMALHAR-2254:
Github user mattqzhang close
bright chen created APEXMALHAR-2289:
---
Summary: Managed State benchmark improvement
Key: APEXMALHAR-2289
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2289
Project: Apache Apex Malhar
GitHub user davidyan74 opened a pull request:
https://github.com/apache/apex-malhar/pull/449
APEXMALHAR-2280 First iteration for windowed operator documentation
@tweise please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
[
https://issues.apache.org/jira/browse/APEXMALHAR-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567004#comment-15567004
]
ASF GitHub Bot commented on APEXMALHAR-2280:
GitHub user davidyan74 opene
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/444
---
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-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567013#comment-15567013
]
ASF GitHub Bot commented on APEXMALHAR-2281:
Github user asfgit closed th
[
https://issues.apache.org/jira/browse/APEXMALHAR-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved APEXMALHAR-2281.
--
Resolution: Fixed
Fix Version/s: 3.6.0
> ManagedState: race condition with p
[
https://issues.apache.org/jira/browse/APEXMALHAR-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567029#comment-15567029
]
ASF GitHub Bot commented on APEXMALHAR-2280:
Github user davidyan74 close
Github user davidyan74 closed the pull request at:
https://github.com/apache/apex-malhar/pull/449
---
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 featur
[
https://issues.apache.org/jira/browse/APEXMALHAR-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567033#comment-15567033
]
ASF GitHub Bot commented on APEXMALHAR-2282:
GitHub user davidyan74 opene
GitHub user davidyan74 opened a pull request:
https://github.com/apache/apex-malhar/pull/450
APEXMALHAR-2282 First iteration for windowed operator documentation
@tweise please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Hi All,
Operators that are not making progress are killed after
TIMEOUT_WINDOW_COUNT. But this doesn't take the operator recovery into
account. Operators that are recovering may need more time than what is set
in TIMEOUT_WINDOW_COUNT.
The new attribute, RECOVERY_WINDOW_TIMEOUT_COUNT, will be used
+1 have seen scenarios where operators that don't utilize large state
management take a while to load state from recovery.
On Tue, Oct 11, 2016 at 5:05 PM, Sandesh Hegde
wrote:
> Hi All,
>
> Operators that are not making progress are killed after
> TIMEOUT_WINDOW_COUNT. But this doesn't take the
GitHub user ShunxinLu opened a pull request:
https://github.com/apache/apex-malhar/pull/451
Renamed MergeWindowedOperator to WindowedMergeOperator.
@davidyan74 @tweise Please review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567659#comment-15567659
]
Chaitanya commented on APEXMALHAR-2284:
---
I am looking into it. But, these tests
Here is a Home page screenshot without 4 buttons. "Now with event-time
windowing and high-level API" is a separator paragraph, can I place it
under "Enterprise-grade unified stream ..." i.e. the buttons location?
[image: Inline image 2]
On Tue, Oct 11, 2016 at 11:15 AM, Thomas Weise wrote:
>
Yes, that can be moved up and it will free up space.
On Tue, Oct 11, 2016 at 10:43 PM, Michelle Xiao
wrote:
> Here is a Home page screenshot without 4 buttons. "Now with event-time
> windowing and high-level API" is a separator paragraph, can I place it
> under "Enterprise-grade unified stream
55 matches
Mail list logo
