Re: Full-text queries in Thin Client protocol

2019-12-04 Thread Ivan Pavlukhin
Pavel mentioned a thread [1] discussion further development of text queries in Ignite. And currently there is some work in progress. And there is a lot to be improved. As for me, I think that we might think about thin clients support when user demand appear. [1] http://apache-ignite-developers.23

[jira] [Created] (IGNITE-12415) .NET: Thin client does not connect to old server nodes

2019-12-04 Thread Pavel Tupitsyn (Jira)
Pavel Tupitsyn created IGNITE-12415: --- Summary: .NET: Thin client does not connect to old server nodes Key: IGNITE-12415 URL: https://issues.apache.org/jira/browse/IGNITE-12415 Project: Ignite

Re: [DISCUSS] Links to commercial version resources in community wiki

2019-12-04 Thread Maxim Muzafarov
Folks, In general case, 3rd party resource links look for me absolutely normal e.g. we could have some links on Oracle's documentation pages. But let's add a little accuracy. We are talking about links to GridGain documentation pages. For me, it's the same as comments `TODO: please, fix me GG-XXX

Re: [DISCUSS] Links to commercial version resources in community wiki

2019-12-04 Thread Ivan Pavlukhin
Maxim, References to GG tickets have definitely no meaning for community. But references to documentation on the other hand can be very useful, actually it is very similar to references to Wikipedia or aforementioned Oracle resources. ср, 4 дек. 2019 г. в 14:40, Maxim Muzafarov : > > Folks, > > I

Re: [DISCUSS] Links to commercial version resources in community wiki

2019-12-04 Thread Dmitriy Pavlov
I agree that 'TODO: please, fix me GG-X' Should be definitely avoided in the code in all cases. A number of community members don't have access to these tickets. This is the same as linking to GG's private documentation or internal network servers. It doesn't make sense. ср, 4 дек. 2019 г. в

[jira] [Created] (IGNITE-12416) Avoid use deprecated the Ignite.active(boolean) methods in project

2019-12-04 Thread Amelchev Nikita (Jira)
Amelchev Nikita created IGNITE-12416: Summary: Avoid use deprecated the Ignite.active(boolean) methods in project Key: IGNITE-12416 URL: https://issues.apache.org/jira/browse/IGNITE-12416 Project:

Re: [ANNOUNCE] 4 December 2019, the 2.8 RELEASE brach creation

2019-12-04 Thread Maxim Muzafarov
Igniters, 1. The release branch created: ignite-2.8 2. The list of unresolved issues [1] related to the 2.8 release has been cleaned up (only Blocker and Critical issues left). 3. Apache Ignite 2.8 wiki page has been updated [2]. 4. The issue [3] with Corrupted B+ tree exception has been reverted

Re: [ANNOUNCE] 4 December 2019, the 2.8 RELEASE brach creation

2019-12-04 Thread Alexey Zinoviev
Great, many thanks to your job ср, 4 дек. 2019 г., 19:05 Maxim Muzafarov : > Igniters, > > > 1. The release branch created: ignite-2.8 > 2. The list of unresolved issues [1] related to the 2.8 release has > been cleaned up (only Blocker and Critical issues left). > 3. Apache Ignite 2.8 wiki page

Re: Joining node validation failure event.

2019-12-04 Thread Mikhail Petrov
Ivan, Am I right, that current approach to solving this problem looks good for you? Regards, Mikhail. On 03.12.2019 15:12, Ivan Pavlukhin wrote: Mikhail, Yep, I see IgniteNodeValidationResult in new event in PR [1]. Discovery events such as (join/left/failed) are connected with a topology

Re: Getting errors while setup new cluster using existing cluster data

2019-12-04 Thread Gangaiah Gundeboina
Thanks Denis. It's ok to loose delta data(which are writing data to cluster while coping), but want to up the cluster whatever data is valid. Is there any way. I don't have idea about Kafka-like approach, will check. Thanks and Regards, Gangaiah -- Sent from: http://apache-ignite-developers

Re: Joining node validation failure event.

2019-12-04 Thread Ivan Pavlukhin
Mikhail, Yes I am fine with the approach. ср, 4 дек. 2019 г. в 20:30, Mikhail Petrov : > > Ivan, > > Am I right, that current approach to solving this problem looks good for > you? > > Regards, > Mikhail. > > On 03.12.2019 15:12, Ivan Pavlukhin wrote: > > Mikhail, > > > > Yep, I see IgniteNodeVal

Re: Joining node validation failure event.

2019-12-04 Thread Mikhail Petrov
Ivan, Andrey, Nikolay, Thanks for your answers! Igniters, if there are no objections, could anyone take a look at implementation [1] of described above event, please? [1] https://github.com/apache/ignite/pull/7057 Regards, Mikhail. On 04.12.2019 21:54, Ivan Pavlukhin wrote: Mikhail, Yes I

[jira] [Created] (IGNITE-12417) .NET: ASP.NET Core Identity Store

2019-12-04 Thread Pavel Tupitsyn (Jira)
Pavel Tupitsyn created IGNITE-12417: --- Summary: .NET: ASP.NET Core Identity Store Key: IGNITE-12417 URL: https://issues.apache.org/jira/browse/IGNITE-12417 Project: Ignite Issue Type: New Fe

Ignite Evolution Direction: short questionary

2019-12-04 Thread Denis Magda
Folks, There are many ongoing conversations and activities on the list related to Ignite's evolution (modularization, 3.0, full-text search support, etc.). I'm suggesting to ask our broader user community to contribute by sharing short feedback and discuss results in several weeks: https://docs.g

[jira] [Created] (IGNITE-12418) Add documentation for Sql default query timeout

2019-12-04 Thread Saikat Maitra (Jira)
Saikat Maitra created IGNITE-12418: -- Summary: Add documentation for Sql default query timeout Key: IGNITE-12418 URL: https://issues.apache.org/jira/browse/IGNITE-12418 Project: Ignite Issue

Re: [ANNOUNCE] 4 December 2019, the 2.8 RELEASE brach creation

2019-12-04 Thread Николай Ижиков
Thank for the leading release, Maxim. Keep going! > 4 дек. 2019 г., в 20:29, Alexey Zinoviev написал(а): > > Great, many thanks to your job > > ср, 4 дек. 2019 г., 19:05 Maxim Muzafarov : > >> Igniters, >> >> >> 1. The release branch created: ignite-2.8 >> 2. The list of unresolved issues [