Hi Riyafa, I think that we should be able to avoid the PairConstructor scalar evaluators, as a) the number of pairs should be fixed in the query and b) each pair has 2 arguments. So we should be able to just pass the keys and the values - either interleaving (k1, v1, k2, v2, ..) or in 2 batches (k1, k2, .., v1, v2, ..) - to the ObjectConstructorScalarEvaluator (there should be no "Node" in the class name as objects shouldn't be nodes). And then yes, the ObjectConstructorScalarEvaluator should be the right place to check for duplicates.
Cheers, Till On 1 Jun 2016, at 22:13, Riyafa Abdul Hameed wrote: > Hi, > > When attempting to implement runtime operators for Object implementation, I > have come across the following issues: > > - Should there be a ConstructorScalarEvaluator for PairConstructor? > - Should I be checking if the keys are unique in the > ObjectNodeConstructorScalarEvaluator? > > > Thank you. > > Yours sincerely, > > Riyafa > > > > -- > Riyafa Abdul Hameed > Undergraduate, University of Moratuwa > > Email: [email protected] > Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/> > <http://facebook.com/riyafa.ahf> <http://lk.linkedin.com/in/riyafa> > <http://twitter.com/Riyafa1>
