Hi Alex,
> I'm not going to write any new records or update existing ones for such > tables through Ignite. So I can skip the overrides in CacheStore > implementation, right? (I'm using default implementation at the moment) That's right. https://apacheignite.readme.io/docs/id-generator > Thi may work. Can you point me to the example where Ignite config is in XML > file I don't have any XML example that shows how to create an AtomicSequence bean. I tend to initialize it programmatically in code. Anyway, just create it as a standard bean if it needs to be defined in the XML format. - Denis On Wed, Jul 22, 2020 at 12:46 AM Alex Panchenko <[email protected]> wrote: > Hi Denis, > thanks for your reply > > >>How will you access such records in Ignite? SQL lookups? > Yes, using SQL lookups > > >>The default CacheStore implementation that writes down changes to a > relational database needs to be overridden. > I'm not going to write any new records or update existing ones for such > tables through Ignite. So I can skip the overrides in CacheStore > implementation, right? (I'm using default implementation at the moment) > > >>Obviously, Ignite still requires a primary key and that can be an integer > number incremented by your application: > https://apacheignite.readme.io/docs/id-generator > Thi may work. Can you point me to the example where Ignite config is in XML > file > > Also at the moment I'm using the following workaround. It seems like > working, but I'm still testing it > > "keyType"="com.some.package.KeyValuesTableKey" > > KeyValuesTableKey { > key: UUID > value: String > } > > > Thank you > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
