[jira] [Updated] (IGNITE-15100) Ignite spring data - IgniteRepository Annotated Queries with LIKE and named parameter

[ https://issues.apache.org/jira/browse/IGNITE-15100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Egloff updated IGNITE-15100: - Description: When I add a method with annotated @Query to my IgniteRepository interface calss

[jira] [Created] (IGNITE-15100) Ignite spring data - IgniteRepository Annotated Queries with LIKE and named parameter

Mark Egloff created IGNITE-15100: Summary: Ignite spring data - IgniteRepository Annotated Queries with LIKE and named parameter Key: IGNITE-15100 URL: https://issues.apache.org/jira/browse/IGNITE-15100

[jira] [Commented] (IGNITE-15050) Add rename index tree to drop index

[ https://issues.apache.org/jira/browse/IGNITE-15050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378613#comment-17378613 ] Kirill Tkalenko commented on IGNITE-15050: -- [~ibessonov] Please make code review. > Add

[jira] [Created] (IGNITE-15101) Ignite tasks run in a security context other than the initiator's security context

Mikhail Petrov created IGNITE-15101: --- Summary: Ignite tasks run in a security context other than the initiator's security context Key: IGNITE-15101 URL: https://issues.apache.org/jira/browse/IGNITE-15101

[jira] [Resolved] (IGNITE-14958) update SQL error "column is not compatible with index definition" after upgrading to 2.10.0

[ https://issues.apache.org/jira/browse/IGNITE-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Zhu resolved IGNITE-14958. Fix Version/s: 2.10 Resolution: Not A Bug We found this is because we store "Date" type