There is our DDL documentation, which describes in detail how one can create indexes on existing table [1]. It can be used with both C++ using SqlFieldsQuery and ODBC.
Now regarding benefits of ODBC over C++ - there are definitely memory benefits if you are comparing ODBC and thick C++ client as thick client starts JVM internally. On the other hand if you compare thin C++ client and ODBC then I don't think there are any significant differences in performance or memory consumption. Using C++ you are getting a more convenient API (e.g. cache API, transactions API) and ability to work with objects. Also when you use cache operations in C++ thin client it may be faster than inserting a value with ODBC as C++ thin client is affinity aware and in many cases will send request to primary node, which is not true for ODBC. There are many other small or not so small differences between those 3 options, but this is just too much of an information to describe it all in a single email. So just ask if you are interested in something particular and we'll try to answer. [1] - https://ignite.apache.org/docs/latest/sql-reference/ddl#create-index Best Regards, Igor On Tue, Mar 16, 2021 at 2:30 PM rakshita04 <[email protected]> wrote: > Hi team, > > I believe the example you mentioned above is using C++ - > > https://github.com/apache/ignite/blob/f37ec9eece4db627f2d5190e589f0522e445a251/modules/platforms/cpp/examples/query-example/src/query_example.cpp > > is there any performance or memory benefit is we use odbc rather than C++ > API? > We are using C++ put/get APIs to write/read data on cache. > Is it okay to use C++ APIs to perform sql query, similar way? or using odbc > client is more beneficial? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
