Re: [VOTE] Release Apache Ignite 3.0.0-beta1 RC2

+1 вт, 15 нояб. 2022 г. в 08:48, Pavel Tupitsyn : > +1 (binding) > > On Mon, Nov 14, 2022 at 9:05 PM Вячеслав Коптилин < > slava.kopti...@gmail.com> > wrote: > > > Dear Community, > > > > Ignite 3 is moving forward and I think we're in a good spot to release > the > > first beta version. In the

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

Hi Igniters, I would like to ask you to add one more bugfix to the beta1: https://issues.apache.org/jira/browse/IGNITE-18003 Best regards, Aleksandr вт, 1 нояб. 2022 г. в 17:17, Aleksandr Pakhomov : > Hi Igniters, > > I would like to ask you to add two more tickets to the beta1: > > -

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

Igniters, I would like to add following tickets to ignite-3.0.0-beta1 https://issues.apache.org/jira/browse/IGNITE-17806 https://issues.apache.org/jira/browse/IGNITE-17759 https://issues.apache.org/jira/browse/IGNITE-17637 https://issues.apache.org/jira/browse/IGNITE-17263

Re: [VOTE] Add micronaut dependency to Ignite 3 (reopened)

+1 ср, 1 июн. 2022 г. в 12:14, ткаленко кирилл : > + 1 >

Re: Node and cluster life-cycle in ignite-3

Alexei, In general I agree with the given proposal. However I'd also like to clarify a few things: 1. start() is called in "depends on" relation order. 2. It might have sense to add a runLevel parameter to start(): start(int runLevel). 3. Seems that we don't need an afterStart() method. Cause we

[jira] [Created] (IGNITE-14599) Add generic way to bootstrap configuration

Alexander Lapin created IGNITE-14599: Summary: Add generic way to bootstrap configuration Key: IGNITE-14599 URL: https://issues.apache.org/jira/browse/IGNITE-14599 Project: Ignite Issue

[jira] [Created] (IGNITE-14586) Remove @SupperessWarnings when implementation provided.

Alexander Lapin created IGNITE-14586: Summary: Remove @SupperessWarnings when implementation provided. Key: IGNITE-14586 URL: https://issues.apache.org/jira/browse/IGNITE-14586 Project: Ignite

[jira] [Created] (IGNITE-14581) Implement IgniteImpl close method

Alexander Lapin created IGNITE-14581: Summary: Implement IgniteImpl close method Key: IGNITE-14581 URL: https://issues.apache.org/jira/browse/IGNITE-14581 Project: Ignite Issue Type

[jira] [Created] (IGNITE-14580) Add exception handling logic to IgntitionProcessor

Alexander Lapin created IGNITE-14580: Summary: Add exception handling logic to IgntitionProcessor Key: IGNITE-14580 URL: https://issues.apache.org/jira/browse/IGNITE-14580 Project: Ignite

[jira] [Created] (IGNITE-14579) Start rest manager

Alexander Lapin created IGNITE-14579: Summary: Start rest manager Key: IGNITE-14579 URL: https://issues.apache.org/jira/browse/IGNITE-14579 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-14578) Bootstrap configuation manager with distributed configuraiton

Alexander Lapin created IGNITE-14578: Summary: Bootstrap configuation manager with distributed configuraiton Key: IGNITE-14578 URL: https://issues.apache.org/jira/browse/IGNITE-14578 Project

[jira] [Created] (IGNITE-14522) CommunicationManager refactoring

Alexander Lapin created IGNITE-14522: Summary: CommunicationManager refactoring Key: IGNITE-14522 URL: https://issues.apache.org/jira/browse/IGNITE-14522 Project: Ignite Issue Type: Bug

Terms clarification and modules splitting logic

Igniters, Seems that within Ignite-3 we have some mess in terms like manager, cpu, service, module, etc. Let's clarify this point. Also It'll be great to discuss the rules of dividing code into modules. I'll use the context of Ignite cluster & node lifecycle

[jira] [Created] (IGNITE-14100) GridCachePartitionedNodeRestartTest fails due to wrong tx mapping

Alexander Lapin created IGNITE-14100: Summary: GridCachePartitionedNodeRestartTest fails due to wrong tx mapping Key: IGNITE-14100 URL: https://issues.apache.org/jira/browse/IGNITE-14100 Project

[jira] [Created] (IGNITE-14036) Tracing: add ability to trace compute operations.

Alexander Lapin created IGNITE-14036: Summary: Tracing: add ability to trace compute operations. Key: IGNITE-14036 URL: https://issues.apache.org/jira/browse/IGNITE-14036 Project: Ignite

[jira] [Created] (IGNITE-13870) Remove GridCacheAdapter#validateCacheKey cause it seems to be obsolete

Alexander Lapin created IGNITE-13870: Summary: Remove GridCacheAdapter#validateCacheKey cause it seems to be obsolete Key: IGNITE-13870 URL: https://issues.apache.org/jira/browse/IGNITE-13870

[jira] [Created] (IGNITE-13869) Add extra map query logging within the debug level.

Alexander Lapin created IGNITE-13869: Summary: Add extra map query logging within the debug level. Key: IGNITE-13869 URL: https://issues.apache.org/jira/browse/IGNITE-13869 Project: Ignite

[jira] [Created] (IGNITE-13868) Create caches simultaneously in same non-existing cache group led to NPE

Alexander Lapin created IGNITE-13868: Summary: Create caches simultaneously in same non-existing cache group led to NPE Key: IGNITE-13868 URL: https://issues.apache.org/jira/browse/IGNITE-13868

[jira] [Created] (IGNITE-13867) IgniteCacheTxExpiryPolicyTest.testNearAccess almost stably fails in CE master

Alexander Lapin created IGNITE-13867: Summary: IgniteCacheTxExpiryPolicyTest.testNearAccess almost stably fails in CE master Key: IGNITE-13867 URL: https://issues.apache.org/jira/browse/IGNITE-13867

Re: Removing MVCC public API

+1 Best regards, Alexander вт, 15 дек. 2020 г. в 10:59, Konstantin Orlov : > +1 > > -- > Regards, > Konstantin Orlov > Software Engineer, St. Petersburg > +7 (921) 445-65-75 > https://www.gridgain.com > Powered by Apache® Ignite™ > > > >

Re: Tool for performance statistics reports

rove the Tracing API. > 3. Combine both tools under the same API. > > > 14 дек. 2020 г., в 10:42, Alexander Lapin > написал(а): > > > > Hello Igniters, > > > > Because the tracing causes performance drop 52% [4] and can not be > >> used for

Re: Tool for performance statistics reports

Hello Igniters, Because the tracing causes performance drop 52% [4] and can not be > used for collecting statistics about all queries in production > deployments. The performance drop of the profiling tool is less than > 2% and it can be used in production. I have benchmarked the tracing > and

[jira] [Created] (IGNITE-13640) Opencensus module has no runtime dependencies.

Alexander Lapin created IGNITE-13640: Summary: Opencensus module has no runtime dependencies. Key: IGNITE-13640 URL: https://issues.apache.org/jira/browse/IGNITE-13640 Project: Ignite

[jira] [Created] (IGNITE-13393) Tracing: Atomic cache read/write flow.

Alexander Lapin created IGNITE-13393: Summary: Tracing: Atomic cache read/write flow. Key: IGNITE-13393 URL: https://issues.apache.org/jira/browse/IGNITE-13393 Project: Ignite Issue Type

[jira] [Created] (IGNITE-13375) Operations started on client nodes are not traced.

Alexander Lapin created IGNITE-13375: Summary: Operations started on client nodes are not traced. Key: IGNITE-13375 URL: https://issues.apache.org/jira/browse/IGNITE-13375 Project: Ignite

[jira] [Created] (IGNITE-13374) Initial PME hangs because of multiple blinking nodes

Alexander Lapin created IGNITE-13374: Summary: Initial PME hangs because of multiple blinking nodes Key: IGNITE-13374 URL: https://issues.apache.org/jira/browse/IGNITE-13374 Project: Ignite

[jira] [Created] (IGNITE-13373) WAL segmentns do not released on releaseHistoryForPreloading()

Alexander Lapin created IGNITE-13373: Summary: WAL segmentns do not released on releaseHistoryForPreloading() Key: IGNITE-13373 URL: https://issues.apache.org/jira/browse/IGNITE-13373 Project

[jira] [Created] (IGNITE-13251) Deadlock between grid-timeout-worker and a thread opening a communication connection.

Alexander Lapin created IGNITE-13251: Summary: Deadlock between grid-timeout-worker and a thread opening a communication connection. Key: IGNITE-13251 URL: https://issues.apache.org/jira/browse/IGNITE-13251

[jira] [Created] (IGNITE-13238) Instant not supported whithin the scope of jdbc thin.

Alexander Lapin created IGNITE-13238: Summary: Instant not supported whithin the scope of jdbc thin. Key: IGNITE-13238 URL: https://issues.apache.org/jira/browse/IGNITE-13238 Project: Ignite

[jira] [Created] (IGNITE-13236) Rebalance doesn't happen after restart if node failed at the moment of rebalance

Alexander Lapin created IGNITE-13236: Summary: Rebalance doesn't happen after restart if node failed at the moment of rebalance Key: IGNITE-13236 URL: https://issues.apache.org/jira/browse/IGNITE-13236

[jira] [Created] (IGNITE-13233) Invalid milliseconds value of java.util.Date converted to java.sql.Timestamp via JDBC Thin.

Alexander Lapin created IGNITE-13233: Summary: Invalid milliseconds value of java.util.Date converted to java.sql.Timestamp via JDBC Thin. Key: IGNITE-13233 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-13232) JDBC thin: it's not possible to use array of objects as value in where _key=

Alexander Lapin created IGNITE-13232: Summary: JDBC thin: it's not possible to use array of objects as value in where _key= Key: IGNITE-13232 URL: https://issues.apache.org/jira/browse/IGNITE-13232

[jira] [Created] (IGNITE-13231) Unable to use character in where _key= clause via JDBC Thin, if previously putted within cache API.

Alexander Lapin created IGNITE-13231: Summary: Unable to use character in where _key= clause via JDBC Thin, if previously putted within cache API. Key: IGNITE-13231 URL: https://issues.apache.org/jira/browse

[DISCUSSION] Tracing: IGNITE-13060

Hello Igniters, I'd like to discuss with you and then donate changes related to IGNITE-13060 In very brief it's an initial tracing implementation that allows to thrace Communication, Exchange, Discovery and Transactions. Spi concept is used

[jira] [Created] (IGNITE-13060) Tracing: initial implementation

Alexander Lapin created IGNITE-13060: Summary: Tracing: initial implementation Key: IGNITE-13060 URL: https://issues.apache.org/jira/browse/IGNITE-13060 Project: Ignite Issue Type

[jira] [Created] (IGNITE-12326) JDBC thin returns java.util.Date instead of java.sql.Date if input values, putted to cache via cache API are LocalDate or java.sql.Date.

Alexander Lapin created IGNITE-12326: Summary: JDBC thin returns java.util.Date instead of java.sql.Date if input values, putted to cache via cache API are LocalDate or java.sql.Date. Key: IGNITE-12326 URL

[jira] [Created] (IGNITE-12322) Changing baseline via set command may cause NPEs if configured NodeFilter takes node attributes into account

Alexander Lapin created IGNITE-12322: Summary: Changing baseline via set command may cause NPEs if configured NodeFilter takes node attributes into account Key: IGNITE-12322 URL: https://issues.apache.org

[jira] [Created] (IGNITE-12321) Rebalance doesn't happen after restart if node failed at the moment of rebalance.

Alexander Lapin created IGNITE-12321: Summary: Rebalance doesn't happen after restart if node failed at the moment of rebalance. Key: IGNITE-12321 URL: https://issues.apache.org/jira/browse/IGNITE-12321

[jira] [Created] (IGNITE-12320) Partial index rebuild fails in case indexed cache contains different datatypes

Alexander Lapin created IGNITE-12320: Summary: Partial index rebuild fails in case indexed cache contains different datatypes Key: IGNITE-12320 URL: https://issues.apache.org/jira/browse/IGNITE-12320

[jira] [Created] (IGNITE-12315) In case of using ArrayBlockingQueue as key, cache.get() returns null.

Alexander Lapin created IGNITE-12315: Summary: In case of using ArrayBlockingQueue as key, cache.get() returns null. Key: IGNITE-12315 URL: https://issues.apache.org/jira/browse/IGNITE-12315

[jira] [Created] (IGNITE-12314) Unexpected return type in case of retrieving Byte[]{1,2,3} from cache value.

Alexander Lapin created IGNITE-12314: Summary: Unexpected return type in case of retrieving Byte[]{1,2,3} from cache value. Key: IGNITE-12314 URL: https://issues.apache.org/jira/browse/IGNITE-12314

[jira] [Created] (IGNITE-12313) Unable to update value via sql update query if a key is a byte array within non-mvcc mode.

Alexander Lapin created IGNITE-12313: Summary: Unable to update value via sql update query if a key is a byte array within non-mvcc mode. Key: IGNITE-12313 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-12312) JDBC thin: it's not possible to use LocalDate/LocalTime/LocalDateTime as value in where _key=.

Alexander Lapin created IGNITE-12312: Summary: JDBC thin: it's not possible to use LocalDate/LocalTime/LocalDateTime as value in where _key=. Key: IGNITE-12312 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-12311) DELETE by PK doesn't work if PK is TINYINT or SMALLINT.

Alexander Lapin created IGNITE-12311: Summary: DELETE by PK doesn't work if PK is TINYINT or SMALLINT. Key: IGNITE-12311 URL: https://issues.apache.org/jira/browse/IGNITE-12311 Project: Ignite

[jira] [Created] (IGNITE-12310) SortedEvictionPolicy fails with java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang. in case of Byte, Short, Long, etc.

Alexander Lapin created IGNITE-12310: Summary: SortedEvictionPolicy fails with java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang. in case of Byte, Short, Long, etc. Key: IGNITE-12310

[jira] [Created] (IGNITE-12308) Data types coverage for basic sql operations.

Alexander Lapin created IGNITE-12308: Summary: Data types coverage for basic sql operations. Key: IGNITE-12308 URL: https://issues.apache.org/jira/browse/IGNITE-12308 Project: Ignite

[jira] [Created] (IGNITE-12307) Data types coverage for basic cache operations.

Alexander Lapin created IGNITE-12307: Summary: Data types coverage for basic cache operations. Key: IGNITE-12307 URL: https://issues.apache.org/jira/browse/IGNITE-12307 Project: Ignite

[jira] [Created] (IGNITE-12036) Changing baseline via set command may cause NPEs if configured NodeFilter takes node attributes into account

Alexander Lapin created IGNITE-12036: Summary: Changing baseline via set command may cause NPEs if configured NodeFilter takes node attributes into account Key: IGNITE-12036 URL: https://issues.apache.org

[jira] [Created] (IGNITE-11705) Jdbc Thin: add ability to control affinity cache size.

Alexander Lapin created IGNITE-11705: Summary: Jdbc Thin: add ability to control affinity cache size. Key: IGNITE-11705 URL: https://issues.apache.org/jira/browse/IGNITE-11705 Project: Ignite

[jira] [Created] (IGNITE-11661) Jdbc Thin: Implement tests for best effort affinity

Alexander Lapin created IGNITE-11661: Summary: Jdbc Thin: Implement tests for best effort affinity Key: IGNITE-11661 URL: https://issues.apache.org/jira/browse/IGNITE-11661 Project: Ignite

[jira] [Created] (IGNITE-11566) JDBC Thin: add support for custom partitions count within the client side best effort affinity

Alexander Lapin created IGNITE-11566: Summary: JDBC Thin: add support for custom partitions count within the client side best effort affinity Key: IGNITE-11566 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-11565) JDBC Thin: add connection resolution in case of multiple partitons

Alexander Lapin created IGNITE-11565: Summary: JDBC Thin: add connection resolution in case of multiple partitons Key: IGNITE-11565 URL: https://issues.apache.org/jira/browse/IGNITE-11565 Project

[jira] [Created] (IGNITE-11507) SQL: Ensure that affinity topology version doesn't change during PartitionResult construction/application.

Alexander Lapin created IGNITE-11507: Summary: SQL: Ensure that affinity topology version doesn't change during PartitionResult construction/application. Key: IGNITE-11507 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-11321) JDBC Thin: implement nodes multi version support in case of best effort affinity mode.

Alexander Lapin created IGNITE-11321: Summary: JDBC Thin: implement nodes multi version support in case of best effort affinity mode. Key: IGNITE-11321 URL: https://issues.apache.org/jira/browse/IGNITE-11321

[jira] [Created] (IGNITE-11320) JDBC Thin: add support for individual reconnect in case of best effort affinity mode.

Alexander Lapin created IGNITE-11320: Summary: JDBC Thin: add support for individual reconnect in case of best effort affinity mode. Key: IGNITE-11320 URL: https://issues.apache.org/jira/browse/IGNITE-11320

[jira] [Created] (IGNITE-11314) JDBC Thin: add transaction-scoped flag to JdbcHandler's responses.

Alexander Lapin created IGNITE-11314: Summary: JDBC Thin: add transaction-scoped flag to JdbcHandler's responses. Key: IGNITE-11314 URL: https://issues.apache.org/jira/browse/IGNITE-11314 Project

[jira] [Created] (IGNITE-11309) JDBC Thin: add flag or property to disable best effort affinity

Alexander Lapin created IGNITE-11309: Summary: JDBC Thin: add flag or property to disable best effort affinity Key: IGNITE-11309 URL: https://issues.apache.org/jira/browse/IGNITE-11309 Project

[jira] [Created] (IGNITE-11287) JDBC Thin: best effort affinity

Alexander Lapin created IGNITE-11287: Summary: JDBC Thin: best effort affinity Key: IGNITE-11287 URL: https://issues.apache.org/jira/browse/IGNITE-11287 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-11258) JDBC: update connection setup logic.

Alexander Lapin created IGNITE-11258: Summary: JDBC: update connection setup logic. Key: IGNITE-11258 URL: https://issues.apache.org/jira/browse/IGNITE-11258 Project: Ignite Issue Type

[jira] [Created] (IGNITE-11257) JDBC: update handshake protocol so that the node returns its UUID.

Alexander Lapin created IGNITE-11257: Summary: JDBC: update handshake protocol so that the node returns its UUID. Key: IGNITE-11257 URL: https://issues.apache.org/jira/browse/IGNITE-11257 Project

[jira] [Created] (IGNITE-11197) SQL:Ability to resolve partiton for temporal data types.

Alexander Lapin created IGNITE-11197: Summary: SQL:Ability to resolve partiton for temporal data types. Key: IGNITE-11197 URL: https://issues.apache.org/jira/browse/IGNITE-11197 Project: Ignite

[jira] [Created] (IGNITE-11019) SQL: explain plan of a simple query contains merge table

Alexander Lapin created IGNITE-11019: Summary: SQL: explain plan of a simple query contains merge table Key: IGNITE-11019 URL: https://issues.apache.org/jira/browse/IGNITE-11019 Project: Ignite

[jira] [Created] (IGNITE-10893) ClientListenerResponse.status uses codes both from IgniteQueryErrorCode and ClientListenerResponse itself.

Alexander Lapin created IGNITE-10893: Summary: ClientListenerResponse.status uses codes both from IgniteQueryErrorCode and ClientListenerResponse itself. Key: IGNITE-10893 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-10836) Add documentation for jdbc thin query cancel

Alexander Lapin created IGNITE-10836: Summary: Add documentation for jdbc thin query cancel Key: IGNITE-10836 URL: https://issues.apache.org/jira/browse/IGNITE-10836 Project: Ignite

Re: JDBC thin driver: support connection timeout

> > > method? > > > 2. Also I checked another quite popular jdbc driver provided by > > > MariaDB [2]. They ignore an executor argument as well and set a socket > > > timeout instead. So, I think that we are on a safe side if we ignore > > > an executor.

JDBC thin driver: support connection timeout

Hi Igniters, Within context of connection timeout [ https://issues.apache.org/jira/browse/IGNITE-5234] it's not obvious whether it's required to use setNetworkTimeout's executor or not. According to the javadoc of java.sql.Connection#setNetworkTimeout(Executor executor, int milliseconds),

[jira] [Created] (IGNITE-10340) JDBC thin: in some cases it's not possible to convert IllegalStateException to SQLException with appropriate message.

Alexander Lapin created IGNITE-10340: Summary: JDBC thin: in some cases it's not possible to convert IllegalStateException to SQLException with appropriate message. Key: IGNITE-10340 URL: https

Welcome Message

Hello, Ignite Community! My name is Alexander Lapin. I want to contribute to Apache Ignite. my JIRA user name is alapin. Any help on this will be appreciated. Thanks!