[ 
https://issues.apache.org/jira/browse/IGNITE-12222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jesus H updated IGNITE-12222:
-----------------------------
    Description: 
I'd like to use Ignite as an in memory database that uses a std::string as a 
key, and a byte buffer as a value (could be char*, std::vector<char>, 
std::vector<int8_t> or something more appropriate).

Ignite C++ lacks sufficient information or functionality to store byte buffers 
as values.

>From the doc, I understand users can specialize BinaryType template to add 
>functionality to an existing byte buffer class, but I believe that being able 
>to store a byte buffer should be something basic that should be part of Ignite.

 

 

  was:
Ignite C++ lacks sufficient information or functionality to store byte buffers 
as values.

>From the doc, I understand users can specialize BInaryType template to add 
>functionality to an existing byte buffer class, but I believe that being able 
>to store a byte buffer should be something basic that should be part of Ignite.

 

 


> Lacking Ignite C++ functionality or examples to store byte arrays
> -----------------------------------------------------------------
>
>                 Key: IGNITE-12222
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12222
>             Project: Ignite
>          Issue Type: Improvement
>         Environment: Ignite 2.7.5
>            Reporter: Jesus H
>            Priority: Major
>
> I'd like to use Ignite as an in memory database that uses a std::string as a 
> key, and a byte buffer as a value (could be char*, std::vector<char>, 
> std::vector<int8_t> or something more appropriate).
> Ignite C++ lacks sufficient information or functionality to store byte 
> buffers as values.
> From the doc, I understand users can specialize BinaryType template to add 
> functionality to an existing byte buffer class, but I believe that being able 
> to store a byte buffer should be something basic that should be part of 
> Ignite.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to