Hello guys,
I propose to cherry-pick to 2.8.1 following bug-fixes too, which are
already in master:
Scan query over an evicted partition can cause node failure (IGNITE-12734
[1])
Java thin client: There were problems with deserialization of some types on
the client-side, these types can't be used
Andrey N. Gura created IGNITE-12908:
---
Summary: Confusding check for presence of SqlViewExporterSpi class
in classpath during initialization
Key: IGNITE-12908
URL:
Andrey N. Gura created IGNITE-12907:
---
Summary: GridSystemViewManager is not thread safe
Key: IGNITE-12907
URL: https://issues.apache.org/jira/browse/IGNITE-12907
Project: Ignite
Issue
Nikolay,
Probably, we should not wait for all blocker issues in minor bug-fix
releases except very special cases. I think we should release all
accumulated bug-fixes `as is` and schedule the next 2.8.2 release.
This will allow as to have shorten minor releases.
On Thu, 16 Apr 2020 at 18:17,
Hello, Igniters.
I’m started to work on this 2.8.1 release [1]
Resolved issues for release(28) - [2]
Unresolved issues for release(30) - [3]
My next step:
1. I want to double-check that all commits for the tickets with the
fixVersion=2.8.1 presented in corresponding release branch.
And
Kirill Tkalenko created IGNITE-12906:
Summary: Add to IgniteWalConverter possibility output only hashes
instead real data
Key: IGNITE-12906
URL: https://issues.apache.org/jira/browse/IGNITE-12906
Johnny Galatikitis created IGNITE-12905:
---
Summary: QueryCursorImpl missing custom spliterator()
implementation
Key: IGNITE-12905
URL: https://issues.apache.org/jira/browse/IGNITE-12905
Project:
Denis Garus created IGNITE-12904:
Summary: ШптшеуЫусгкшен
Key: IGNITE-12904
URL: https://issues.apache.org/jira/browse/IGNITE-12904
Project: Ignite
Issue Type: Improvement
Taras Ledkov created IGNITE-12903:
-
Summary: Fix ML + SQL examples
Key: IGNITE-12903
URL: https://issues.apache.org/jira/browse/IGNITE-12903
Project: Ignite
Issue Type: Task