Hi Vivek,
Did you end up fixing the issue? If so, would you like to contribute the
fix back to Apex?
Thanks,
Thomas
On Fri, Mar 23, 2018 at 11:05 AM, Vivek Bhide
wrote:
> Hi Vlad,
>
> I have filed a JIRA https://issues.apache.org/jira/browse/APEXMALHAR-2557
>
> but I am not sure about all the
Hi Vlad,
I have filed a JIRA https://issues.apache.org/jira/browse/APEXMALHAR-2557
but I am not sure about all the attributes like component or epic or Label.
Please update the ticket with correct values or let me know and I will add
that
Regards
Vivek
--
Sent from: http://apache-apex-users-l
IMO, it is a regression introduced in 3.8.0, not a
configuration/infrastructure or a NULL key issue. File a JIRA.
Thank you,
Vlad
On 3/23/18 10:07, Vivek Bhide wrote:
Hi Vlad,
Yes, its 3.8.0
Regards
Vivek
--
Sent from: http://apache-apex-users-list.78494.x6.nabble.com/
Hi Bhupesh,
Please find the details below
Dedup operator configuration :
dt.application.KafkaDedupOutputOperatorTest.operator.dedupeOperator.prop.keyExpression
{$.id} + {$.name}
dt.application.KafkaDedupOutputOperatorTest.opera
Hi Vlad,
Yes, its 3.8.0
Regards
Vivek
--
Sent from: http://apache-apex-users-list.78494.x6.nabble.com/
Most likely the NPE is caused by a bug (regression introduced by
APEXMALHAR-2492 Correct usage of empty Slice in Malhar Library). What is
operator library version (3.8.0)?
Thank you,
Vlad
On 3/23/18 05:48, Bhupesh Chawda wrote:
Hi Vivek,
Can you send across few more details, like the config
Hi Vivek,
Can you send across few more details, like the configuration of the
operator and some sample data?
Also do confirm if the key could have been null?
~ Bhupesh
___
Bhupesh Chawda
E: bhup...@datatorrent.com | Twitter: @bhupeshsc
www.
