[
https://issues.apache.org/jira/browse/IGNITE-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897044#comment-16897044
]
Gaurav commented on IGNITE-12021:
---------------------------------
Thanks Alex, It worked like a charm.
Now, i ran into a different issue related Hash code.
How can I implement a hash code while inserting. The other side of application
is in JAVA and they have custom logic of hash code.
Whenever I query the cache(Key is complex object) it gives me NULL.
When I insert from Node.JS, Java cannot read using cache.get()
Upon debugging I found its related to hash code.
Can you help on this topic.
Gaurav
> Inserting date from Node.JS to a cache which has Java.SQL.Timestamp
> -------------------------------------------------------------------
>
> Key: IGNITE-12021
> URL: https://issues.apache.org/jira/browse/IGNITE-12021
> Project: Ignite
> Issue Type: Bug
> Components: cache, thin client
> Affects Versions: 2.7
> Environment: We are in DEV right now. can't proceed to higher
> environment with this show stopper
> Reporter: Gaurav
> Priority: Blocker
> Labels: Node.JS, ignite,
>
> I have cache which has one field with type java.sql.Timestamp
>
> From, Node.JS i am inserting it as new Date().
> If the cache is empty the inserts are successful. Issue come when java
> inserted few records in this cache (Java inserts java.sql.Timestamp) . Now ,
> if I run Node.JS program which tries to insert it gives me this error.
>
> Binary type has different field types [typeName=XYZCacheName,
> fieldName=updateTime, fieldTypeName1=Timestamp, fieldTypeName2=Date]
>
> Please help, its stopped my work totally!
>
> P.S : JavaScript new Date() is itself a Timestamp, so cache should ideally
> accept it as Timestamp and not Date.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
