I hope there is no data loss here, but index tree corruption can be easily
obtained.
Impact: someone believe that inline_size has been changed due to index
recreation but that`s not so.
Hi Evgeniy,
I can't review this change. We need approve of a committer, who is SQL
expert, here.
What
Hi Evgeniy,
I can't review this change. We need approve of a committer, who is SQL
expert, here.
What would be an impact on users if we don' include it into 2.7.6?
Is it a critical/data loss issue? If not, I agree it can wait for 2.8
release.
Sincerely,
Dmitriy Pavlov
сб, 17 авг. 2019 г. в
hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i
have no clue - why, but seems i can`t merge it without his visa.
thanks.
Hi Igniters,
I also suggest adding newly created critical bug into scope
https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
Hi Ivan,
Thank you so much, Ivan, for contributing this fix after hours.
We have second barrier here - 2.7.6 related to 2.7.5,
https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.5
I've triggered one more run for RunAll here.
Sincerely,
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 г. в
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
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
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
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, review passed, plz proceed.
thanks !
I removed https://issues.apache.org/jira/browse/IGNITE-12032 until
nobody
volunteer to complete the task.
Evgeniy, please keep me updated about IGNITE-12061.
чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
:
yep, i`l try to call someone
Sorry, it was too easy to do, no need to ask Maxim.
Cherry-picked to 2.7.6,
https://github.com/apache/ignite/commit/891e49fe1eeb28bc6b655024086c3f4d1324fda4
чт, 15 авг. 2019 г. в 19:02, Dmitriy Pavlov :
> Hi Ilya,
>
> I bypassed this problem in the Tc bot by
> "triggerBuild": true,
>
Hi Ilya,
I bypassed this problem in the Tc bot by
"triggerBuild": true,
"triggerBuildQuietPeriod": 480, //triggering quiet period in minutes, 2
builds per day
"triggerParameters": [
{
"name": "reverse.dep.*.IGNITE_LOGGING_OPTS",
"value": "-DIGNITE_QUIET=false"
}
]
But if is test
Hello!
I suggest also including IGNITE-11736, otherwise we are going to run into
problems each time TC is invoked.
https://issues.apache.org/jira/browse/IGNITE-11736
Regards,
--
Ilya Kasnacheev
чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky :
> yep, i`l try to call someone who probably
I removed https://issues.apache.org/jira/browse/IGNITE-12032 until nobody
volunteer to complete the task.
Evgeniy, please keep me updated about IGNITE-12061.
чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky :
> yep, i`l try to call someone who probably familiar with this problem.
>
> >
> >
>
14 matches
Mail list logo
