Dmitriy Govorukhin created IGNITE-12081:
---
Summary: Page replacement can reload invalid page during checkpoint
Key: IGNITE-12081
URL: https://issues.apache.org/jira/browse/IGNITE-12081
Project:
Hi Ivan,
yes, sure.
If it is cherry-picked without conflicts, just push it.
If it contains conflicts it is better to push to 2.7.6-based branch and
start additional run-all, example
https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562, base:
2.7.6
Sincerely,
Dmitriy Pavlov
Kirill Tkalenko created IGNITE-12080:
Summary: Add extended logging for rebalance
Key: IGNITE-12080
URL: https://issues.apache.org/jira/browse/IGNITE-12080
Project: Ignite
Issue Type:
Hi Igniters,
I also suggest adding newly created critical bug into scope
https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned since
it was discussed before in private communication).
It is not a regression but can cause data corruption, so I'd rather wait
for the fix.
Eduard
Luca created IGNITE-12078:
-
Summary: implement loadCache on CacheJdbcBlobStore
Key: IGNITE-12078
URL: https://issues.apache.org/jira/browse/IGNITE-12078
Project: Ignite
Issue Type: Task
Dmitriy,
I cherry-picked fix for
https://issues.apache.org/jira/browse/IGNITE-12068 to 2.7.6. Bot visa
seems good comparing to 2.7.6 but there are some reported blockers. It
would be great if someone can double-check it. If something is wrong
you may consider a revert.
пт, 16 авг. 2019 г. в
Aleksey Zinoviev created IGNITE-12079:
-
Summary: [ML][Umbrella] Add advanced preprocessing techniques
Key: IGNITE-12079
URL: https://issues.apache.org/jira/browse/IGNITE-12079
Project: Ignite
Hi Igniters,
Yesterday was a planned date of code freeze.
So the scope (related both to features and to bugs) is final, we're
entering to stabilization phase. Nothing can be included into scope besides
blockers approved by the release manager.
Dmitriy,
We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068
Should I cherry-pick it to release branch?
пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>
> Hi Igniters,
>
> Yesterday was a planned date of code freeze.
>
> So the scope (related both to features and to bugs) is