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
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15567659#comment-15567659
]
Chaitanya commented on APEXMALHAR-2284:
---
I am looking into it. But, these tests are passing in
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
+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.
[
https://issues.apache.org/jira/browse/APEXMALHAR-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15567033#comment-15567033
]
ASF GitHub Bot commented on APEXMALHAR-2282:
GitHub user davidyan74 opened a pull
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://issues.apache.org/jira/browse/APEXMALHAR-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15567029#comment-15567029
]
ASF GitHub Bot commented on APEXMALHAR-2280:
Github user davidyan74 closed the pull
[
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15567013#comment-15567013
]
ASF GitHub Bot commented on APEXMALHAR-2281:
Github user asfgit closed the pull request
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566954#comment-15566954
]
ASF GitHub Bot commented on APEXMALHAR-2254:
GitHub user mattqzhang reopened a pull
[
https://issues.apache.org/jira/browse/APEXMALHAR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566953#comment-15566953
]
ASF GitHub Bot commented on APEXMALHAR-2254:
Github user mattqzhang closed the pull
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
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
[
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
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
[
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
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:
[
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
>
[
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
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 moved APEXCORE-554 to APEXMALHAR-2287:
---
Workflow: Default workflow, editable Closed status
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.
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
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
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:
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
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566050#comment-15566050
]
Michelle Xiao edited comment on APEXCORE-514 at 10/11/16 6:44 PM:
--
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://issues.apache.org/jira/browse/APEXCORE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566187#comment-15566187
]
ASF GitHub Bot commented on APEXCORE-552:
-
GitHub user davidyan74 opened a pull request:
[
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
>
>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.
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
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566050#comment-15566050
]
Michelle Xiao edited comment on APEXCORE-514 at 10/11/16 5:38 PM:
--
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566050#comment-15566050
]
Michelle Xiao commented on APEXCORE-514:
upate:
1. Nav bar:
a. change Docs to Documentation,
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566027#comment-15566027
]
Thomas Weise commented on APEXCORE-514:
---
The Github top level item should link to
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
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:
>
>
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
+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
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
[
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565680#comment-15565680
]
ASF GitHub Bot commented on APEXMALHAR-2190:
GitHub user brightchen reopened a pull
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://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565679#comment-15565679
]
ASF GitHub Bot commented on APEXMALHAR-2190:
Github user brightchen closed the pull
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
[
https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565218#comment-15565218
]
Alex McCullough commented on APEXCORE-528:
--
The code for this is done. There is a process at my
[
https://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564665#comment-15564665
]
ASF GitHub Bot commented on APEXMALHAR-2190:
Github user brightchen closed the pull
[
https://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564666#comment-15564666
]
ASF GitHub Bot commented on APEXMALHAR-2190:
GitHub user brightchen reopened a pull
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
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
Right now nav bar has too many items, which causes it to render in 2
lines. See attachment.
I think you can drop Home button in favor of using the Apache Apex banner
as the home button, and probably Roadmap is the next best candidate
which can be moved one level below top nav. Additionally
53 matches
Mail list logo