> maxConnectionNumber parameter
What's the idea? Follow the Best Effor Affinity logic, but establish up to
N connections?
On Thu, Mar 7, 2019 at 1:23 PM Igor Sapego wrote:
> I can propose two improvements here:
>
> 1. A simple one. Lets introduce maxConnectionNumber parameter
> in ClientConfigu
Dmitriy Govorukhin created IGNITE-11509:
---
Summary: Remove DistributedBaselineConfiguration and replace to
methods on IgniteCluster
Key: IGNITE-11509
URL: https://issues.apache.org/jira/browse/IGNITE-11509
I suggest to make a release from master but at 15 April-1 May to prepare
all release features. It's bad practice to announce release and cut master
in one week. And in future put the approximate date of release for feature
planning.
In ML we are in progress of changing API and it takes 1 month to
Dear Denis, I agree, that mentioned fixes should be accessible for
developers, maybe we could release them as an emergency release 2.7.xxx or
another minor version of 2.7, nor 2.8.
And 2.8 could be planned in next 1-2 months with a lot of cool features
пт, 8 марта 2019 г., 13:29 Alexey Zinovi
Vladimir Ozerov created IGNITE-11510:
Summary: SQL: Rework running queries tests to make them stable to
internal code changes
Key: IGNITE-11510
URL: https://issues.apache.org/jira/browse/IGNITE-11510
Vladimir Ozerov created IGNITE-11511:
Summary: SQL: Possible bug with parameters passing for complex DML
queries
Key: IGNITE-11511
URL: https://issues.apache.org/jira/browse/IGNITE-11511
Project:
Alexand Polyakov created IGNITE-11512:
-
Summary: Add counter left partition for index rebuild in
CacheGroupMetricsMXBean
Key: IGNITE-11512
URL: https://issues.apache.org/jira/browse/IGNITE-11512
P
