Zhenya, Dmitriy,
>>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i
>>> have no clue - why,
The reason here is a lack of time to ensure that everything is fine there. The
patch is valuable but not so trivial. Honestly, I find it wrong to merge a
changes I am not sure
Hi Ivan, Denis
Thank you for your feedback, I am looking into the changes needed for this
issue.
I am also looking into these configurations parameters
https://apacheignite.readme.io/v2.2/docs/configuration-parameters to see if
there are similar attributes being used in SqlFieldsQuery and
We have observed a similar problem but have not characterised it well
enough to report on the list yet.
We are using IA .Net 2.7.5.
Sent from my iPhone
> On 17/08/2019, at 1:45 PM, Ilya Kasnacheev wrote:
>
> Hello!
>
> Can we get back to this question? It rears its ugly head again:
>
Hello!
Can we get back to this question? It rears its ugly head again:
https://stackoverflow.com/questions/57513576/apache-ignite-spawns-too-much-threads/57523214
Regards,
--
Ilya Kasnacheev
вс, 23 сент. 2018 г. в 15:20, Pavel Tupitsyn :
> Denis,
>
> Can't say for sure, did not investigate
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,