IGNITE-15266 Add isclass check to is_hinted#48
IGNITE-15266 Add isclass check to is_hinted#48bojidar-bg wants to merge 1 commit intoapache:masterfrom
Conversation
|
@bojidar-bg Great catch, Bojidar. Could you please add a test case for it? I've really appreciate your effort and create some tests for your case, please add tests to your patch. Also, we have already imported Also I'd suggest not to use OBJECT_ARRAY at all, Ignite itself doesn't have a great support of it. Use Collections (simple list) instead. |
Co-authored-by: Ivan Daschinsky <ivandasch@apache.org>
29f5478 to
df33e7e
Compare
|
Ah, good spot, didn't notice it was already imported! Thanks for the patch, just went ahead and used it ☺ |
|
@bojidar-bg Great, I'll merge a fix today. I cannot give your a promise to release 0.5.2 as ASAP, unfortunatelly. But let's wait for a while, may be others bugs appears, so we can ship a new bugfix release. |
Signed-off-by: Ivan Daschinsky <ivandasch@apache.org>
Signed-off-by: Ivan Daschinsky <ivandasch@apache.org> (cherry picked from commit fa364df)
The issue seems to be caused by
issubclassrequiring its first parameter to be a class, which isn't the case for two-element tuples like the ones used by e.g. object arrays for hinting the object array type ((-1, [...])). Hence, an obvious patch would be to just double check that we are using it with a class.Performance impact:
Doesn't seem to impactful to me, we can do a million of those in a millisecond.