Congrats Chinmay. Well deserved.
On Thu, May 24, 2018 at 10:10 PM Vlad Rozov wrote:
> Congrats Chinmay!
>
> Thank you,
>
> Vlad
>
> On 5/24/18 12:27, Ananth G wrote:
> > Congratulations Chinmay
> >
> > Regards
> > Ananth
> >
> >> On 25 May 2018, at 4:19 am, amol kekre
Congratulations Tushar!!
Regards,
Ashwin.
On Fri, Nov 3, 2017 at 9:17 AM, Pramod Immaneni
wrote:
> A bit delayed but nevertheless important announcement, Apache Apex PMC is
> pleased to announce Tushar Gosavi as a new PMC member.
>
> Tushar has been contributing to Apex
Congratulations Ananth. Well deserved!
On Fri, Nov 3, 2017 at 2:08 AM, Chinmay Kolhatkar
wrote:
> Congrats Ananth!!
>
> On Fri, Nov 3, 2017 at 2:37 PM, Priyanka Gugale wrote:
>
> > Congrats Ananth!!
> >
> > -Priyanka
> >
> > On Fri, Nov 3, 2017 at
ent anyone
> from continuing 3.x line. That's what versioning and branching are there
> for.
>
> Thomas
>
>
> On Fri, Aug 25, 2017 at 4:42 PM, Ashwin Chandra Putta <
> ashwinchand...@gmail.com> wrote:
>
> > Haha I missed your personal attacks Thomas. Love it! Thi
ated discussion threads as these already address
> some of what repeats here?
>
> On Fri, Aug 25, 2017 at 2:00 PM, Ashwin Chandra Putta <
> ashwinchand...@gmail.com> wrote:
>
> > I agree that it makes the project consistent to have the package names
> > ch
I agree that it makes the project consistent to have the package names
changed to org.apache.apex. However, it seems like an unnecessary overhead
to make a major version change for just changing package names. I may be
wrong but is there a major feature set in the proposed vote that deems for
a
Sunil,
You can poll the queue in end window since process method in the input port
does not get called if there is no incoming tuple. However, end window is
called irrespective of there are incoming tuples or not.
Regards,
Ashwin.
On Tue, Feb 21, 2017 at 11:32 AM, Sunil Parmar
of meetup groups that have "Apache Apex" as topic but the event
> has nothing to do with it.
>
> Also see: https://www.apache.org/foundation/marks/events
>
> Thanks,
> Thomas
>
>
> On Wed, Feb 1, 2017 at 4:45 PM, Ashwin Chandra Putta <
> ashwinchand...@gmail.co
+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"
+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
t; wrote:
> >> >
> >> > 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
> >> >
> >>
[
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781026#comment-15781026
]
Ashwin Chandra Putta commented on APEXCORE-592:
---
[~vrozov] The attribute descriptions help
Hitesh,
We should standardize the schema definition across apex for individual
operators and tuple classes.
I think you should be able to use schema definition for CSV parser without
the delimiter.
Regards,
Ashwin.
On Nov 14, 2016 2:45 AM, "Hitesh Kapoor" wrote:
> Hi
[
https://issues.apache.org/jira/browse/APEXCORE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Chandra Putta updated APEXCORE-553:
--
Description:
Add Google Analytics tracking to the apex.apache.org website so
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
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
; 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: "User e-mail that is
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.
> &g
>
> Thks
> Amol
>
>
> On Mon, Oct 10, 2016 at 6:59 PM, Thomas Weise <t...@apache.org> wrote:
>
> > +1 this will be very valuable
> >
> > How would the data be accessible to the project?
> >
> >
> > On Mon, Oct 10, 2016 at 6:19 PM, Ashwin Ch
I do not see a UA tracking code on the apex.apache.org webpages. Can we add
it? Google analytics is very valuable in learning about the website traffic
and what users are looking for.
I looked around other apache projects and they do have it. Spark, storm,
flink etc.
--
Regards,
Ashwin.
[
https://issues.apache.org/jira/browse/APEXMALHAR-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Chandra Putta updated APEXMALHAR-2233:
-
Description:
Bring relevant apps from the following examples
e brought into shape wrt
> > licensing, checkstyle, CI support etc.
> >
> >
> > On Tue, Sep 6, 2016 at 4:34 PM, Pramod Immaneni <pra...@datatorrent.com>
> > wrote:
> >
> > > Sounds like a good idea. How about merging demos with apps as well?
> >
Ashwin Chandra Putta created APEXMALHAR-2233:
Summary: Consolidate example apps into malhar apps
Key: APEXMALHAR-2233
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2233
Project
Hi All,
We have a lot of examples for apex malhar operators in the following
repository which resides outside of malhar.
https://github.com/DataTorrent/examples/tree/master/tutorials
Now that it has grown quite a bit, does it make sense to bring some of the
most common examples to malhar
We already discussed this in another thread and the consensus was to call
it "Initiatives" and add it to the top nav bar.
Regards,
Ashwin.
On Tue, Aug 23, 2016 at 3:35 PM, Kartavya Jain
wrote:
> We can place the "Roadmap" tab on the main nav bar so it easily visible
Ashwin Chandra Putta created APEXCORE-505:
-
Summary: setup and activate calls in operator block heartbeat loop
in container
Key: APEXCORE-505
URL: https://issues.apache.org/jira/browse/APEXCORE-505
In a separate thread I mean.
Regards,
Ashwin.
On Wed, Aug 10, 2016 at 2:01 PM, Ashwin Chandra Putta <
ashwinchand...@gmail.com> wrote:
> + dev@apex.apache.org
> - us...@apex.apache.org
>
> This is one of those best practices that we learn by experience during
>
+ dev@apex.apache.org
- us...@apex.apache.org
This is one of those best practices that we learn by experience during
operator development. It will save a lot of time during operator
development if we can catch and throw validation error when someone emits
tuples in a non separate thread.
I don't think we have such a feature, it will be a good addition. A
configuration parameter for number of operators in a container would be
useful as well.
Regards,
Ashwin.
On Wed, Aug 10, 2016 at 11:53 AM, Amol Kekre wrote:
> Good idea.
>
> Thks
> Amol
>
>
> On Wed, Aug
Congratulations Devendra and welcome!
Regards,
Ashwin.
On Wed, Aug 10, 2016 at 12:28 PM, Thomas Weise wrote:
> The Project Management Committee (PMC) for Apache Apex has asked Devendra
> Tagare to become a committer and we are pleased to announce that he has
> accepted.
>
>
+1 for common abstract class and specific implementations that are use case
specific.
Regards,
Ashwin.
On Mon, Aug 8, 2016 at 7:55 AM, Devendra Tagare
wrote:
> + 1 for a common Abstract Class.
>
> 0 - for adding ports.
>
> Use-case for CSV - data migration from
Send email to dev-unsubscr...@apex.apache.org to unsubscribe.
Regards,
Ashwin.
On Tue, Jul 26, 2016 at 4:23 PM, Praveen Kumar
wrote:
> unsubscribe
>
>
--
Regards,
Ashwin.
They can be made test scoped in malhar for testing. The user of this
operator can add the implementation specific dependency in their
application pom where they use this operator and supply the corresponding
connection factory class name.
Regards,
Ashwin.
On Thu, Jul 14, 2016 at 11:55 AM, Sanjay
Finally we have a robust jdbc polling input operator. Since it is
@evolving, we can make improvements over time as folks start using this
operator.
+1 for merging the PR.
Regards,
Ashwin.
On Tue, Jul 12, 2016 at 11:17 AM, Devendra Tagare wrote:
> All,
>
> We have
Added a few comments Pramod, otherwise looks good. Dividing the guidelines
would probably make sense. Contribution process related guidelines can go
into contribution guidelines and technical implementation related
guidelines can go into implementation guidelines. Another thing that might
be
Congratulations Siyuan!!
On Jun 15, 2016 9:26 PM, "Thomas Weise" wrote:
> The Apache Apex PMC is pleased to announce that Siyuan Hua is now a PMC
> member. We appreciate all his contributions to the project so far, and are
> looking forward to more.
>
> Welcome, Siyuan,
Hey no worries Sunil. Seems like the application master killed the
containers for the operator because it might not have received the
heartbeats for some time. This typically happens if the windows are not
moving forward in the container. Can you check the app master logs if the
heartbeats are
[
https://issues.apache.org/jira/browse/APEXMALHAR-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Chandra Putta closed APEXMALHAR-537.
---
Resolution: Invalid
> Need a Session computation operator which works
[
https://issues.apache.org/jira/browse/APEXMALHAR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Chandra Putta closed APEXMALHAR-281.
---
Resolution: Invalid
> [logstream] add ale
[
https://issues.apache.org/jira/browse/APEXMALHAR-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Chandra Putta closed APEXMALHAR-1150.
Resolution: Won't Fix
> create operator that can convert JSON str
[
https://issues.apache.org/jira/browse/APEXMALHAR-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310830#comment-15310830
]
Ashwin Chandra Putta commented on APEXMALHAR-1150:
--
correct, closing this.
> cre
[
https://issues.apache.org/jira/browse/APEXMALHAR-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Chandra Putta updated APEXMALHAR-2066:
-
Description:
Create a JDBC poller input operator that has
Instead of creating a new space for evolving operators, why not create a
new space for mature operators and graduate existing mature operators?
That way, it solves both the items of discussion
- having separation between evolving and mature operators.
- not having evolving operators in mature
43 matches
Mail list logo