[jira] [Created] (IGNITE-12884) Extend debug output for restorePartitionStates method.

Stanilovsky Evgeny created IGNITE-12884: --- Summary: Extend debug output for restorePartitionStates method. Key: IGNITE-12884 URL: https://issues.apache.org/jira/browse/IGNITE-12884 Project: Ignite

Re: [jira] [Created] (IGNITE-12852) Comma in field is not supported by COPY command

Hello, Apologies for missing the thread, I am already working on this issue under the scope of the closed ticket, which I have missed to notify about: https://issues.apache.org/jira/browse/IGNITE-7537. I have already fixed the parsing of quotes/field delimiters but there is a bit more to implemen

[jira] [Created] (IGNITE-12885) Checkpoint thread executes partitions fsync in single thread

Ivan Bessonov created IGNITE-12885: -- Summary: Checkpoint thread executes partitions fsync in single thread Key: IGNITE-12885 URL: https://issues.apache.org/jira/browse/IGNITE-12885 Project: Ignite

[jira] [Created] (IGNITE-12886) Introduce separate SQL configuration

Taras Ledkov created IGNITE-12886: - Summary: Introduce separate SQL configuration Key: IGNITE-12886 URL: https://issues.apache.org/jira/browse/IGNITE-12886 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-12887) Node stops on type mismatch error between index type and type of value from searched row

Taras Ledkov created IGNITE-12887: - Summary: Node stops on type mismatch error between index type and type of value from searched row Key: IGNITE-12887 URL: https://issues.apache.org/jira/browse/IGNITE-12887

Re: [DISCUSSION] Major changes in Ignite in 2020

Hi everyone! Major changes that are going to be contributed from our side: - https://issues.apache.org/jira/browse/IGNITE-11704 - keeping tombstones for removed entries to make rebalance consistent (this problem is solved by on-heap deferred deletes queue so far). - https://issues.apache.org/jira/

Re: [jira] [Created] (IGNITE-12852) Comma in field is not supported by COPY command

Hi Anton, I have paid attention to the issue of IGNITE-7537, because it is now closed and there is no task assignment, so I created a new ticket. This issue brings a lot of trouble to data migration, many original fields are separated by commas. If it is only to solve the problem of comma se

Re: [DISCUSSION] Major changes in Ignite in 2020

Hi Igniters! Major changes that are going to be contributed from our side for IGNITE SQL: - Local runtime statistics which helps to estimate query execution plan. It should help use right join order in most cases. Seems could be done by Q3. - most efforts will be direct to new SQL eng

Re: [DISCUSSION] Major changes in Ignite in 2020

My company is initiating major project using Golang, Ignite and need native Golang client support. What is the status of support for Golang? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: [DISCUSSION] Major changes in Ignite in 2020

My plan includes: * Cluster API for C++ thick client * Moving Python, Node.js and PHP thin clients in separate repositories and separate release cycles. * Partition Awareness for Python and Node.js thin clients * SQL for C++ thin client. Steven, There are some third-party golang clients AFAIK, fo

Re: [DISCUSSION] Major changes in Ignite in 2020

Folks, Thanks to everyone responded. @Alexey Zinoviev , @Alexey Scherbakov , @Nikolay Izhikov , @Maxim Muzafarov , @Anton Vinogradov , @Andrey Gura could you guys please also join this thread and share your intentions for this year? What I want to do next, once the majority responds, is to cre

Re: [DISCUSSION] Major changes in Ignite in 2020

Hi, Denis, currently I'm working on roadmap, will publish during this month. Need a time to estimate different things. Will join later and update the wiki pages suggested earlier. пт, 10 апр. 2020 г. в 18:38, Denis Magda : > Folks, > > Thanks to everyone responded. > > @Alexey Zinoviev , @Alexey

Re: [DISCUSSION] Major changes in Ignite in 2020

First thanks for your quick response. I looked at https://github.com/amsokol/ignite-go-client and its NOT completed and nothing has been for last 16 months. Initial test with package failed, so trying to determine your project roadmap with regards to Golang and maybe Rust support. I'm NOT sure

Re: [DISCUSSION] Major changes in Ignite in 2020

Steven, Please start a dedicated discussion for the Golang support. At the moment, I'm not aware if anybody from the community planned to provide support out-of-the-box. However, that's not a tricky task thanks to Ignite's binary protocol that lets enable any programming language support easily.

Re: [DISCUSSION] Hot cache backup

Maxim, Thanks for raising this PR. I will do a review during next week. --AG

Re: Tibco BW 6 plug-in for Apache Ignite

Hi Angel, Thanks for sharing your plugin with the community! It's highly likely that there some folks on the user list who will be glad to know the plugin is available. We also supported you by sharing the integration via Ignite twitter handle: https://twitter.com/ApacheIgnite/status/124866356404

Re: Change Ignite download.cgi page to satisfy requirements

Denis, Petr If I'll prepare pgp and sha512 for this Google Compute Image file [1] is there any official repository where we can store these files to use them? Can we upload them to the storage.googleapis.com/ignite-media site? [1] https://storage.googleapis.com/ignite-media/ignite-google-image.ta