+1.
On Sat, 26 Jan 2019, 11:56 pm amol kekre +1 for this proposal. The only caveat I have is
> -> "acceptable performance and resolving logical flaws identified during
> the review process"
>
> is subjective. Functionally working should cover any logical issues.
> Performance should be applicable
50 PM Chinmay Kolhatkar
wrote:
> Hi All,
>
> I've created following jiras encompassing the requirements (To be picked
> up in order):
> https://issues.apache.org/jira/browse/APEXMALHAR-2558
> https://issues.apache.org/jira/browse/APEXMALHAR-2559
>
> I'll start adding
Chinmay Kolhatkar created APEXMALHAR-2564:
-
Summary: Extend the UI Console to show physical operator info
Key: APEXMALHAR-2564
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2564
Chinmay Kolhatkar created APEXMALHAR-2563:
-
Summary: Extend the UI Console to show logical operator info
Key: APEXMALHAR-2563
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2563
Project
Chinmay Kolhatkar created APEXMALHAR-2562:
-
Summary: Update backend to serve console UI from stram
Key: APEXMALHAR-2562
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2562
Project
Chinmay Kolhatkar created APEXMALHAR-2561:
-
Summary: Update build steps for release build
Key: APEXMALHAR-2561
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2561
Project: Apache Apex
Chinmay Kolhatkar created APEXMALHAR-2560:
-
Summary: Create react project which shows application level
information
Key: APEXMALHAR-2560
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2560
ate the feature branch shortly so that we can start working
against it.
-Chinmay.
On Sat, Jun 16, 2018 at 7:07 PM Chinmay Kolhatkar
wrote:
> So here is how it'll be:
> 1. ReactJS application can be compiled for production builds. The output
> is set of html+css+compressed js fi
Chinmay Kolhatkar created APEXMALHAR-2559:
-
Summary: Add operational elements to UI Console
Key: APEXMALHAR-2559
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2559
Project: Apache
[
https://issues.apache.org/jira/browse/APEXMALHAR-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2559:
-
Assignee: (was: Chinmay Kolhatkar)
> Add operational eleme
[
https://issues.apache.org/jira/browse/APEXMALHAR-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2558:
-
Assignee: Chinmay Kolhatkar
> Create UI Console for show
Chinmay Kolhatkar created APEXMALHAR-2558:
-
Summary: Create UI Console for showing realtime apex app
information
Key: APEXMALHAR-2558
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2558
API to display
> > information in a browser, where they will be hosted is irrelevant. They
> > can be hosted by stram, but it should be possible to host them
> > externally without making modificaitons. If this is the case, I don't
> > have any objections to the prop
zov
> wrote:
> > > >
> > > >> Clarification: I am -0 on making UI part of the stram. I am +1 on
> > > >> providing reference webUI application outside of the stram.
> > > >>
> > > >> Thank you,
> > > >>
Hi Community,
I want to propose a feature in apex-core to have a UI component in stram.
This is influenced by how basic runtime information is shown on UI by spark.
This includes following features:
1. Webpage will be hosted by stram and will be available for user to view
in one of the two ways (
; >> On Thu, May 24, 2018 at 10:34 AM, Hitesh Kapoor <
> > > > > forhitesh...@gmail.com
> > > > > >> >
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >>> Congra
ker files in apex-core/release-3.7, my
> suggestion to create the branch in your repo, as done till now.
>
> You can still pilot the build for the latest image from apex-core/master
>
> Thanks
>
>
> On Wed, May 9, 2018 at 7:38 AM, Chinmay Kolhatkar <
> chinmaykolhatka..
+1 for approach 1. As Thomas mentioned, I think there metrics layer should
be abstracted out from its implementation. This way one can plugin
different metrics systems in apex.
Also keep in mind that there is a lot of code which uses AutoMetrics
annotations. We should help a smooth transition from
Yes Thomas. I'm going to create a docker image.
I was hoping that I can create the docker for 3.7.0 from new changes in
master which pulls dist atrato instead of creating from my repo. This will
act as a pilot for building docker from apex-core repo as well. Let me know
if this is fine.
Regards,
[
https://issues.apache.org/jira/browse/APEXCORE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXCORE-289:
--
Assignee: (was: Chinmay Kolhatkar)
> Encrypted Streams in Apex
[
https://issues.apache.org/jira/browse/APEXMALHAR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-1979:
-
Assignee: (was: Chinmay Kolhatkar)
> Ability to gener
[
https://issues.apache.org/jira/browse/APEXMALHAR-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2053:
-
Assignee: (was: Chinmay Kolhatkar)
> Add utility for mak
[
https://issues.apache.org/jira/browse/APEXCORE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXCORE-623:
--
Assignee: (was: Chinmay Kolhatkar)
> Schema propagation support in A
[
https://issues.apache.org/jira/browse/APEXCORE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466285#comment-16466285
]
Chinmay Kolhatkar commented on APEXCORE-813:
[~thw] and others (I
[
https://issues.apache.org/jira/browse/APEXCORE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXCORE-812:
--
Assignee: Chinmay Kolhatkar
> Update Docker Hub build account with build
[
https://issues.apache.org/jira/browse/APEXCORE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXCORE-813:
--
Assignee: Chinmay Kolhatkar
> Update docker build steps to use apex bin d
Chinmay Kolhatkar created APEXCORE-814:
--
Summary: Rename envvar DT_CLIENT_OPTS to APEX_CLIENT_OPTS
Key: APEXCORE-814
URL: https://issues.apache.org/jira/browse/APEXCORE-814
Project: Apache Apex
[
https://issues.apache.org/jira/browse/APEXCORE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXCORE-813:
---
Summary: Update docker build steps to use apex bin dist package (was:
Update
Chinmay Kolhatkar created APEXCORE-813:
--
Summary: Update docker build steps to generate apex deb from dist
binary package from apex-core repo
Key: APEXCORE-813
URL: https://issues.apache.org/jira/browse
Chinmay Kolhatkar created APEXCORE-812:
--
Summary: Update Docker Hub build account with build src from
apache repository
Key: APEXCORE-812
URL: https://issues.apache.org/jira/browse/APEXCORE-812
Chinmay Kolhatkar created APEXCORE-811:
--
Summary: Move docker build sourcecode from private repository to
apex-core repo
Key: APEXCORE-811
URL: https://issues.apache.org/jira/browse/APEXCORE-811
[
https://issues.apache.org/jira/browse/APEXCORE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXCORE-729:
---
Summary: Include an example in the apex core release binary (was: Include
an
[
https://issues.apache.org/jira/browse/APEXCORE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXCORE-729:
---
Issue Type: Task (was: Sub-task)
Parent: (was: APEXCORE-727)
> Incl
[
https://issues.apache.org/jira/browse/APEXCORE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463263#comment-16463263
]
Chinmay Kolhatkar commented on APEXCORE-729:
I suggest we make this
[
https://issues.apache.org/jira/browse/APEXCORE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXCORE-728:
--
Assignee: Chinmay Kolhatkar
> Include licenses for dependenc
[
https://issues.apache.org/jira/browse/APEXCORE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXCORE-731:
--
Assignee: Chinmay Kolhatkar (was: Thomas Weise)
> Modifications to
[
https://issues.apache.org/jira/browse/APEXCORE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXCORE-729:
--
Assignee: Chinmay Kolhatkar
> Include an example in the rele
[
https://issues.apache.org/jira/browse/APEXCORE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXCORE-727:
--
Assignee: Chinmay Kolhatkar (was: Pramod Immaneni)
> Create and publ
Hello Community,
I want to propose following improvements for apex-core build and related
steps:
1. Most (probably all of the open source project) has the a binary release
package of the software and not just the source release package. Currently
we have only source package. Luckily there are few
+1 for the release.
- Chinmay.
On 18 Jan 2018 8:58 pm, "Tushar Gosavi" wrote:
> +1 for the release
>
> Regards,
> - Tushar.
>
>
> On Thu, Jan 18, 2018 at 3:28 AM, Amol Kekre wrote:
>
> > +1
> >
> > Thks,
> > Amol
> >
> >
> > E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre*
> >
Congrats Tushar!!
On Fri, Nov 3, 2017 at 10:21 PM, Chaitanya Chebolu <
chaita...@datatorrent.com> wrote:
> Congratulations Tushar!!!
>
> On Fri, Nov 3, 2017 at 10:06 PM, Venkatesh Kottapalli <
> venkat...@datatorrent.com> wrote:
>
> > Congratulations Tushar!
> >
> > -Venky
> >
> > On Fri, Nov 3,
Congrats Ananth!!
On Fri, Nov 3, 2017 at 2:37 PM, Priyanka Gugale wrote:
> Congrats Ananth!!
>
> -Priyanka
>
> On Fri, Nov 3, 2017 at 2:20 PM, Thomas Weise wrote:
>
> > The Project Management Committee (PMC) for Apache Apex is pleased to
> > announce Ananth Gundabattula as new committer.
> >
>
+1.
- Chinmay.
On 25 Oct 2017 9:20 pm, "Chaitanya Chebolu"
wrote:
> +1 on new release.
>
> Thanks,
>
> On Wed, Oct 25, 2017 at 9:09 PM, Vlad Rozov wrote:
>
> > +1.
> >
> > Thank you,
> >
> > Vlad
> >
> >
> > On 10/25/17 08:21, Amol Kekre wrote:
> >
> >> +1 on a new malhar release.
> >>
> >> Th
nka
>
> On Tue, Aug 8, 2017 at 8:34 AM, Chinmay Kolhatkar >
> wrote:
>
> > Dear Community,
> >
> > Currently Apache Apex does not have a deliverable tarball which bundles
> the
> > dependent jars and apex cli which user can just download and get started
> >
Dear Community,
Currently Apache Apex does not have a deliverable tarball which bundles the
dependent jars and apex cli which user can just download and get started
with.
Having this would be also be useful for current integration with Apache
Bigtop as well. Currently in bigtop, the bigtop build
+1 for the best effort with warnings.
On Sun, Aug 6, 2017 at 9:19 PM, Pradeep Kumbhar
wrote:
> +1 for the best effort with warnings as default behavior and an optional
> flag for Validate & Fail (Ajay's suggestion)
>
>
> On Sun, Aug 6, 2017 at 12:14 PM, Mohit Jotwani
> wrote:
>
> > +1 for best
[
https://issues.apache.org/jira/browse/APEXCORE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036569#comment-16036569
]
Chinmay Kolhatkar commented on APEXCORE-740:
Chinmay Kolhatkar created APEXCORE-740:
--
Summary: Setup plugins does not identify operator classes because
they're loaded through different plugin classloaders
Key: APEXCORE-740
URL:
[
https://issues.apache.org/jira/browse/APEXCORE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXCORE-740:
---
Summary: Setup plugins does not identify operator classes because they're
l
Hi Thomas,
Even I'm currently occupied and won't be able to work on this as of now.
Also, you're already collaborator on docker-pool repository.
-Chinmay.
On Sat, Jun 3, 2017 at 3:08 PM, Aniruddha Thombare <
anirud...@datatorrent.com> wrote:
> Hi,
>
> I'm currently preoccupied, won't be able t
+1 for pramod's proposal.
On 19-May-2017 4:51 AM, "Sanjay Pujare" wrote:
> +1 for Pramod's proposal for impersonation.
>
> I have an issue with Sandesh's suggestion about making the new behavior as
> the default (or only) behavior. This will introduce incompatibility with
> other legacy tools (e
[
https://issues.apache.org/jira/browse/APEXCORE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007939#comment-16007939
]
Chinmay Kolhatkar commented on APEXCORE-720:
RCA:
Plugin event of
Chinmay Kolhatkar created APEXCORE-720:
--
Summary: In DAGExecution plugin, Context.getDAG returns null
Key: APEXCORE-720
URL: https://issues.apache.org/jira/browse/APEXCORE-720
Project: Apache
+1
On Fri, May 12, 2017 at 1:41 PM, Mohit Jotwani
wrote:
> +1
>
> Regards,
> Mohit
>
> On Fri, May 12, 2017 at 10:49 AM, Bhupesh Chawda
> wrote:
>
> > +1
> >
> > ~ Bhupesh
> >
> >
> > ___
> >
> > Bhupesh Chawda
> >
> > E: bhup...@datatorrent.c
[
https://issues.apache.org/jira/browse/APEXMALHAR-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2296:
-
Assignee: (was: Chinmay Kolhatkar)
> Apex SQL: Add support
[
https://issues.apache.org/jira/browse/APEXMALHAR-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2295:
-
Assignee: (was: Chinmay Kolhatkar)
> Apex SQL: Repl
[
https://issues.apache.org/jira/browse/APEXMALHAR-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2294:
-
Assignee: (was: Chinmay Kolhatkar)
> Apex SQL: Make opera
[
https://issues.apache.org/jira/browse/APEXMALHAR-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2293:
-
Assignee: (was: Chinmay Kolhatkar)
> Apex SQL: Add sql line
[
https://issues.apache.org/jira/browse/APEXMALHAR-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2292:
-
Assignee: (was: Chinmay Kolhatkar)
> Apex SQL: Add gene
[
https://issues.apache.org/jira/browse/APEXMALHAR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2453.
---
Resolution: Done
Fix Version/s: 3.8.0
> Add sort Accumulation
[
https://issues.apache.org/jira/browse/APEXMALHAR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXMALHAR-2453:
--
Summary: Add sort Accumulation for Windowed operator (was: Sort
[
https://issues.apache.org/jira/browse/APEXMALHAR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXMALHAR-2453:
--
Issue Type: New Feature (was: Task)
> Sort Accumulation for Windo
Chinmay Kolhatkar created APEXCORE-679:
--
Summary: Apex core 3.5.0 build failing with hadoop 2.7.3 dependency
Key: APEXCORE-679
URL: https://issues.apache.org/jira/browse/APEXCORE-679
Project
[
https://issues.apache.org/jira/browse/APEXMALHAR-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2376.
---
Resolution: Done
Fix Version/s: 3.7.0
> Add Common Log support
nitoring.
> I think that the current approach of using fields that the operator
> developer can choose to keep private is good.
>
>
>
> On Tue, Mar 14, 2017 at 11:17 PM, Chinmay Kolhatkar
> wrote:
>
> > Dear Community,
> >
> > While going through the code, I
Dear Community,
While going through the code, I found that the AutoMetrics are retrieved
from operators using java reflection. This adds a lot of processing
overhead.
Hence to improve the performance of containers and stram, I want to suggest
following appraoch:
1. In Node, try to collect the met
[
https://issues.apache.org/jira/browse/APEXMALHAR-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2430.
---
Resolution: Done
Fix Version/s: 3.7.0
> Optimize J
[
https://issues.apache.org/jira/browse/APEXMALHAR-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2429.
---
Resolution: Done
Fix Version/s: 3.7.0
> Ambiguity in passing &
[
https://issues.apache.org/jira/browse/APEXMALHAR-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar closed APEXMALHAR-2437.
-
Resolution: Invalid
> Malhar build - ratcheck fail
Got it... After removing demos folder, its seems to run fine.
On Wed, Mar 8, 2017 at 11:58 AM, Thomas Weise wrote:
> demos -> examples
>
> You probably need to remove the leftover local demo folder with its target
> directories.
>
> Thomas
>
>
> On Tue, Ma
Chinmay Kolhatkar created APEXMALHAR-2437:
-
Summary: Malhar build - ratcheck failing
Key: APEXMALHAR-2437
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2437
Project: Apache Apex Malhar
Hi,
I'm finding malhar build to fail because of rat check failing in demos/
folder.
Moreover, I cannot see demos/ folder in
https://github.com/apache/apex-malhar
I want to confirm whether its in apache repository itself OR its my
environment issue.
Please reply.
Thanks,
Chinmay.
[
https://issues.apache.org/jira/browse/APEXMALHAR-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2417.
---
Resolution: Done
Fix Version/s: 3.7.0
> Add PojoOuterJoin (l
[
https://issues.apache.org/jira/browse/APEXMALHAR-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2413.
---
Resolution: Done
Fix Version/s: 3.7.0
> Improve PojoInnerJ
[
https://issues.apache.org/jira/browse/APEXMALHAR-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2428.
---
Resolution: Done
Fix Version/s: 3.7.0
> CompositeAccumulation
Min());*
> >
> > *//following is the sample how to get the sub-accumulation output*
> >
> > *accumulations.getSubOutput(sumTag, outputValues)*
> >
> > *accumulations.getSubOutput(countTag, outputValues)*
> >
> > *accumulations.getSubO
Thomas,
I agree with you that we need this migration to be done but I have a
different opinion on how to execute this.
I think if we do this in phases as described above, users might end up in
more confusion.
For doing this migration, I think it should follow these steps:
1. Whether for operator
Dear Community,
We have deb package being generated via bigtop builds.
Should we add the package to ppa for easy start for new users?
Thanks,
Chinmay.
Dear Community,
Currently we have accumulations for individual types of accumulations.
But if one wants to do more than one accumulations in a single stage of
Windowed Operator it is not possible.
I want to propose an idea about "CompositeAccumulation" where more than one
accumulation can be conf
Certainly good and convenient for application/operator developers to use.
But could someone include this dependency in apex application project and
use it?
If yes, then I would prefer to keep this outside of Apex in general and let
the user use it for convenience.
-Chinmay.
On Wed, Feb 22, 2017
[
https://issues.apache.org/jira/browse/APEXMALHAR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2414:
-
Assignee: (was: Chinmay Kolhatkar)
> Improve performance
[
https://issues.apache.org/jira/browse/APEXMALHAR-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2413:
-
Assignee: Hitesh Kapoor (was: Chinmay Kolhatkar)
> Impr
[
https://issues.apache.org/jira/browse/APEXMALHAR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar reassigned APEXMALHAR-2414:
-
Assignee: Chinmay Kolhatkar
> Improve performance of PojoInnerJ
Chinmay Kolhatkar created APEXMALHAR-2414:
-
Summary: Improve performance of PojoInnerJoin accum by using
PojoUtils
Key: APEXMALHAR-2414
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2414
Chinmay Kolhatkar created APEXMALHAR-2415:
-
Summary: Enable PojoInnerJoin accum to allow multiple keys for
join purpose
Key: APEXMALHAR-2415
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2415
[
https://issues.apache.org/jira/browse/APEXMALHAR-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXMALHAR-2409:
--
Issue Type: Sub-task (was: Improvement)
Parent: APEXMALHAR-2413
Chinmay Kolhatkar created APEXMALHAR-2413:
-
Summary: Improve PojoInnerJoin Accumulation
Key: APEXMALHAR-2413
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2413
Project: Apache Apex
APEXMALHAR-2409 Created.
I'll create a PR soon.
On Wed, Feb 15, 2017 at 10:31 PM, Chinmay Kolhatkar wrote:
> Thanks guys. I'll create a jira and create a PR for it soon.
>
> Ajay, btw this is not much related to Schema discovery design... This is
> for windowed operator.
Chinmay Kolhatkar created APEXMALHAR-2409:
-
Summary: Improve PojoInnerJoin accumulation to emit a POJO instead
of Map
Key: APEXMALHAR-2409
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2409
I agree with the requirement. But I think the requirement here is superceed
by requirement at
https://lists.apache.org/thread.html/d1e282047399558a4f04aab186c0d986114d353dcaf6d6c76a2a3a35@%3Cdev.apex.apache.org%3E
Having PojoInnerJoin to emit a POJO instead of map overrides this.
I suggest to do
>
> > Yes, it should be emitting a POJO. This POJO can then be further used to
> > join with a third POJO stream, thus behaving like a DB join.
> >
> > It would be best if we can incorporate this into Schema Discovery design.
> >
> >
> > Ajay
> &
Dear Community,
Currently PojoInnerJoin accumulation is accepting 2 POJOs but emitting a
Map.
I think it should be emitting POJO instead of Map.
Please share your thoughts about this.
Thanks,
Chinmay.
[
https://issues.apache.org/jira/browse/APEXMALHAR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2399.
---
Resolution: Fixed
Fix Version/s: 3.7.0
> In PojoInnerJ
data that can be useful by the schema receiver to process the data (for
> instance, a delimiter for CSV record stream).
>
> Thanks,
> Sergey
>
> On 2017-01-25 01:47 (-0800), Chinmay Kolhatkar
> wrote:
> > Thank you all for the feedback.
> >
> > I've created a Jir
Hi Santhosh,
It seems that your YARN does not have enough resources available for
allocating memory for 2 application.
When you kill the first application, the memory is regained by yarn and
then allocated to the second application.
You can try to give more memory to yarn if your system allows RA
[
https://issues.apache.org/jira/browse/APEXCORE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838061#comment-15838061
]
Chinmay Kolhatkar commented on APEXCORE-623:
Design doc:
h
[
https://issues.apache.org/jira/browse/APEXCORE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838050#comment-15838050
]
Chinmay Kolhatkar commented on APEXCORE-623:
Discussion on mailing
nka
>
> On Tue, Jan 17, 2017 at 9:18 PM, Pramod Immaneni
> wrote:
>
> > +1
> >
> > On Mon, Jan 16, 2017 at 1:23 AM, Chinmay Kolhatkar
> > wrote:
> >
> > > Hi All,
> > >
> > > Currently a DAG that is generated by user, if contai
Chinmay Kolhatkar created APEXCORE-623:
--
Summary: Schema propagation support in Apex
Key: APEXCORE-623
URL: https://issues.apache.org/jira/browse/APEXCORE-623
Project: Apache Apex Core
> > On Thu, Jan 19, 2017 at 8:55 PM, Priyanka Gugale <
> priya...@datatorrent.com
> > >
> > wrote:
> >
> > > +1
> > >
> > > On Fri, Jan 20, 2017 at 9:25 AM, Chinmay Kolhatkar <
> > > chin...@datatorrent.com>
> > >
1 - 100 of 272 matches
Mail list logo
