Re: IEP-90 Ignite 3 Client Lifecycle

Another point: With the current proposal, there is no way for the server to distinguish a broken connection from a normal user-initiated connection close. So in either case we'll wait for some configured timeout before cleaning up session resources. I think this is fine, at least for now. On Thu

restful api get not work，but scan can work

anybody know why restful api scan has data http://127.0.0.1:8080/ignite?cmd=qryscanexe&pageSize=5&cacheName=contact result { "successStatus": 0, "error": null, "sessionToken": null, "response": { "items": [ { "key": { "id": 703896957108224 }, "value": { "mergedId": null, "priority": 0, "identitie

Re: [DISCUSS] Query API for Ignite 3.0

JFYI. we have merged the initial version of SQL public API [1] and are going to implement it in epic [2] and I've created few tickets on this. Andey Gura, Taras Ledkov, Konstantine Orlov would you mind to share your thoughts on implementation part in some IEP? Is there IEP page created on the topi

Re: [DISCUSSION] IEP-88: CLI Tool

Hi Ilya, Thanks for the python usage example. AWS cli does not support interactive mode at all. Google too. Even Google Big query cli [1] executes sql queries without interactive shell. For REPL-first tools like Reql [2], ksqlDB CLI [3], or SnowSQL [4] it is common thing to enter the REPL if

Re: [DISCUSSION] Add additional 3rd party libraries to Ignite 3 Code style and practices

Hi Andrey, Thank you for the valuable arguments. Speaking about micronaut, it is a popular library that provides a lot of build-in features like error handling, auth, IoC, test infrastructure, and many more. The main functionality of micronaut framework is REST, so this library is scanned for