[MTCGA]: new failures in builds [6551542] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master GridCommandHandlerWithSSLTest.testCacheIdleVerifyChecksGapsAtomic https://ci2.ignite.apache.org/test/6961701646225931?currentProjectId=IgniteTests24Java8=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 04:53:23 09-08-2022
[MTCGA]: new failures in builds [6551324] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master StatisticsConfigurationTest.updateStatisticsOnChangeTopology[persist=true] https://ci2.ignite.apache.org/test/2355900617476832260?currentProjectId=IgniteTests24Java8=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 22:23:20 08-08-2022
Re: Apache Ignite 2.14 RELEASE [Time, Scope, Manager]
+1 from my side. Count on my support if somethings need to be done from PMC
This link works for me (without pre-selected issue in URL JIRA displays
more predictable results):
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.14%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
and one more filter with open issues
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.14'))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20not%20in%20('CLOSED'%2C%20'RESOLVED')%20ORDER%20BY%20priority
There are only 40, for now.
пн, 8 авг. 2022 г. в 16:01, Taras Ledkov :
> Dear Ignite Community!
>
> I suggest starting Apache Ignite 2.14 release activities.
>
> We've accumulated a hundred resolved [1] issues with new
> features and bug fixes which are waiting for their release date. For
> example,
> - bunch of Calcite based SQL engine fixes and improvements;
> - thin clients improvements;
> - fixes at the core: update counters, binary meta, etc.
>
> I want to propose myself to be the release manager of the planning release.
>
> I propose the following timeline:
>
> Scope Freeze: August 17, 2022
> Code Freeze: August 24, 2022
> Voting Date: September 7, 2022
> Release Date: September 14, 2022
>
> [1].
> https://issues.apache.org/jira/browse/IGNITE-16958?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.14%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
>
> --
> With best regards,
> Taras Ledkov
>
Apache Ignite 2.14 RELEASE [Time, Scope, Manager]
Dear Ignite Community! I suggest starting Apache Ignite 2.14 release activities. We've accumulated a hundred resolved [1] issues with new features and bug fixes which are waiting for their release date. For example, - bunch of Calcite based SQL engine fixes and improvements; - thin clients improvements; - fixes at the core: update counters, binary meta, etc. I want to propose myself to be the release manager of the planning release. I propose the following timeline: Scope Freeze: August 17, 2022 Code Freeze: August 24, 2022 Voting Date: September 7, 2022 Release Date: September 14, 2022 [1]. https://issues.apache.org/jira/browse/IGNITE-16958?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.14%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority -- With best regards, Taras Ledkov
Re: URL parameters in CLI
The main question here is : what is the node URL? How will the user know a port from a wide port range? On Tue, Jul 26, 2022 at 3:01 PM Vadim Pakhnushev wrote: > > Hi Igniters! > After implementing commands for CLI tool listed in the IEP-88 > https://cwiki.apache.org/confluence/display/IGNITE/IEP-88%3A+CLI+Tool some > early users raised a concern about confusion between --node-url and > --cluster-url arguments. > Initially --node-url was intended to be used in commands dealing with the > particular node (i.e. node config show) and --cluster-url for commands > dealing with the cluster as a whole (i.e. cluster config show). > Although cluster URL is basically a URL of any node in the cluster. > So the question for discussion is - would it make sense to unify parameters > to both cluster- and node-related commands to be --node-url? > Or it would be better to keep the distinction?
Re: Questions about SQL transactions
Hi, > 1. Is MVCC the only atomicity mode that supports SQL transactions? Yes, only TRANSACTIONAL_SNAPSHOT atomicity mode is applicable to SQL. > What if I create a table with TRANSACTIONAL atomicity? Will it fall back to like optimistic/pessimistic transactions (OCC/PCC), or just no transaction supports at all? If OCC/PCC is applied, what are the limitations? TRANSACTIONAL atomicity mode works only with KV API. > 2 (1-yes). Is that possible to implement an external cache store that provides some sort of transaction support that could work for SQL OCC/PCC, any suggestions on supplemental materials that are helpful for the goal? No, it is impossible now. Moreover, SQL is not intended for queries over cache store storages. > 3 (1-false). What are the plans for SQL transaction support later on? Will it likely be supported in the following 2.x versions? Currently there is no (at least I don't know about it) the transactional SQL in road map for 2.x. > I've noticed Ignite 3.x initiative that regards tables as first-class citizens so that SQL transactions and K-V transactions would be the same thing and natively be supported? Yes, Apache Ignite 3 goal is to provide transactions with strong serializable consistency. KV API and SQL will use the same transactional protocol and will not provide weak atomic guaranties. Nevertheless, single KV read/write operations will have minimal transactional overhead for most cases. On Tue, Aug 2, 2022 at 3:26 PM Yijie Shen wrote: > > Hi, > > I notice that "Caches with the TRANSACTIONAL_SNAPSHOT atomicity mode > support SQL transactions"[1], but there are also notes on deprecation of ` > TRANSACTIONAL_SNAPSHOT` since Ignite 2.12 due to lots of limitations and > are not considered production ready [2]. > > I have a few questions about SQL transactions in Ignite: > > 1. Is MVCC the only atomicity mode that supports SQL transactions? What if > I create a table with TRANSACTIONAL atomicity? Will it fall back to like > optimistic/pessimistic transactions (OCC/PCC), or just no transaction > supports at all? If OCC/PCC is applied, what are the limitations? > > 2 (1-yes). Is that possible to implement an external cache store that > provides some sort of transaction support that could work for SQL OCC/PCC, > any suggestions on supplemental materials that are helpful for the goal? > > 3 (1-false). What are the plans for SQL transaction support later on? Will > it likely be supported in the following 2.x versions? I've noticed Ignite > 3.x initiative that regards tables as first-class citizens so that SQL > transactions and K-V transactions would be the same thing and natively be > supported? > > Best, > Yijie > > [1] https://ignite.apache.org/docs/latest/transactions/mvcc > [2] https://issues.apache.org/jira/browse/IGNITE-15757
