[jira] [Created] (IGNITE-11073) Add Copy-on-Write machinery to the Checkpoiner

Maxim Muzafarov created IGNITE-11073: Summary: Add Copy-on-Write machinery to the Checkpoiner Key: IGNITE-11073 URL: https://issues.apache.org/jira/browse/IGNITE-11073 Project: Ignite

[jira] [Created] (IGNITE-11075) Implement index rebuild procedure after partitions uploaded

Maxim Muzafarov created IGNITE-11075: Summary: Implement index rebuild procedure after partitions uploaded Key: IGNITE-11075 URL: https://issues.apache.org/jira/browse/IGNITE-11075 Project:

[jira] [Created] (IGNITE-11074) Implement catch-up temporary WAL

Maxim Muzafarov created IGNITE-11074: Summary: Implement catch-up temporary WAL Key: IGNITE-11074 URL: https://issues.apache.org/jira/browse/IGNITE-11074 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11072) [ML] Prepare an example of model inference in SQL

Anton Dmitriev created IGNITE-11072: --- Summary: [ML] Prepare an example of model inference in SQL Key: IGNITE-11072 URL: https://issues.apache.org/jira/browse/IGNITE-11072 Project: Ignite

[jira] [Created] (IGNITE-11071) [ML] Prepare an example of machine learning on top of SQL table

Anton Dmitriev created IGNITE-11071: --- Summary: [ML] Prepare an example of machine learning on top of SQL table Key: IGNITE-11071 URL: https://issues.apache.org/jira/browse/IGNITE-11071 Project:

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Pavel, Initially I meant Java thick client. And I see the difference between thin and thick Java clients. As was already mentioned thin Java client behaves in way like each cache is enforced to not unwrap binary objects (withKeepBinary()). You can see a test demonstrating current behavior [1].

[MTCGA]: new failures in builds [2818504] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

[MTCGA]: new failures in builds [2741149] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

[MTCGA]: new failures in builds [2896735] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

[jira] [Created] (IGNITE-11070) Update RocketMQ dependency to 4.4.0

Roman Shtykh created IGNITE-11070: - Summary: Update RocketMQ dependency to 4.4.0 Key: IGNITE-11070 URL: https://issues.apache.org/jira/browse/IGNITE-11070 Project: Ignite Issue Type: Task

Re: [DISCUSSION] Control.sh global rework in apache ignite 3.0

Hi! Why should we choose between interactive and command mode? I'd suggest that new utility doesn't matter of its name control.sh or visor should have support of both modes. Sergey Kosarev чт, 24 янв. 2019 г., 23:02 Denis Magda dma...@apache.org: > Sergey, > > Let's break and rebuild the visor

Re: [DISCUSSION] Control.sh global rework in apache ignite 3.0

Sergey, Let's break and rebuild the visor from the ground. It's fine if it becomes incompatible with older versions. - Denis On Thu, Jan 24, 2019 at 7:05 AM Sergey Kozlov wrote: > Denis > > I'm not sure that visorcmd can be refactored without incompatible changes > or significant changes for

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Ivan, There is no inconsistency between thick and thin clients. All of them work with caches in binary mode, see ClientCacheRequest (thin) and PlatformCache (thick) classes. On Thu, Jan 24, 2019 at 10:26 PM Ivan Pavlukhina wrote: > Sergey, > > There are couple of things which should be

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Sergey, There are couple of things which should be addressed: 1. Unnecessary deserialization. 2. Inconsistent behavior. 3. Unclear documentation. Deserialization is not free and in my mind should be avoided where possible. I think that if some feature (like interceptors) requires

[MTCGA]: new failures in builds [2658036] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

Re: Baseline auto-adjust`s discuss

Hi Anton, This is great feature, but I am a bit confused about automatic disabling of a feature during manual baseline adjustment. This may lead to unpleasant situations when a user enabled auto-adjustment, then re-adjusted it manually somehow (e.g. from some previously created script) so that

[jira] [Created] (IGNITE-11069) MVCC: Refactor GridCacheMapEntry mvcc set/remove/lock methods and listeners

Roman Kondakov created IGNITE-11069: --- Summary: MVCC: Refactor GridCacheMapEntry mvcc set/remove/lock methods and listeners Key: IGNITE-11069 URL: https://issues.apache.org/jira/browse/IGNITE-11069

Re: SQL View with list of existing indexes

Hi Vladimir, Thanks for your comments, 1) Agree. 2) Ok. 3) We create number of index copies depend on query parallelism. But seems you are right - it should be exposed on TABLES level. 4) Approx. inline size shouldn't be used here, due to the value depend on node and not has single value. 5) Do

Baseline auto-adjust`s discuss

Hello, Igniters! Work on the Phase II of IEP-4 (Baseline topology) [1] has started. I want to start to discuss of implementation of "Baseline auto-adjust" [2]. "Baseline auto-adjust" feature implements mechanism of auto-adjust baseline corresponding to current topology after event join/left

[jira] [Created] (IGNITE-11068) MVCC TX: Do not create TxLog and do not start vacuum workers in case there are no MVCC caches on the node.

Igor Seliverstov created IGNITE-11068: - Summary: MVCC TX: Do not create TxLog and do not start vacuum workers in case there are no MVCC caches on the node. Key: IGNITE-11068 URL:

[jira] [Created] (IGNITE-11067) MVCC: IoStatistics test failed on TC.

Andrew Mashenkov created IGNITE-11067: - Summary: MVCC: IoStatistics test failed on TC. Key: IGNITE-11067 URL: https://issues.apache.org/jira/browse/IGNITE-11067 Project: Ignite Issue

Re: SQL View with list of existing indexes

Hi Yuriy, Please note that MySQL link is about SHOW command, which is a different beast. In general I think that PG approach is better as it allows user to get quick overview of index content without complex JOINs. I would start with plain single view and add columns view later if we found it

[jira] [Created] (IGNITE-11066) Start MetaStorage for write before activation

Ivan Bessonov created IGNITE-11066: -- Summary: Start MetaStorage for write before activation Key: IGNITE-11066 URL: https://issues.apache.org/jira/browse/IGNITE-11066 Project: Ignite Issue

Re: SQL View with list of existing indexes

One additional thought which I figured out just now. Seems approximately recommended inline size is not good choice to add to the index view, due to value this parameter has different value for each node. Even more, for non affinity node it always will be zero. So, seems it should be excluded

Re: [DISCUSSION] Control.sh global rework in apache ignite 3.0

Denis I'm not sure that visorcmd can be refactored without incompatible changes or significant changes for behaviour: 1. Visorcmd starts as demon node and joins the cluster. The modern utilities don't need spring config and just connect to TCP management port. 2. Visorcmd is mostly an interactive

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

I think it's bad idea. This contract nowhere defined and it's not clear for users. чт, 24 янв. 2019 г. в 17:18, Pavel Tupitsyn : > Yes > > On Thu, Jan 24, 2019 at 5:15 PM Sergey Antonov > wrote: > > > Pavel, > > > > "Leave it as is, use instanceof." > > You meant always use CacheInterceptor and

[jira] [Created] (IGNITE-11064) Add documentation for enabling cache statistics only on appropriate nodes.

Stanilovsky Evgeny created IGNITE-11064: --- Summary: Add documentation for enabling cache statistics only on appropriate nodes. Key: IGNITE-11064 URL: https://issues.apache.org/jira/browse/IGNITE-11064

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Yes On Thu, Jan 24, 2019 at 5:15 PM Sergey Antonov wrote: > Pavel, > > "Leave it as is, use instanceof." > You meant always use CacheInterceptor and in all methods > check, that passed arguments is BinaryObject? > > чт, 24 янв. 2019 г. в 17:10, Pavel Tupitsyn : > > > I don't think we should

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Pavel, "Leave it as is, use instanceof." You meant always use CacheInterceptor and in all methods check, that passed arguments is BinaryObject? чт, 24 янв. 2019 г. в 17:10, Pavel Tupitsyn : > I don't think we should complicate things. Leave it as is, use instanceof. > The fact is - you can get

[jira] [Created] (IGNITE-11062) Calculating Compute Usage section contains confusing numbers

Denis Mekhanikov created IGNITE-11062: - Summary: Calculating Compute Usage section contains confusing numbers Key: IGNITE-11062 URL: https://issues.apache.org/jira/browse/IGNITE-11062 Project:

[jira] [Created] (IGNITE-11063) IgniteClusterActivateDeactivateTestWithPersistence#testDeactivateDuringEvictionAndRebalance has NPE inside of it.

Ivan Bessonov created IGNITE-11063: -- Summary: IgniteClusterActivateDeactivateTestWithPersistence#testDeactivateDuringEvictionAndRebalance has NPE inside of it. Key: IGNITE-11063 URL:

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

I don't think we should complicate things. Leave it as is, use instanceof. The fact is - you can get anything, BinaryObject or any user class, so be prepared. Good example of older API is CacheEvent, which actually has oldValue() and newValue() as Object. Igniters, any other thoughts? On Thu,

[jira] [Created] (IGNITE-11065) System view for caches.

Stanilovsky Evgeny created IGNITE-11065: --- Summary: System view for caches. Key: IGNITE-11065 URL: https://issues.apache.org/jira/browse/IGNITE-11065 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11060) Add documentation about CacheInterceptor.

Sergey Antonov created IGNITE-11060: --- Summary: Add documentation about CacheInterceptor. Key: IGNITE-11060 URL: https://issues.apache.org/jira/browse/IGNITE-11060 Project: Ignite Issue

Re: Ignite index corruption issue -> unrecoverable cluster

Denis, Whan do you think about a more general idea of creating FAQs for Ignite users? What if experts will once place their answer in a wiki page and then develop answers for frequent problems. And before diving into researching each problem, experienced community members will ask users to check

[jira] [Created] (IGNITE-11061) Сopyright still points out 2018

Pavel Voronkin created IGNITE-11061: --- Summary: Сopyright still points out 2018 Key: IGNITE-11061 URL: https://issues.apache.org/jira/browse/IGNITE-11061 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-11059) Print information about pending locks queue in case of dht local tx timeout.

Alexei Scherbakov created IGNITE-11059: -- Summary: Print information about pending locks queue in case of dht local tx timeout. Key: IGNITE-11059 URL: https://issues.apache.org/jira/browse/IGNITE-11059

SQL View with list of existing indexes

Hi Igniters, As part of IEP-29: SQL management and monitoring I'm going to implement SQL view with list of existing indexes. I've investigate how it expose by ORACLE, MySQL and Postgres. ORACLE -

Re: Review and merge IGNITE-10921

Count on my support if nobody else would like to help with the merge. Eventually, I will pick up. ср, 23 янв. 2019 г. в 19:53, Stanislav Lukyanov : > Hi Igniters, > > Can anyone please review and merge IGNITE-10921? > Artur Muradimov contributed the change, I did a review myself and now we >

[jira] [Created] (IGNITE-11058) Possible OOM due to large discard queue in TcpDiscoverySpi

Alexei Scherbakov created IGNITE-11058: -- Summary: Possible OOM due to large discard queue in TcpDiscoverySpi Key: IGNITE-11058 URL: https://issues.apache.org/jira/browse/IGNITE-11058 Project:

Re: Greeting

Hi, My ticket IGNITE-10921 passed review and ready to merge as I understanding. Can anyone merge that or I miss something? On Tue, Jan 22, 2019 at 10:27 PM Dmitriy Pavlov wrote: > Hi Artur, > > You're in, now you can assign an issue to yourself. > > Thank you for interest in Apache Ignite and

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Pavel, how about marker interface DeserializedValueCacheInterceptor? We will deserialize data and pass it to cache interceptor, if CacheInterceptor implements marker interface. чт, 24 янв. 2019 г. в 13:41, Pavel Tupitsyn : > You are exactly right, generic parameters don't make much sense here. >

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Pavel, I agree your's points about working on server side in binary mode, but we should add ability to proccessing data in deserialized form too. Of course, it will add performance drop because of serialization round trip (serialized -> deserialize -> serialized). One of possible scenario: User

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

You are exactly right, generic parameters don't make much sense here. Ignite caches are not restricted to any type, and there is type erasure in Java so you have no runtime guarantees. Maybe Interceptor design should be improved (e.g. add a flag to force binary or non-binary mode), but Thin or

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Hi, Pavel, "Interceptor should support both modes, binary or not. Any code can call withKeepBinary(), this should be expected. Just add if (x instanceof BinaryObject) and go from there. " I don't agree. The cache interceptor[1] is a parametrized class and you couldn't pass multiple cache

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

Hi Sergey, I don't think this is a bug. Thick or thin clients always work in binary mode on server side, because you receive data in serialized form and there is no point in deserializing it. Moreover, in most cases you don't have classes on the server, so binary mode is the only way.

Re: [MTCGA]: new failures in builds [2872965] needs to be handled

Hi, it is probably related to https://issues.apache.org/jira/browse/IGNITE-10822 Test was failing before. I've muted it. ср, 23 янв. 2019 г. в 12:33, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your changes can lead

Re: [MTCGA]: new failures in builds [2872963] needs to be handled

Hi, it is an obvious and stable new test failure. This issue is probably coming from Roman Kondakov (rkondakov) 3 files IGNITE-10753 : MVCC: Await all queries are done before checking versions are cleaned. This closes #5786. Sergey Kosarev (skosarev) 20 files IGNITE-6564 Correct calculation of

Re: CacheInterceptor ClassCastException in case of cache was updated from thin java client

I did a little investigation. In o.a.i.i.p.p.c.c.ClientCacheRequest#cache() enforced cache with keep binary. Why we should always work binary objects? чт, 24 янв. 2019 г. в 12:29, Sergey Antonov : > Hello, Igniters! > > I have ignite node with configured cache. The cache have cache >

CacheInterceptor ClassCastException in case of cache was updated from thin java client

Hello, Igniters! I have ignite node with configured cache. The cache have cache interceptor. I wiil got ClassCastException on cache interceptor, If I put some entry to the cache (without keepBinary) from thin java client. I think it's a bug. I'd like to find out yours view! Also I made JIRA

Re: [DISCUSSION] Control.sh global rework in apache ignite 3.0

Alexey, Denis I agree yours points. I think we should rewrite visor.cmd from scala to java at first. And then merge control.sh into visor.cmd. чт, 24 янв. 2019 г. в 11:44, Alexey Kuznetsov : > I agree with Denis, > > How about to merge control.sh into Visor.CMD ? > And rewrite Visor.CMD from

[jira] [Created] (IGNITE-11057) Document new SQL system view "CACHE_GROUPS_IO"

Vladimir Ozerov created IGNITE-11057: Summary: Document new SQL system view "CACHE_GROUPS_IO" Key: IGNITE-11057 URL: https://issues.apache.org/jira/browse/IGNITE-11057 Project: Ignite

[jira] [Created] (IGNITE-11056) SQL: Create a view with list of existing indexes

Yury Gerzhedovich created IGNITE-11056: -- Summary: SQL: Create a view with list of existing indexes Key: IGNITE-11056 URL: https://issues.apache.org/jira/browse/IGNITE-11056 Project: Ignite

Re: [DISCUSSION] Control.sh global rework in apache ignite 3.0

I agree with Denis, How about to merge control.sh into Visor.CMD ? And rewrite Visor.CMD from Scala to Java. What do you think? On Thu, Jan 24, 2019 at 4:41 AM Denis Magda wrote: > Why don't we go in a reverse direction - instead of creating multiple > scripts for different needs we

Re: Introducing Typescript for the Node.js Client

Igor, I can give it a look. Thomas, can you please create a Pull Request for your changes so that it's easier to review and discuss them? Thanks! - p. On Wed, Jan 23, 2019 at 2:19 AM Igor Sapego wrote: > Great job! > > Forwarding to devlist. > > Are there Node.js guys that can take a look?