Given link has all the details needed. You either write your db queries in custom cache store or move them to a separate db DAO class and have it's instance in cache store. Then it will be similar to how you connect your app to DB. Next you need to have these custom classes in ignite class path and it should work. I have tried this with Java app and Oracle.
On Fri, 24 Feb 2023, 19:16 satyajit.mandal.barclays.com via user, < [email protected]> wrote: > Hi Team, > > > > We are using .NET Api for accessing Ignite cache. We want to > understand how can we implement the custom cache store and extend > it to save data in MongoDB from Ignite. Can someone share detail > steps how to extend the cachestore and how it will integrate with > Ignite libraries? We are referring this documentation > https://ignite.apache.org/docs/latest/persistence/custom-cache-store > but it does not mentions what to do after we have written custom > cache store and what are the next steps? > > > > Thanks > > Satyajit > > > > > > Barclays Execution Services Limited registered in England. Registered No. > 1767980. Registered office: 1 Churchill Place, London, E14 5HP > > Barclays Execution Services Limited provides support and administrative > services across Barclays group. Barclays Execution Services Limited is an > appointed representative of Barclays Bank UK plc, Barclays Bank plc and > Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays > Bank plc are authorised by the Prudential Regulation Authority and > regulated by the Financial Conduct Authority and the Prudential Regulation > Authority. Clydesdale Financial Services Limited is authorised and > regulated by the Financial Conduct Authority. > > This email and any attachments are confidential and intended solely for > the addressee and may also be privileged or exempt from disclosure under > applicable law. If you are not the addressee, or have received this email > in error, please notify the sender and immediately delete it and any > attachments from your system. Do not copy, use, disclose or otherwise act > on any part of this email or its attachments. > > Internet communications are not guaranteed to be secure or virus-free. The > Barclays group does not accept responsibility for any loss arising from > unauthorised access to, or interference with, any internet communications > by any third party, or from the transmission of any viruses. Replies to > this email may be monitored by the Barclays group for operational or > business reasons. > > Any opinion or other information in this email or its attachments that > does not relate to the business of the Barclays group is personal to the > sender and is not given or endorsed by the Barclays group. > > Unless specifically indicated, this e-mail is not an offer to buy or sell > or a solicitation to buy or sell any securities, investment products or > other financial product or service, an official confirmation of any > transaction, or an official statement of Barclays. >
