[
https://issues.apache.org/jira/browse/IGNITE-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897293#comment-16897293
]
Alexey Kosenchuk commented on IGNITE-12021:
-------------------------------------------
mmm... maybe you need to specify the full java class name when creating your
ComplexObjectType in NodeJs client. See the typeName parameter of the
ComplexObjectType constructor.
But it's hard to help here w/o more details.
Please provide examples of your code (for NodeJs and for Java).
> 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)
