Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Sergey, Thank you. I also do not support @IgniteExperemental annotation only for solving the current case of compatibility issues. I like your second suggestion to revert the issue [2] from 2.8 release by applying [1] PR. I'm going to apply this patch [1] within the next three days. Any

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Igniters, The list of the 2.8 release BLOCKERs at this moment: [1] Default auto-adjust baseline enabled flag calculated incorrectly [Anton Kalashnikov] PATCH AVAILABLE [2] (Amazon S3 Based Discovery) Nodes getting down *[Unassigned] *OPEN [3] Cluster Data Store grid gets Corrupted for Load

[jira] [Created] (IGNITE-12529) Getting local ignite instance inside ComputeJob#cancel

Denis Garus created IGNITE-12529: Summary: Getting local ignite instance inside ComputeJob#cancel Key: IGNITE-12529 URL: https://issues.apache.org/jira/browse/IGNITE-12529 Project: Ignite

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Igniters, I got green TC Bit visas [1] [2] for patch and commit revert. [1] https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAllNightly=ignite-2.8=pull%2F7238%2Fhead=Latest [2]

[jira] [Created] (IGNITE-12532) .NET: Recognize fields with KeyAttribute and set QueryEntity.KeyFieldName

Pavel Tupitsyn created IGNITE-12532: --- Summary: .NET: Recognize fields with KeyAttribute and set QueryEntity.KeyFieldName Key: IGNITE-12532 URL: https://issues.apache.org/jira/browse/IGNITE-12532

Re: IGNITE-12361 Migrate Flume module to ignite-extensions

Alex Goncharuk, Nikolay Izhikov, Could you possibly check the changes or suggest any other committer/contributor for that? - Denis On Sun, Jan 12, 2020 at 9:31 AM Saikat Maitra wrote: > Hello, > > These PRs are part of Modularization effort > >

Re: Hint for user that baseline topology should be changed in order to trigger rebalance

Stan, I would not suggest us adding any links to docs as long as the message needs to be self-explanatory. If someone doesn't get it then they should google. Taking your feedback into consideration: "New server node joined the cluster, add it to the baseline topology to store data there

JAVADOC fails on local build. Should it be checked on TC?

Igniters, I've run locally maven command according to DEVNOTES: mvn initialize -Pjavadoc and it fails due to: 'Other Packages' section should not be present, all packages should have corresponding documentation groups. The reason of that is a newly added `org.apache.ignite.springdata22`

Re: Hint for user that baseline topology should be changed in order to trigger rebalance

We already have a ticket for this open BTW: https://issues.apache.org/jira/browse/IGNITE-8115 . I would also avoid saying anything about rebalancing - at this point the user may not know what it is. This message is very clearly targeted at new

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Igniters, Seems like we have another blocker for 2.8 [1]. Impact: after migration of persistent cluster from 2.7- to 2.8 any updates of baseline topology are not persisted. [1]: https://issues.apache.org/jira/browse/IGNITE-12531 On Mon, Jan 13, 2020 at 6:14 PM Sergey Antonov wrote: >

[jira] [Created] (IGNITE-12531) Cluster is unable to change BLT on 2.8 if storage was initially created on 2.7 or less

Ivan Rakov created IGNITE-12531: --- Summary: Cluster is unable to change BLT on 2.8 if storage was initially created on 2.7 or less Key: IGNITE-12531 URL: https://issues.apache.org/jira/browse/IGNITE-12531

[jira] [Created] (IGNITE-12528) JAVADOC build fails when appropriate profile is enabled

Maxim Muzafarov created IGNITE-12528: Summary: JAVADOC build fails when appropriate profile is enabled Key: IGNITE-12528 URL: https://issues.apache.org/jira/browse/IGNITE-12528 Project: Ignite

[jira] [Created] (IGNITE-12530) Pages list caching can cause IgniteOOME when checkpoint is triggered by "too many dirty pages" reason

Aleksey Plekhanov created IGNITE-12530: -- Summary: Pages list caching can cause IgniteOOME when checkpoint is triggered by "too many dirty pages" reason Key: IGNITE-12530 URL:

Re: Please a reviewer for the case IGNITE-12518

Hi Saikat, I add information for evidence for the changes of ignite rest-http module. 1. Can you please share more information on the issue that will be resolved with this change? R: This change add the possibility for publish war files with webpages in JSF or webservices JaxWS inside of the