[
https://issues.apache.org/jira/browse/APEXCORE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849510#comment-15849510
]
ASF GitHub Bot commented on APEXCORE-604:
-
Github user tushargosavi closed the p
GitHub user tushargosavi reopened a pull request:
https://github.com/apache/apex-core/pull/447
APEXCORE-604 extend DAG API to get operators and streams from the DAG.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tushargosavi/ap
[
https://issues.apache.org/jira/browse/APEXCORE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849511#comment-15849511
]
ASF GitHub Bot commented on APEXCORE-604:
-
GitHub user tushargosavi reopened a p
Github user tushargosavi closed the pull request at:
https://github.com/apache/apex-core/pull/447
---
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
Deepak Narkhede created APEXCORE-634:
Summary: Apex Platform unable to set Unifier attribute window
time out
Key: APEXCORE-634
URL: https://issues.apache.org/jira/browse/APEXCORE-634
Project: Ap
This can be done neatly and possibly completely outside the engine if we
are able to deliver schema information via the control tuple mechanism.
Current control tuple proposal reorders the control tuple to be delivered
at the end of the window to the operator. This would not be feasible for
schemas
I think dynamic schema would be good to consider (schema known and possibly
changing at runtime). Some applications cannot be written under the
assumption that the schema is known upfront.
Also, does this really need to leak into the engine? I think it would be
good to consider alternatives and tr
Note this is follow-up from a previous discussion on the PMC list.
I think the decision on activity for the ApacheApex handle should be with
the PMC and the handle should be operated by PMC members.
See http://apache.org/foundation/how-it-works.html for more context about
roles and responsibiliti
+1 I strongly agree since the community is growing. As a community, we need
to be able to publish updates and relevant content to followers. All
committers having access to publish tweets makes community inclusive.
Regards,
Ashwin.
On Feb 1, 2017 4:43 PM, "Amol Kekre" wrote:
I want to see what
[
https://issues.apache.org/jira/browse/APEXCORE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849192#comment-15849192
]
ASF GitHub Bot commented on APEXCORE-259:
-
Github user sandeshh closed the pull
Github user sandeshh closed the pull request at:
https://github.com/apache/apex-core/pull/453
---
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
+1 for community volunteers to manually maintain the list.
+1 for adding the events to the main page.
The community as a whole is working toward Apex adoption, we should
collectively publish all relevant events that help toward the common goal.
All Apex events should be treated equally irrespectiv
I am ok if there is a volunteer.
Thks
Amol
On Wed, Feb 1, 2017 at 4:34 PM, Pramod Immaneni
wrote:
> How about asking for volunteers in the community to manually maintain the
> list. How about the specific request to add the conference link to the main
> page?
>
> Thanks
>
> On Wed, Feb 1, 2017
I want to see what the community feels about posting tweets on ApacheApex
handle. My thoughts are that the committers should have the right to post a
tweek on ApacheApex. For contributors and anyone else, we could have a
mechanism where they request it on dev@apex.apache.org and a committer can
hel
How about asking for volunteers in the community to manually maintain the
list. How about the specific request to add the conference link to the main
page?
Thanks
On Wed, Feb 1, 2017 at 10:33 AM, Amol Kekre wrote:
> I agree with Thomas on not putting meetup events. meetup.com does "index
> by
>
[
https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849066#comment-15849066
]
ASF GitHub Bot commented on APEXMALHAR-2239:
GitHub user d9liang opened a
GitHub user d9liang opened a pull request:
https://github.com/apache/apex-malhar/pull/546
APEXMALHAR-2239 Handle Null pointer exception in JDBCPojoInputOperator
This is to handle the exception when we set a query to fetch rows and have
additional columns in fieldInfos.
You can merg
Sandesh created APEXCORE-633:
Summary: Add unit tests for DataList
Key: APEXCORE-633
URL: https://issues.apache.org/jira/browse/APEXCORE-633
Project: Apache Apex Core
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/APEXCORE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-632:
Assignee: Sandesh
> Fix the existing unit test and possibly move them to JUnit from testNg
>
Sandesh created APEXCORE-632:
Summary: Fix the existing unit test and possibly move them to
JUnit from testNg
Key: APEXCORE-632
URL: https://issues.apache.org/jira/browse/APEXCORE-632
Project: Apache Apex
Sandesh created APEXCORE-631:
Summary: Improving BufferServer tests
Key: APEXCORE-631
URL: https://issues.apache.org/jira/browse/APEXCORE-631
Project: Apache Apex Core
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/APEXCORE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-630:
-
Summary: Remove FastDataList & related components from BufferServer &
Engine (was: Remove FastDataList
[
https://issues.apache.org/jira/browse/APEXCORE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848891#comment-15848891
]
ASF GitHub Bot commented on APEXCORE-630:
-
GitHub user sandeshh opened a pull re
GitHub user sandeshh opened a pull request:
https://github.com/apache/apex-core/pull/462
APEXCORE-630 Removing FastDataList as it is not complete and not deveâ¦
â¦loped, so no reason to keep it
@vrozov please review.
You can merge this pull request into a Git repository b
Sandesh created APEXCORE-630:
Summary: Remove FastDataList & related components from BufferServer
Key: APEXCORE-630
URL: https://issues.apache.org/jira/browse/APEXCORE-630
Project: Apache Apex Core
I agree with Thomas on not putting meetup events. meetup.com does "index by
Apex", and the search would simply pick up anyone putting Apex in the event
and at times they are not relevant to Apex. We get too much clutter. So the
only way out is to manually select the events, and then take them out a
[
https://issues.apache.org/jira/browse/APEXCORE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov updated APEXCORE-504:
Affects Version/s: 3.5.0
> Possible race condition in StreamingContainerAgent.getStreamCodec()
> -
On Wed, Feb 1, 2017 at 8:55 AM, Thomas Weise wrote:
> Since the conference was beforehand discussed with the PMC I think you
> could list it under:
>
> http://apex.apache.org/community.html#events
How about putting something on the website main page?
>
>
> There is already a link to all meetu
Since the conference was beforehand discussed with the PMC I think you
could list it under:
http://apex.apache.org/community.html#events
There is already a link to all meetup groups that have "Apache Apex" as
topic.
As for other meetup references, IMO direct vendor meetup group references
don't
Hi,
I wanted to discuss a couple of items. First, as many of you are aware, a
conference specifically for apex, apex big data world 2017, is coming up in
the next couple of months. There is one in Pune India and another in San
Jose, USA. I wanted to see if we can put links/information about it on
[
https://issues.apache.org/jira/browse/APEXCORE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXCORE-629:
--
Issue Type: Improvement (was: Bug)
> ApexCLI launch command does not support application inde
[
https://issues.apache.org/jira/browse/APEXCORE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXCORE-629:
--
Priority: Minor (was: Major)
> ApexCLI launch command does not support application index (vs.
32 matches
Mail list logo
