Re: Best Effort Affinity for thin clients

Igor, I think that "Cache Partitions Request" should contain affinity topology version. Otherwise we do not know what distribution is returned - the one we expected, or some newer one. The latter may happen in case topology changed or late affinity assignment happened between server response and s

Hello everyone

Hello Ignite Community! This is prehistoricpenguin. I want to contribute to Apache Ignite, I am a senior c++ server engineer, and I also write some Java, Node, and Python, my JIRA username is "prehistoricpenguin". Thanks!

Hello Ignite Community

Hello Ignite Community! My name is Manu. I want to contribute to Apache Ignite. My JIRA username mnusan. Any help on this will be appreciated. Thanks! -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: proposed realization KILL QUERY command

Hi Yuriy, I think all proposed approaches might work. The question is what is the most convenient from user perspective. Encoded values without special characters are good because they are easy to copy with mouse (double-click) or keyboard (Ctrl+Shift+arrow). On the other hand, ability to identify

[jira] [Created] (IGNITE-10938) After restart cluster with non-blt nodes - they left by handler

ARomantsov created IGNITE-10938: --- Summary: After restart cluster with non-blt nodes - they left by handler Key: IGNITE-10938 URL: https://issues.apache.org/jira/browse/IGNITE-10938 Project: Ignite

Re: How to update Documentation 2.8 docs? - IGNITE-8532 [ML] GA Grid - Implement Roulette Wheel Selection

Hi Turik, 2.8 is not released, and dates were not discussed yet. So it is hard to say when a doc package will be available. Sincerely, Dmitriy Pavlov пн, 14 янв. 2019 г. в 14:18, techbysample : > Igniters, > > Would you please advise on when 2.8 documentation will be available? > > I need to m

[jira] [Created] (IGNITE-10939) SQL: UPDATE of second level fields fails if parent field was set to null previously

Pavel Kuznetsov created IGNITE-10939: Summary: SQL: UPDATE of second level fields fails if parent field was set to null previously Key: IGNITE-10939 URL: https://issues.apache.org/jira/browse/IGNITE-10939

[jira] [Created] (IGNITE-10940) Supply pre-built ./configure with Apache Ignite releases

Ilya Kasnacheev created IGNITE-10940: Summary: Supply pre-built ./configure with Apache Ignite releases Key: IGNITE-10940 URL: https://issues.apache.org/jira/browse/IGNITE-10940 Project: Ignite

Re: proposed realization KILL QUERY command

Thanks Vladimir for your thoughts. Based on it most convenient ways are first and third. But with some modifications: For first variant delimiter should be a letter, e.g. 123X15494, then it could be simple copy by user. For 3rd variant can be used convert both numeric to HEX and use a letter delim

[jira] [Created] (IGNITE-10941) Ignite won't build with Java 11

Andrey Kalinin created IGNITE-10941: --- Summary: Ignite won't build with Java 11 Key: IGNITE-10941 URL: https://issues.apache.org/jira/browse/IGNITE-10941 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-10942) [TC Bot] Optimize backround JIRA tickets sync

Dmitriy Pavlov created IGNITE-10942: --- Summary: [TC Bot] Optimize backround JIRA tickets sync Key: IGNITE-10942 URL: https://issues.apache.org/jira/browse/IGNITE-10942 Project: Ignite Issue

[jira] [Created] (IGNITE-10943) "No next node in topology" infinite messages in log after cycle cluster nodes restart

Dmitry Sherstobitov created IGNITE-10943: Summary: "No next node in topology" infinite messages in log after cycle cluster nodes restart Key: IGNITE-10943 URL: https://issues.apache.org/jira/browse/IGNITE-

[jira] [Created] (IGNITE-10944) Plugin discovery data from PluginProvider.provideDiscoveryData should be available in PluginProvider.validateNewNode

Andrey Aleksandrov created IGNITE-10944: --- Summary: Plugin discovery data from PluginProvider.provideDiscoveryData should be available in PluginProvider.validateNewNode Key: IGNITE-10944 URL: https://issues.

Re: Best Effort Affinity for thin clients

Pavel, This will require from client to send this new request periodically, I'm not sure this will make clients simpler. Anyway, let's discuss it. Vladimir, With current proposal, we will have affinity info in message header. Best Regards, Igor On Tue, Jan 15, 2019 at 11:01 AM Vladimir Ozerov

[jira] [Created] (IGNITE-10945) Document Baseline auto-adjust feature

Ivan Bessonov created IGNITE-10945: -- Summary: Document Baseline auto-adjust feature Key: IGNITE-10945 URL: https://issues.apache.org/jira/browse/IGNITE-10945 Project: Ignite Issue Type: Task

SQL views for IO statistics

Hi Igniters! As part of IEP-27 we already gathering IO statistics and expose it through JMX. User who use only SQL should have access to the statistics also. So let's discuss about how such SQL view should looks.

[jira] [Created] (IGNITE-10946) --excludeCaches do not fit unified argument naming format

Max Shonichev created IGNITE-10946: -- Summary: --excludeCaches do not fit unified argument naming format Key: IGNITE-10946 URL: https://issues.apache.org/jira/browse/IGNITE-10946 Project: Ignite

[jira] [Created] (IGNITE-10947) CPP: Fix documentation on how to build Ignite C++ on Linux

Igor Sapego created IGNITE-10947: Summary: CPP: Fix documentation on how to build Ignite C++ on Linux Key: IGNITE-10947 URL: https://issues.apache.org/jira/browse/IGNITE-10947 Project: Ignite

[ANNOUNCE] Apache Roadshow Chicago, Call for Presentations

Hello Devs! You're receiving this email because you are subscribed to one or more Apache developer email lists. I’m writing to let you know about an exciting event coming to the Chicago area: The Apache Roadshow Chicago. It will be held May 13th and 14th at three bars in the Logan Square neighb

Re: Apache Ignite Codebase has been migrated to GitBox

Hello, Igniters. Please, note, Github merges without squashing by default. Use "squash and merge" option in drop down list. ср, 9 янв. 2019 г. в 14:25, Anton Vinogradov : > Seems, the next step is to integrate tcbot with github. > It will be nice to have an opportunity to ask the bot to check P

Re: proposed realization KILL QUERY command

Hi, Concatenation through a letter looks like a good approach to me. As far as killing all queries on a specific node, I would put it aside for now - this looks like a separate command with possibly different parameters. On Tue, Jan 15, 2019 at 1:30 PM Юрий wrote: > Thanks Vladimir for your tho

Re: [MTCGA]: new failures in builds [2732834] needs to be handled

The fix was merged to master. Related tests were unmuted. On Thu, Jan 10, 2019 at 7:03 PM Vyacheslav Daradur wrote: > > Looks like the test "ServicesTest.TestGetServiceProxy(False)" became > flaky after IGNITE-9607. > > I muted the test on TC and filled Jira issue assigned to myself: > https://is

[jira] [Created] (IGNITE-10948) Ignition.Stop() methods (named, all, etc.) fail to Stop cluster nodes

Glenn Wiebe created IGNITE-10948: Summary: Ignition.Stop() methods (named, all, etc.) fail to Stop cluster nodes Key: IGNITE-10948 URL: https://issues.apache.org/jira/browse/IGNITE-10948 Project: Igni

[jira] [Created] (IGNITE-10949) org.apache.ignite.internal.MarshallerContextImpl.CombinedMap generates NPE

Alexand Polyakov created IGNITE-10949: - Summary: org.apache.ignite.internal.MarshallerContextImpl.CombinedMap generates NPE Key: IGNITE-10949 URL: https://issues.apache.org/jira/browse/IGNITE-10949

Re: proposed realization KILL QUERY command

Denis and other Igniters, do you have any comments for proposed approach? Which of these ones will be better to use for us - simple numeric or hex values (shorter id, but with letters)? As for me hex values preferable due to it shorter and looks more unique across a logs вт, 15 янв. 2019 г. в

Re: Hello everyone

Hello, Welcome to the community! Added you to the contributors' list in JIRA. Feel free to take over tickets of your interest. Just in case, Igor Sapego can help you to pick good starting C++ tasks. - Denis On Tue, Jan 15, 2019 at 12:12 AM 泰然 wrote: > Hello Ignite Community! > > > This is pr

Re: Hello Ignite Community

Hello Manu and welcome to the community! I've added you to the contributors' list in JIRA. Feel free to pick a ticket of your choice. In general, try to start playing with Ignite examples and checking our technical docs. Also, get to know out Dev Process page: https://cwiki.apache.org/confluence/

Re: proposed realization KILL QUERY command

Yury, Please give me a couple of days to read through the thread and respond. Pretty busy these days, bare with me. - Denis On Tue, Jan 15, 2019 at 8:00 AM Юрий wrote: > Denis and other Igniters, do you have any comments for proposed approach? > Which of these ones will be better to use for u

Re: Apache Ignite Codebase has been migrated to GitBox

GitHub has an option to disable non-squash commit in the repo settings. Can we use that? [image: image.png] On Tue, Jan 15, 2019 at 6:30 PM Nikolay Izhikov wrote: > Hello, Igniters. > > Please, note, Github merges without squashing by default. > Use "squash and merge" option in drop down list.

Re: Best Effort Affinity for thin clients

Igor, > It is proposed to add flag to every response, that shows whether the Affinity Topology Version of the cluster has changed since the last request from the client. I propose to keep this flag. So no need for periodic checks. Makes sense? On Tue, Jan 15, 2019 at 4:45 PM Igor Sapego wrote:

[jira] [Created] (IGNITE-10950) Lost backup entries when using spring data and cache store

Roman Guseinov created IGNITE-10950: --- Summary: Lost backup entries when using spring data and cache store Key: IGNITE-10950 URL: https://issues.apache.org/jira/browse/IGNITE-10950 Project: Ignite

[jira] [Created] (IGNITE-10951) migration from Junit 3 to 4 phase 2 (follow-up to IGNITE-10173)

Oleg Ignatenko created IGNITE-10951: --- Summary: migration from Junit 3 to 4 phase 2 (follow-up to IGNITE-10173) Key: IGNITE-10951 URL: https://issues.apache.org/jira/browse/IGNITE-10951 Project: Igni