You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/02 13:34:00 UTC
[jira] [Commented] (IGNITE-8552) Unable to use date as primary key
[ https://issues.apache.org/jira/browse/IGNITE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942815#comment-16942815 ]
Maxim Muzafarov commented on IGNITE-8552:
-----------------------------------------
Folks,
any updates? Does this issue is still actual?
> Unable to use date as primary key
> ---------------------------------
>
> Key: IGNITE-8552
> URL: https://issues.apache.org/jira/browse/IGNITE-8552
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.4
> Reporter: Pavel Vinokurov
> Priority: Blocker
> Fix For: 2.8
>
> Attachments: IGNITE-8552_implemented.patch
>
>
> It' is unable to create cache via ddl:
> create table tab(id date primary key, date_field date);
> Result:
> ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to rollback cache start routine. [cacheName=SQL_PUBLIC_T3]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in the node classpath (use default marshaller to enable binary objects) : SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409
> at org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)