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. On 15 Feb 2017 10:11 p.m., "Amol Kekre" <[email protected]> wrote: > yes it should be POJO > > Thks > Amol > > *Join us at Apex Big Data World-San Jose > <http://www.apexbigdata.com/san-jose.html>, April 4, 2017!* > [image: http://www.apexbigdata.com/san-jose-register.html] > <http://www.apexbigdata.com/san-jose-register.html> > > On Wed, Feb 15, 2017 at 7:34 AM, AJAY GUPTA <[email protected]> wrote: > > > 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 > > > > On Wed, 15 Feb 2017 at 5:30 PM, Chinmay Kolhatkar <[email protected]> > > wrote: > > > > Dear Community, > > > > Currently PojoInnerJoin accumulation is accepting 2 POJOs but emitting a > > Map<String, Object>. > > > > I think it should be emitting POJO instead of Map<String, Object>. > > > > Please share your thoughts about this. > > > > Thanks, > > Chinmay. > > >
