Yes. there are scenarios you can't use simple data types. This relates to not only Ignite.
As Ignite SQL layer is built over key-value storage, there always be some overhead on SQL operations. Key-value API allow you operate with one or more cache entries with known keys. If the keys of entries are unknown then the only way to retrieve entries efficiently is to use some index: either SQL or implement your own custom IndexingSPI, On Wed, Jun 6, 2018 at 3:36 PM, the_palakkaran <jik...@suntecsbs.com> wrote: > But you cannot use simple datatypes all the time in a real scenario, > right? I > mean when you need to get results based on multiple fields/columns [unless > I > form a key or something based on them] > > As per different discussions here in the forum and from some demo stubs, I > understand performance of ignite in the order high to low will be : > > 1. Using Binary Objects direct get > 2. Using normal serialiazable objects > 3. Using Externalizable direct get > 4. Using SQLField query [ queries will always be the one taking most > performance, from my experience] > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov
