[jira] [Commented] (IGNITE-7728) Put together a doc that shows how to blend SQL with k/v APIs

["Denis Magda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639212#comment-16639212 ] 

Denis Magda commented on IGNITE-7728:
-------------------------------------

[~Artem Budnikov], thanks for the documentation. I reviewed it and made minor changes:
* renamed to SQL and Key-Value Usage
* removed the requirement of having the PRIVATE deployment mode. It was never required. We always use the default mode and the peer-class-loading works fine. Send a message to the dev list if the issue persists, it sounds like a bug on your side.

[~pgarg], please do a final review.

> Put together a doc that shows how to blend SQL with k/v APIs
> ------------------------------------------------------------
>
>                 Key: IGNITE-7728
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7728
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>            Priority: Blocker
>             Fix For: 2.7
>
>
> More and more people start blending SQL with key-value APIs in Ignite. Usually, they create tables/caches with DDL and wish to use key-value later as well:
> [https://stackoverflow.com/questions/48795533/how-do-i-read-data-from-cache-using-javaapi-after-i-put-it-through-jdbc]
> https://stackoverflow.com/questions/49834964/mixing-apache-ignite-binaryobject-with-sql-tables/49864396#49864396
>  
> We already have a project that demonstrates this approach:
> [https://github.com/dmagda/ignite_world_demo]
>  
> Put together a doc that points out to it and elaborates on this topic. The doc needs to explain how tables are mapped to the caches, columns to types as discussed here: http://apache-ignite-developers.2346864.n4.nabble.com/write-through-when-using-SQL-updates-td29767.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)