[jira] [Created] (IGNITE-14127) Python Thin: increase default query page size

Igor Sapego created IGNITE-14127: Summary: Python Thin: increase default query page size Key: IGNITE-14127 URL: https://issues.apache.org/jira/browse/IGNITE-14127 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-14126) Annoying warning messages in test logs from cli module

Kirill Gusakov created IGNITE-14126: --- Summary: Annoying warning messages in test logs from cli module Key: IGNITE-14126 URL: https://issues.apache.org/jira/browse/IGNITE-14126 Project: Ignite

[jira] [Created] (IGNITE-14125) GridClusterStateProcessor: Logging at INFO level without checking if INFO level is enabled

Paolo Bazzi created IGNITE-14125: Summary: GridClusterStateProcessor: Logging at INFO level without checking if INFO level is enabled Key: IGNITE-14125 URL: https://issues.apache.org/jira/browse/IGNITE-14125

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Folks, I've prepared the RELEASE_NOTES. Would anyone take a look at the PR [2] [1]? [1] https://issues.apache.org/jira/browse/IGNITE-14069 [2] https://github.com/apache/ignite/pull/8748/files On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov wrote: > > Folks, > > I've prepared first benchmarks com

[jira] [Created] (IGNITE-14124) Fix project's Maven settings

Peter Ivanov created IGNITE-14124: - Summary: Fix project's Maven settings Key: IGNITE-14124 URL: https://issues.apache.org/jira/browse/IGNITE-14124 Project: Ignite Issue Type: Bug Affects

Re: [DISCUSS] Missed (non-suited) tests

Hello! Code mostly looks good, I have added a minor request. I will check how it works and then we may commit. + zaleslaw@gmail.com Can you please check whether the new ML suites make sense? math/distances/DistancesTestSuite.java naivebayes/NaiveBayesTestSuite.java Would we need to add them

[jira] [Created] (IGNITE-14123) Separate unit tests from integration tests

Semyon Danilov created IGNITE-14123: --- Summary: Separate unit tests from integration tests Key: IGNITE-14123 URL: https://issues.apache.org/jira/browse/IGNITE-14123 Project: Ignite Issue Typ

Re: Re[4]: [DISCUSSION] Fail on non-colocated join

Hello! I don't think this is absolutely needed. From my userlist experience I don't get particularly many questions about distributed joins. They are, but it's not a hot topic, which is somewhat surprising to me actually. I would expect more people struggling with them. To tell people about erron

Re[4]: [DISCUSSION] Fail on non-colocated join

I think it`s « absolutely needed » case ) Many people will find erroneous places.   >Hello! > >Many people do read logs, especially developers. You would be amazed how >many people come to discuss even the most benign of warnings. > >I think it violates the Apache Ignite compatibility policy,

Re: Re[2]: [DISCUSSION] Fail on non-colocated join

Hello! Many people do read logs, especially developers. You would be amazed how many people come to discuss even the most benign of warnings. I think it violates the Apache Ignite compatibility policy, where we do not break existing code during a major release. We do not always hold on to that p

[jira] [Created] (IGNITE-14122) Fix NPE in ProgressBarTest

Kirill Gusakov created IGNITE-14122: --- Summary: Fix NPE in ProgressBarTest Key: IGNITE-14122 URL: https://issues.apache.org/jira/browse/IGNITE-14122 Project: Ignite Issue Type: Task

Re[2]: [DISCUSSION] Fail on non-colocated join

  >If it breaks existing working code it may not be done that way.   Who reads the logs ?  Is it violates apache way approach or some existing rules ?   thanks !     >Regards, >-- >Ilya Kasnacheev > > >ср, 3 февр. 2021 г. в 09:05, Zhenya Stanilovsky < arzamas...@mail.ru.invalid >>: > >> >> >>

[jira] [Created] (IGNITE-14121) Implement ability to generate configuration trees from arbitrary sources

Ivan Bessonov created IGNITE-14121: -- Summary: Implement ability to generate configuration trees from arbitrary sources Key: IGNITE-14121 URL: https://issues.apache.org/jira/browse/IGNITE-14121 Projec

Re: [DISCUSSION] Fail on non-colocated join

Hello! I think that we should issue a developer warning with LT.warn. I don't think we should raise an exception. Our code may not have enough information. For example, it is possible that the data is collocated via constraint observed by user, such as, ina table of key (id, affKey) there is join