Re: Applicability of term 'cache' to Apache Ignite
Or we could extend our SQL commands by "GET BY KEY = X" and "PUT (x1, x2, x3) BY KEY = X" and the IgniteTable could be correct. Agree with Denis that each table in the 3rd normal form is like key-value store. Key-value operations are only subset of rich SQL commands. The problem with IgniteData that it's too common. Also, it's difficult to understand is it a plural or single object? For instance, the bunch of IgniteTables could be IgniteData. But the set of IgniteData? IgniteDatum? чт, 18 окт. 2018 г. в 4:18, Denis Magda : > Key-value calls are just primary key based calls. From a user perspective, > it's the same as "SELECT * FROM table WHERE primary_idx = X", just > different API. > > -- > Denis > > On Wed, Oct 17, 2018 at 5:04 PM Dmitriy Setrakyan > wrote: > > > On Wed, Oct 17, 2018 at 4:58 PM Denis Magda wrote: > > > > > I've been calling everything "tables" instead of "caches" for a while. > > The > > > main reason is the maturity of our SQL engine - seeing more SQL users > and > > > deployments which talk "tables" language. > > > > > > > > I think "IgniteTable" only implies SQL, not key-value. We need both. > > >
Re: [DISCUSS] Dropping hadoop-accelerator download
No objections from my side. -- Denis On Tue, Oct 16, 2018 at 4:45 PM Dmitriy Setrakyan wrote: > Igniters, > > I would like to suggest dropping the hadoop accelerator distribution of > Apache Ignite. Note, that it does not mean dropping any features. We are > still going to support IGFS, in-memory map reduce, spark integration, etc. > However, the hadoop-accelerator downloadable is putting extra pressure on > the community to test and document, which can be avoided. All the features > will still be supported through regular Ignite distribution. > > Any objections? > > D. >
[jira] [Created] (IGNITE-9925) Validate QueryEntites on cache creation
Mikhail Cherkasov created IGNITE-9925: - Summary: Validate QueryEntites on cache creation Key: IGNITE-9925 URL: https://issues.apache.org/jira/browse/IGNITE-9925 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 2.6 Reporter: Mikhail Cherkasov Fix For: 2.8 it's possible to create a cache with the index for non-existing field and kill the whole cluster, I think this should be prevented by configuration validation, see reproducer in https://issues.apache.org/jira/browse/IGNITE-9907 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Applicability of term 'cache' to Apache Ignite
Key-value calls are just primary key based calls. From a user perspective, it's the same as "SELECT * FROM table WHERE primary_idx = X", just different API. -- Denis On Wed, Oct 17, 2018 at 5:04 PM Dmitriy Setrakyan wrote: > On Wed, Oct 17, 2018 at 4:58 PM Denis Magda wrote: > > > I've been calling everything "tables" instead of "caches" for a while. > The > > main reason is the maturity of our SQL engine - seeing more SQL users and > > deployments which talk "tables" language. > > > > > I think "IgniteTable" only implies SQL, not key-value. We need both. >
[jira] [Created] (IGNITE-9924) Rename "allow non-collacated joins" to allow distributed joins
Mikhail Cherkasov created IGNITE-9924: - Summary: Rename "allow non-collacated joins" to allow distributed joins Key: IGNITE-9924 URL: https://issues.apache.org/jira/browse/IGNITE-9924 Project: Ignite Issue Type: Improvement Components: visor Affects Versions: 2.6 Reporter: Mikhail Cherkasov Assignee: Mikhail Cherkasov Attachments: Screen Shot 2018-10-17 at 15.33.33.png if you google "allow non-collacated joins" it will show you doc with title about distributed join, our API use is/setDistributedJoins method, so why we have this non-collacated in WebConsole, let's rename it to "allow distributed joins" to make it more consistent to our API and doc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Applicability of term 'cache' to Apache Ignite
On Wed, Oct 17, 2018 at 4:58 PM Denis Magda wrote: > I've been calling everything "tables" instead of "caches" for a while. The > main reason is the maturity of our SQL engine - seeing more SQL users and > deployments which talk "tables" language. > > I think "IgniteTable" only implies SQL, not key-value. We need both.
Re: Applicability of term 'cache' to Apache Ignite
I've been calling everything "tables" instead of "caches" for a while. The main reason is the maturity of our SQL engine - seeing more SQL users and deployments which talk "tables" language. On Wed, Oct 17, 2018 at 3:55 PM Dmitriy Setrakyan wrote: > If dataset cannot be used, can we still consider "IgniteData"? > > D. > > On Wed, Oct 17, 2018 at 5:06 AM Ilya Lantukh > wrote: > > > As I see, many people agree that the term *"cache"* is outdated, but > > consider these changes too disruptive. > > > > For me, keeping terminology up-to-date is important part of project > > development. If we change some of our core terms with more relevant ones, > > it indeed might cause confusion for current users, but in long term it > will > > help new users to understand what Ignite is and what it isn't. And most > > short-term problems can easily be avoided by keeping @Deprecated > > IgniteCache. > > > > On Wed, Oct 17, 2018 at 2:59 PM Ilya Lantukh > > wrote: > > > > > Unfortunately, we already use the word *"store"* for many other > concepts, > > > like CacheStore and PageStore. I'd prefer to avoid giving it one more > > > meaning. > > > > > > As already mentioned, *"dataset"* has special meaning for ML folks. > > > > > > *"Bucket" *might give wrong association with bucket in a hash table. > > > > > > On Wed, Oct 17, 2018 at 1:49 PM Igor Sapego > wrote: > > > > > >> Well, the obvious term for me is a "Store" or "MemoryStore", as we > > already > > >> have persistence store. > > >> > > >> Best Regards, > > >> Igor > > >> > > >> > > >> On Wed, Oct 17, 2018 at 1:19 PM Andrey Kuznetsov > > >> wrote: > > >> > > >> > I'm not an ML expert, so 'dataset' term just reminds me of various > > >> client > > >> > drivers to access tables from RDBM servers. For me, the only common > > >> trait > > >> > of all kinds of Ignite caches is their asociativity. So if we rename > > >> them > > >> > I'd suggest something like KVStore. > > >> > > > >> > ср, 17 окт. 2018 г. в 12:56, Alexey Zinoviev < > zaleslaw@gmail.com > > >: > > >> > > > >> > > From my perspective, the main goal is to make easy the explanation > > >> what > > >> > is > > >> > > Ignite on conferences, marketing deals, in papers, in > documentation. > > >> And > > >> > > the > > >> > > /cache/ term really reduces the area of Ignite usage in users > minds. > > >> > > > > >> > > I don't support the critical changes in code base, but I support > all > > >> > > changes > > >> > > that helps the goal described above in this letter. > > >> > > > > >> > > > > >> > > > > >> > > -- > > >> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >> > > > > >> > > > >> > > > >> > -- > > >> > Best regards, > > >> > Andrey Kuznetsov. > > >> > > > >> > > > > > > > > > -- > > > Best regards, > > > Ilya > > > > > > > > > -- > > Best regards, > > Ilya > > >
Re: SQL Engine
Dmitriy, Correct me if I’m wrong, but the concept is to store everything off heap - which is perfectly fine :). So, the question is how SQL engine actually works. Analyzing profiler object generation and sizes on heap, I’ve learned that for each query entire rows in question are copied on heap which, I’d say is a little bit inefficient (more or less depending on domain object). Maybe an example will help to further elaborate on the issue. Lets say we have an object ORGANIZATION which has only two query enabled fields (annotated with @QuerySqlField) and 20 more value fields (text/blobs, …) which are not used in queries (not annotated with @QuerySqlField and thus not visible by SQL engine). So, how COUNT works? Will SQL engine copy on heap just a part of ORGANIZATION rows (2 fields that might be part of COUNT query) or entire rows (sql enabled fields + text/blob fields…)? From what I saw during profiling, I’d say entire rows will be copied on heap. Just to compare, this is our, real world example: Object A (~300k rows, each row has 5 columns, all sql enabled), COUNT(*) takes ~2MB on heap Object B (~25k rows, each row has 16 columns, 5 sql enabled fields and 11 text value fields), COUNT(*) takes ~60MB on heap - nearly 30 times more Regards, Igor > On Oct 18, 2018, at 12:24 AM, Dmitriy Setrakyan wrote: > > I do not understand - why are we copying values on-heap? If we must copy > something, why not copy rows into some off-heap space and read what we have > from there? At least this way we will not burden the JVM with extra GC > pressure. > > D. > > On Wed, Oct 17, 2018 at 10:33 AM Igor Tanackovic > wrote: > >> Vladimir, >> >> Thanks for explanation... that’s true - ignite never deserialize values >> during query execution. The point here is why copying fields to heap that >> sql engine could not use (not annotated as QuerySqlField)? >> SQL count is a perfect example where you can benefit (heap space and gc) >> copying only field sql engine could use. >> >> Regards, >> Igor >> >> On Wed, Oct 17, 2018 at 18:47 Vladimir Ozerov >> wrote: >> >>> Hi Igor, >>> >>> We never deserialize values during query execution. Instead, we copy the >>> row to heap and extract fields as needed. In general case it is >> impossible >>> to avoid reading the whole row because we do not know whether this is >>> COUNT(*) or COUNT(*) WHERE or COUNT() WHERE >>> . >>> We do handle plain COUNT(*) as speical case and iterate over index only, >>> but event this simple query cannot avoid row reads in general case when >> new >>> snapshot mode is enabled, because an entry in the index may be not >> visible >>> to current transaction. >>> >>> On Wed, Oct 17, 2018 at 7:19 PM igor.tanackovic < >> igor.tanacko...@gmail.com >>> wrote: >>> Hello, Seems that SQL engine always deserialize whole objects instead of using just SQL enabled fields (annotated with @QuerySqlField). This may have a >> huge impact on Ignite heap usage and GC overhead as well. For example, we have a cache holding big objects but with only two sql query fields which for each query execution (SELECT COUNT(*) FROM 'cache') consumes large amount on heap memory (~300MB). As a proof of concept, >> we divided the same cache to *index* cache with only sql query field and a *data* holding whole object for materialization. The same query (SELECT COUNT(*) FROM 'index-cache') consumes ~25 time less memory! The same is true for all other queries. The obvious workaround would be to always have separated regions for indexes (sql query enabled region) and a data/value region for materialization, >>> but it might be a good idea to fix this in a systematic way during off heap deserialization. Regards, Igor -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >>> >>
Re: Applicability of term 'cache' to Apache Ignite
If dataset cannot be used, can we still consider "IgniteData"? D. On Wed, Oct 17, 2018 at 5:06 AM Ilya Lantukh wrote: > As I see, many people agree that the term *"cache"* is outdated, but > consider these changes too disruptive. > > For me, keeping terminology up-to-date is important part of project > development. If we change some of our core terms with more relevant ones, > it indeed might cause confusion for current users, but in long term it will > help new users to understand what Ignite is and what it isn't. And most > short-term problems can easily be avoided by keeping @Deprecated > IgniteCache. > > On Wed, Oct 17, 2018 at 2:59 PM Ilya Lantukh > wrote: > > > Unfortunately, we already use the word *"store"* for many other concepts, > > like CacheStore and PageStore. I'd prefer to avoid giving it one more > > meaning. > > > > As already mentioned, *"dataset"* has special meaning for ML folks. > > > > *"Bucket" *might give wrong association with bucket in a hash table. > > > > On Wed, Oct 17, 2018 at 1:49 PM Igor Sapego wrote: > > > >> Well, the obvious term for me is a "Store" or "MemoryStore", as we > already > >> have persistence store. > >> > >> Best Regards, > >> Igor > >> > >> > >> On Wed, Oct 17, 2018 at 1:19 PM Andrey Kuznetsov > >> wrote: > >> > >> > I'm not an ML expert, so 'dataset' term just reminds me of various > >> client > >> > drivers to access tables from RDBM servers. For me, the only common > >> trait > >> > of all kinds of Ignite caches is their asociativity. So if we rename > >> them > >> > I'd suggest something like KVStore. > >> > > >> > ср, 17 окт. 2018 г. в 12:56, Alexey Zinoviev >: > >> > > >> > > From my perspective, the main goal is to make easy the explanation > >> what > >> > is > >> > > Ignite on conferences, marketing deals, in papers, in documentation. > >> And > >> > > the > >> > > /cache/ term really reduces the area of Ignite usage in users minds. > >> > > > >> > > I don't support the critical changes in code base, but I support all > >> > > changes > >> > > that helps the goal described above in this letter. > >> > > > >> > > > >> > > > >> > > -- > >> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > >> > > > >> > > >> > > >> > -- > >> > Best regards, > >> > Andrey Kuznetsov. > >> > > >> > > > > > > -- > > Best regards, > > Ilya > > > > > -- > Best regards, > Ilya >
Re: SQL Engine
I do not understand - why are we copying values on-heap? If we must copy something, why not copy rows into some off-heap space and read what we have from there? At least this way we will not burden the JVM with extra GC pressure. D. On Wed, Oct 17, 2018 at 10:33 AM Igor Tanackovic wrote: > Vladimir, > > Thanks for explanation... that’s true - ignite never deserialize values > during query execution. The point here is why copying fields to heap that > sql engine could not use (not annotated as QuerySqlField)? > SQL count is a perfect example where you can benefit (heap space and gc) > copying only field sql engine could use. > > Regards, > Igor > > On Wed, Oct 17, 2018 at 18:47 Vladimir Ozerov > wrote: > > > Hi Igor, > > > > We never deserialize values during query execution. Instead, we copy the > > row to heap and extract fields as needed. In general case it is > impossible > > to avoid reading the whole row because we do not know whether this is > > COUNT(*) or COUNT(*) WHERE or COUNT() WHERE > > . > > We do handle plain COUNT(*) as speical case and iterate over index only, > > but event this simple query cannot avoid row reads in general case when > new > > snapshot mode is enabled, because an entry in the index may be not > visible > > to current transaction. > > > > On Wed, Oct 17, 2018 at 7:19 PM igor.tanackovic < > igor.tanacko...@gmail.com > > > > > wrote: > > > > > Hello, > > > > > > Seems that SQL engine always deserialize whole objects instead of using > > > just > > > SQL enabled fields (annotated with @QuerySqlField). This may have a > huge > > > impact on Ignite heap usage and GC overhead as well. > > > > > > For example, we have a cache holding big objects but with only two sql > > > query > > > fields which for each query execution (SELECT COUNT(*) FROM 'cache') > > > consumes large amount on heap memory (~300MB). As a proof of concept, > we > > > divided the same cache to *index* cache with only sql query field and a > > > *data* holding whole object for materialization. The same query (SELECT > > > COUNT(*) FROM 'index-cache') consumes ~25 time less memory! The same is > > > true > > > for all other queries. > > > > > > The obvious workaround would be to always have separated regions for > > > indexes > > > (sql query enabled region) and a data/value region for materialization, > > but > > > it might be a good idea to fix this in a systematic way during off heap > > > deserialization. > > > > > > Regards, > > > Igor > > > > > > > > > > > > -- > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > >
[GitHub] ignite pull request #5018: IGNITE-9663: Data node failure can cause TX hangi...
GitHub user rkondakov opened a pull request: https://github.com/apache/ignite/pull/5018 IGNITE-9663: Data node failure can cause TX hanging. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9663 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5018.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5018 commit 02b9a43df59c6c3b5ed5424d462bb21383e4da9b Author: rkondakov Date: 2018-10-17T18:56:10Z IGNITE-9663: Data node failure can cause TX hanging. WIP ---
Re: Python thin client
Dmitry, Great, now client works properly on all OS Thanks I hope PR will be merged soon Igor, can please help with that? ср, 17 окт. 2018 г. в 20:48, Dmitry Melnichuk < dmitry.melnic...@nobitlost.com>: > Stepan, > > Sadly, it was a C `long` data type size mismatch between Windows and > other OSes. I investigated this issue and offered a pull request. > > https://github.com/apache/ignite/pull/5017 > > On 10/17/18 6:29 PM, Stepan Pilschikov wrote: > > Dmitry, > > > > I've trying to use python thin client with Ignite 2.7 it dosn't work > > Please help to investigate > > Problem reproduced on several others machines > > > > Issue: > > https://issues.apache.org/jira/browse/IGNITE-9908 > > >
Re: Python thin client
Stepan, Sadly, it was a C `long` data type size mismatch between Windows and other OSes. I investigated this issue and offered a pull request. https://github.com/apache/ignite/pull/5017 On 10/17/18 6:29 PM, Stepan Pilschikov wrote: Dmitry, I've trying to use python thin client with Ignite 2.7 it dosn't work Please help to investigate Problem reproduced on several others machines Issue: https://issues.apache.org/jira/browse/IGNITE-9908
Re: SQL Engine
Vladimir, Thanks for explanation... that’s true - ignite never deserialize values during query execution. The point here is why copying fields to heap that sql engine could not use (not annotated as QuerySqlField)? SQL count is a perfect example where you can benefit (heap space and gc) copying only field sql engine could use. Regards, Igor On Wed, Oct 17, 2018 at 18:47 Vladimir Ozerov wrote: > Hi Igor, > > We never deserialize values during query execution. Instead, we copy the > row to heap and extract fields as needed. In general case it is impossible > to avoid reading the whole row because we do not know whether this is > COUNT(*) or COUNT(*) WHERE or COUNT() WHERE > . > We do handle plain COUNT(*) as speical case and iterate over index only, > but event this simple query cannot avoid row reads in general case when new > snapshot mode is enabled, because an entry in the index may be not visible > to current transaction. > > On Wed, Oct 17, 2018 at 7:19 PM igor.tanackovic > > wrote: > > > Hello, > > > > Seems that SQL engine always deserialize whole objects instead of using > > just > > SQL enabled fields (annotated with @QuerySqlField). This may have a huge > > impact on Ignite heap usage and GC overhead as well. > > > > For example, we have a cache holding big objects but with only two sql > > query > > fields which for each query execution (SELECT COUNT(*) FROM 'cache') > > consumes large amount on heap memory (~300MB). As a proof of concept, we > > divided the same cache to *index* cache with only sql query field and a > > *data* holding whole object for materialization. The same query (SELECT > > COUNT(*) FROM 'index-cache') consumes ~25 time less memory! The same is > > true > > for all other queries. > > > > The obvious workaround would be to always have separated regions for > > indexes > > (sql query enabled region) and a data/value region for materialization, > but > > it might be a good idea to fix this in a systematic way during off heap > > deserialization. > > > > Regards, > > Igor > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >
[GitHub] ignite pull request #4975: IGNITE-9868 Send refresh partitions message for a...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4975 ---
[GitHub] ignite pull request #5017: Ignite 9908
GitHub user dmelnichuk opened a pull request: https://github.com/apache/ignite/pull/5017 Ignite 9908 Ensure compatibility with Windows (setup and 8-byte data type). You can merge this pull request into a Git repository by running: $ git pull https://github.com/nobitlost/ignite ignite-9908 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5017.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5017 commit 4b444dff62c04b97bc2cdb0676ad52880374 Author: ekaterina-nbl Date: 2018-03-20T21:12:21Z initial implementation commit d1e8014c80f698028d23e09cafd7ea190ac3e929 Author: ekaterina-nbl Date: 2018-03-20T21:32:52Z initial implementation commit f79229e233ffa7bff1e7c22f04749924af6d712a Author: ekaterina-nbl Date: 2018-03-22T09:39:32Z initial implementation commit 658d60b58840080b664e02815f4ba6aac76e5804 Author: ekaterina-nbl Date: 2018-03-22T16:52:18Z minor update commit 617cef12ad72791c7e7e67179e1b0c3f7f3ae6bb Author: ekaterina-nbl Date: 2018-03-25T13:33:27Z api spec commit d9729585f5a901977e2a2e40e86a2b715fab79fa Author: alexey-nbl Date: 2018-03-25T21:27:11Z link to api_spec added commit ea847eba62e556fa81cbf9838ffe17af60f464e4 Author: ekaterina-nbl Date: 2018-03-31T22:07:50Z error types modified commit c2ad53fe625cc3a05155eeef318421538830 Author: ekaterina-nbl Date: 2018-03-31T23:41:56Z client states commit 6d2233864b4d891361d38a7143846570bd6c0ef6 Author: ekaterina-nbl Date: 2018-04-01T13:11:27Z object types improvement commit 52fbc5f87143da068596141cb59b17b684fd2c1f Author: ekaterina-nbl Date: 2018-04-02T16:59:52Z complex objects commit cae5a28e7e0d610434debcc140738e2f48d061cf Author: ekaterina-nbl Date: 2018-04-02T20:13:00Z object types improvement commit 3165405d4eae09519dc9b5f40f162eb74a9b3c5d Author: ekaterina-nbl Date: 2018-04-02T21:21:26Z client states commit fdbb8f86b32fe4c038d38620a80921be3038f31f Author: alexey-nbl Date: 2018-04-03T08:26:04Z Ignite client states described commit 04b946885db0ea2f6fe56a75e28302641dad5f61 Author: alexey-nbl Date: 2018-04-03T09:35:49Z minor update commit f4aaf1c3f23c82ba7974b4c571a9984748e5e82e Author: alexey-nbl Date: 2018-04-03T12:47:54Z Update ObjectType.js commit e4c8279f4e83b3ed13383420ab3d1417b090a3fa Author: ekaterina-nbl Date: 2018-04-03T13:46:19Z minor updates + api spec commit ed2e4ee830ca40a28dc31958665f52fab6a0bcdd Author: alexey-nbl Date: 2018-04-04T14:34:52Z Update ObjectType.js commit 7e1666eb5df82b622a028c0ea949fa21c79e66c2 Author: alexey-nbl Date: 2018-04-04T15:14:00Z Update ObjectType.js commit 7b0270d65b597dc1b0d164e78f07c3a21c37ca67 Author: ekaterina-nbl Date: 2018-04-08T17:16:43Z sql queries, key value ops commit fe90f53fd08f77add17fbf06d014f9a9b0a11c65 Author: alexey-nbl Date: 2018-04-08T18:31:47Z Update IgniteClient.js commit 04137bf5ec3b7077e194edd0100a01bb43f7933a Author: alexey-nbl Date: 2018-04-08T18:37:04Z Update CacheConfiguration.js commit b63ad5980718da1b0c44fa4ca138c6e85e47aef3 Author: alexey-nbl Date: 2018-04-08T19:11:11Z Update ObjectType.js commit 756b908c9dc38ae497e4d7d740f836dabed93e48 Author: alexey-nbl Date: 2018-04-08T22:41:54Z Update CacheClient.js commit e96ffee17298dd25d26a7029738132478271cf92 Author: ekaterina-nbl Date: 2018-04-08T23:23:33Z object array, minor updates commit c050e671f74232c4efc41f51c2018d08b152cbbc Author: alexey-nbl Date: 2018-04-09T21:04:35Z Update CacheClient.js commit 25052a4e93d6fcc0b0c4789fdd5a1eb85413b5a2 Author: alexey-nbl Date: 2018-04-09T22:43:50Z Update ObjectType.js commit c516b4147c10398d4f34d78a8830dd0fcb5f28f4 Author: alexey-nbl Date: 2018-04-10T11:50:13Z Update CacheClient.js commit 0e9924a0df8a1d41718fb929698b8e4416f2efa2 Author: ekaterina-nbl Date: 2018-04-10T13:21:16Z cache key value operations tests commit e09ee0e7969bffd6f4cfd11579f6d0ff9b486c99 Author: ekaterina-nbl Date: 2018-04-10T13:21:50Z Merge branch 'master' of https://github.com/nobitlost/ignite commit 15d2abce41b4f1c9d4d5fecd44a99a5393177482 Author: alexey-nbl Date: 2018-04-10T14:38:57Z Update Query.js ---
[GitHub] ignite pull request #4962: IGNITE-9710 Ignite watchdog service handles longr...
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/4962 ---
[GitHub] ignite pull request #4914: IGNITE-9737
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/4914 ---
[GitHub] ignite pull request #4936: IGNITE-9756
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4936 ---
[GitHub] ignite pull request #5015: IGNITE-9922 Python thin: python directory should ...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5015 ---
SQL Engine
Moving to dev forum... Hello, Seems that SQL engine always deserialize whole objects instead of using just SQL enabled fields (annotated with @QuerySqlField). This may have a huge impact on Ignite heap usage and GC overhead as well. For example, we have a cache holding big objects but with only two sql query fields which for each query execution (SELECT COUNT(*) FROM 'cache') consumes large amount on heap memory (~300MB). As a proof of concept, we divided the same cache to *index* cache with only sql query field and a *data* holding whole object for materialization. The same query (SELECT COUNT(*) FROM 'index-cache') consumes ~25 time less memory! The same is true for all other queries. The obvious workaround would be to always have separated regions for indexes (sql query enabled region) and a data/value region for materialization, but it might be a good idea to fix this in a systematic way during off heap deserialization. Regards, Igor -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: SQL Engine
Hi Igor, We never deserialize values during query execution. Instead, we copy the row to heap and extract fields as needed. In general case it is impossible to avoid reading the whole row because we do not know whether this is COUNT(*) or COUNT(*) WHERE or COUNT() WHERE . We do handle plain COUNT(*) as speical case and iterate over index only, but event this simple query cannot avoid row reads in general case when new snapshot mode is enabled, because an entry in the index may be not visible to current transaction. On Wed, Oct 17, 2018 at 7:19 PM igor.tanackovic wrote: > Hello, > > Seems that SQL engine always deserialize whole objects instead of using > just > SQL enabled fields (annotated with @QuerySqlField). This may have a huge > impact on Ignite heap usage and GC overhead as well. > > For example, we have a cache holding big objects but with only two sql > query > fields which for each query execution (SELECT COUNT(*) FROM 'cache') > consumes large amount on heap memory (~300MB). As a proof of concept, we > divided the same cache to *index* cache with only sql query field and a > *data* holding whole object for materialization. The same query (SELECT > COUNT(*) FROM 'index-cache') consumes ~25 time less memory! The same is > true > for all other queries. > > The obvious workaround would be to always have separated regions for > indexes > (sql query enabled region) and a data/value region for materialization, but > it might be a good idea to fix this in a systematic way during off heap > deserialization. > > Regards, > Igor > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
[GitHub] ignite pull request #5016: IGNITE-9420 Logical recovery before PME
GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5016 IGNITE-9420 Logical recovery before PME You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9420 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5016.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5016 commit fc0ba2d389fa021055413b9d6596859d3ea838df Author: Maxim Muzafarov Date: 2018-08-24T14:27:26Z IGNITE-7196: initial commit commit 07d8c0296476656131ffcf929c6eeaeaec1a3a7f Author: Maxim Muzafarov Date: 2018-08-31T08:11:02Z Merge branch 'master' into ignite-7196 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheDatabaseSharedManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/IgniteCacheDatabaseSharedManager.java commit b8935632089b6a77fa533089508a062c6933161b Author: Maxim Muzafarov Date: 2018-08-31T08:18:20Z IGNITE-7196: move down init listener commit 97bde70641d02621925e85bf46defc6c0c213423 Author: Maxim Muzafarov Date: 2018-08-31T08:21:20Z IGNITE-7196: revert down init listener commit e9c84f2a9f5ae5f2fe4c9e2275addc6042a635e8 Author: Maxim Muzafarov Date: 2018-09-03T16:47:46Z IGNITE-7196: WIP restore binary on first activate commit a8e6a59bd680c5e861159c32788022e9c000f019 Author: Maxim Muzafarov Date: 2018-09-03T20:24:09Z IGNITE-7196: WIP remove readAndRestore from PME commit 71b5efb046bbe13632ec938a06683d6a2c398b4e Author: Maxim Muzafarov Date: 2018-09-03T20:30:17Z IGNITE-7196: WIP remove readAndRestore from PME 2 commit 9f982cd05ad608317c183e9f5a4008a178dac31a Author: Maxim Muzafarov Date: 2018-09-04T09:41:32Z Merge branch 'master' into ignite-7196 # Conflicts: # modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/persistence/db/wal/IgniteWalRecoveryTest`.java commit 161b48d94a574007b37a070e731e963ded6bf431 Author: Maxim Muzafarov Date: 2018-09-04T09:46:45Z IGNITE-7196: WIP remove unused imports commit 1f286be9e80a484a62c6c355e4141afef55923a6 Author: Maxim Muzafarov Date: 2018-09-04T16:18:37Z IGNITE-7196: WIP make lastRestored flag checkable commit 2b6b17c3a8e9b254fe9337dc76b51c6ca02dd617 Author: Maxim Muzafarov Date: 2018-09-04T16:25:38Z IGNITE-7196: WIP lastRestored 2 commit 323b0e83af00878afd5286dcf6973973b8188844 Author: Maxim Muzafarov Date: 2018-09-04T19:17:42Z IGNITE-7196: WIP make lastRestored flag checkable 2 commit 087e63a5999a8cd4b06d6ee6085d4d1db837576d Author: Maxim Muzafarov Date: 2018-09-04T19:56:12Z IGNITE-7196: WIP make lastRestored flag checkable 3 commit 3b40a2ef0aef628af088f3a1a8ab0a9a11b3be4b Author: Maxim Muzafarov Date: 2018-09-04T21:21:53Z IGNITE-7196: WIP make lastRestored flag checkable 4 commit 6f9b44ed9e1c523c266167ff9f03a6e680c2d9fa Author: Maxim Muzafarov Date: 2018-09-05T09:46:42Z IGNITE-7196: WIP minor changes commit bb86b9144c9e863ad86af27823046f992503d00e Author: Maxim Muzafarov Date: 2018-09-05T12:14:51Z IGNITE-7196: WIP without activate#deactivate 1 commit 87b4f325c5dd8a93f6c4fc1dd21d50c9c3752684 Author: Maxim Muzafarov Date: 2018-09-05T13:14:58Z IGNITE-7196: WIP without activate#deactivate 2 commit 65f83f68f5b5ca1923bcc5a7c4841ca2455cb902 Author: Maxim Muzafarov Date: 2018-09-05T14:23:24Z IGNITE-7196: WIP without activate#deactivate 3 commit 166fd04c3bd5dfdd39c6118c21f0ae39170842eb Author: Maxim Muzafarov Date: 2018-09-05T15:43:35Z IGNITE-7196: WIP without activate#deactivate 4 commit b60a68cb1275b8c1074ae3d22c4c7f7967c883b6 Author: Maxim Muzafarov Date: 2018-09-05T16:32:48Z IGNITE-7196: WIP without activate#deactivate 5 commit a60fdd67145ee5d6f4bbac81de9e6b1d9bbab6b1 Author: Maxim Muzafarov Date: 2018-09-05T16:44:03Z IGNITE-7196: WIP without activate#deactivate 6 commit 3cf0911f646c4100e0a1654e3dec3c0f4952abf5 Author: Maxim Muzafarov Date: 2018-09-05T17:21:02Z IGNITE-7196: WIP without activate#deactivate 7 commit 65ed786c9d9bf83ab56f60349ac8eaba8099807b Author: Maxim Muzafarov Date: 2018-09-05T18:28:59Z IGNITE-7196: WIP without activate#deactivate 8 commit 53f81a8ce75785c9b6badf67a93261e8eae2947a Author: Maxim Muzafarov Date: 2018-09-05T18:32:39Z IGNITE-7196: WIP minor code changes commit 61633dc9dd0980070b5f1c9ec5a9624b99b32b69 Author: Maxim Muzafarov Date: 2018-09-06T17:56:13Z IGNITE-7196: WIP suspend#resume WAL logging 1 commit 3772cbdcfe9edd90d76d5cb841c4c00123077eac Author: Maxim Muzafarov Date: 2018-09-07T17:56:07Z IGNITE-7196: WIP deactivate wal commit 5d7affd2539f2b1fb4ab63c93a7c3fba2104eb2b Author: Maxim
[GitHub] ignite pull request #5015: IGNITE-9922 Python thin: python directory should ...
GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/5015 IGNITE-9922 Python thin: python directory should be included in binar⦠â¦y release You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9922 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5015.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5015 commit abbc1c1302fd7e1183203ab1e44b8bf9436a9940 Author: Peter Ivanov Date: 2018-10-17T15:25:35Z IGNITE-9922 Python thin: python directory should be included in binary release ---
SQL Engine
Hello, Seems that SQL engine always deserialize whole objects instead of using just SQL enabled fields (annotated with @QuerySqlField). This may have a huge impact on Ignite heap usage and GC overhead as well. For example, we have a cache holding big objects but with only two sql query fields which for each query execution (SELECT COUNT(*) FROM 'cache') consumes large amount on heap memory (~300MB). As a proof of concept, we divided the same cache to *index* cache with only sql query field and a *data* holding whole object for materialization. The same query (SELECT COUNT(*) FROM 'index-cache') consumes ~25 time less memory! The same is true for all other queries. The obvious workaround would be to always have separated regions for indexes (sql query enabled region) and a data/value region for materialization, but it might be a good idea to fix this in a systematic way during off heap deserialization. Regards, Igor -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
[jira] [Created] (IGNITE-9923) Fix unused imprts according to inspections profile
Maxim Muzafarov created IGNITE-9923: --- Summary: Fix unused imprts according to inspections profile Key: IGNITE-9923 URL: https://issues.apache.org/jira/browse/IGNITE-9923 Project: Ignite Issue Type: Bug Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 New `Code Inspections` profile can be found \idea\ignite_inspections.xml. We need to fix rule `Unused imports` for the whole Apache Ignite project. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4619: IGNITE-9272 j.u.zip.CRC32algo instead of PureJava...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4619 ---
[GitHub] ignite pull request #5014: IGNITE-9918 Default configuration missed
GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/5014 IGNITE-9918 Default configuration missed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9918 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5014.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5014 commit 64cbe291ba1ddaffaa57936785dbea81357b753e Author: Peter Ivanov Date: 2018-10-17T15:04:33Z IGNITE-9918 Default configuration missed ---
[jira] [Created] (IGNITE-9922) Python thin: python directory should be included in binary release
Igor Sapego created IGNITE-9922:
---
Summary: Python thin: python directory should be included in
binary release
Key: IGNITE-9922
URL: https://issues.apache.org/jira/browse/IGNITE-9922
Project: Ignite
Issue Type: Bug
Components: thin client
Reporter: Igor Sapego
Fix For: 2.7
Currently, python directory is not generated by the {{maven install}} command.
Need to add appropriate copy steps to {{assembly/release-fabric-base.xml}} file.
The following components should be copied:
{noformat}
ignite/modules/platforms/python/pyignite/**
ignite/modules/platforms/python/requirements/**
ignite/modules/platforms/python/LICENSE
ignite/modules/platforms/python/README.md
ignite/modules/platforms/python/setup.py
{noformat}
(** stands for "all the files and sub-folders recursively, starting from
this folder".)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #5013: IGNITE-9909 Extract file handle from WAL manager
GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5013 IGNITE-9909 Extract file handle from WAL manager You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9909 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5013.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5013 commit 8d54934e6127d8a74f2182f1e4e32723c9a3dc90 Author: Anton Kalashnikov Date: 2018-10-17T09:22:42Z IGNITE-9909 Extract file handle from WAL manager ---
Re: Apache Ignite 2.7. Last Mile
JFYI IGNITE-9737 and IGNITE-9710 are merged to release branch. On Wed, Oct 17, 2018 at 5:41 PM Pavel Tupitsyn wrote: > > Thank you. Fix has been merged to master and cherry-picked to ignite-2.7. > > On Wed, Oct 17, 2018 at 1:26 PM Nikolay Izhikov wrote: > > > Pavel. > > > > Ok, I agree to include this ticket into 2.7 > > Let's do it. > > > > В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет: > > > Nikolay, > > > > > > It completely breaks a major feature under certain conditions. I would > > > consider it a blocker. > > > > > > On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov > > wrote: > > > > > > > Hello, Pavel. > > > > > > > > Is it a blocker? > > > > > > > > В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет: > > > > > Hi Igniters, > > > > > > > > > > I'd like to include IGNITE-9877 in 2.7, can we do that? > > > > > The fix is ready, I'm waiting for TC run. > > > > > > > > > > Pavel > > > > > > > > > > On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван > > > > > > > > wrote: > > > > > > > > > > > Hi NIkolay, > > > > > > > > > > > > Thank you for keeping everybody focused! Regarding to my ticket > > > > > > IGNITE-5935. > > > > > > It is in final stage now. Tests look good. I believe that it will > > be > > > > > > > > merged > > > > > > in couple of days (at most). > > > > > > > > > > > > ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov > >: > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > 9 tickets to go! > > > > > > > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > Taras Ledkov - IGNITE-9882 > > > > > > > Petr Ivanov - IGNITE-9852 > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > Roman Kondakov - IGNITE-9663 > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > > > > > > В Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет: > > > > > > > > Hi, > > > > > > > > > > > > > > > > I've found that IGNITE-9723 was resolved but didn't cherry > > picked > > > > > > > > to > > > > > > > > ignite-2.7 branch. So I'll do it. > > > > > > > > On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov < > > > > > > > > nizhi...@apache.org> > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > We have 13 tickets mapped to 2.7. > > > > > > > > > All tickets assigned to some contributor. > > > > > > > > > > > > > > > > > > Alexey Gonchruk - IGNITE-9784, IGNITE-9895 > > > > > > > > > Vladimir Ozerov - IGNITE-9887 > > > > > > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > > > Petr Ivanov - IGNITE-9852 > > > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > Roman Kondakov - IGNITE-9663 > > > > > > > > > Taras Ledkov - IGNITE-9864 > > > > > > > > > Igor Seliverstov - IGNITE-9292 > > > > > > > > > > > > > > > > > > В Пн, 15/10/2018 в 17:49 +0300, Andrey Gura пишет: > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > I'm looking at IGNITE-9737 and IGNITE-9710 which are > > critical > > > > > > > > > > > > issues > > > > > > > > > > from my point of view. > > > > > > > > > > I need some time for review, possible fixes and merge. > > > > > > > > > > I will keep you informed. > > > > > > > > > > On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego < > > > > > > > > isap...@apache.org> > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > Guys, Python client is in the master and ignite-2.7 > > already. > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov < > > > > > > > > > > > > > > voze...@gridgain.com> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > > > > > AI 2.7 will include Python thin client. TC suite is > > crucial > > > > > > > > > > > > part > > > > > > > of this > > > > > > > > > > > > feature, so we should keep the ticket in AI 2.7 scope. > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov < > > > > > > > > > > > > > > nizhi...@apache.org> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > > > > > > > There is no progress till Friday. > > > > > > > > > > > > > We have 14 tickets mapped to 2.7. > > > > > > > > > > > > > > > > > > > > > > > > > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov > > пишет: > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > > > > > > > > > We made some progress yesterday. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Please, note, we have 1 new ticket mapped to 2.7 > > > > > > > > > > > > > > "IGNITE-9852: Create >
Re: Apache Ignite 2.7. Last Mile
Thank you. Fix has been merged to master and cherry-picked to ignite-2.7. On Wed, Oct 17, 2018 at 1:26 PM Nikolay Izhikov wrote: > Pavel. > > Ok, I agree to include this ticket into 2.7 > Let's do it. > > В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет: > > Nikolay, > > > > It completely breaks a major feature under certain conditions. I would > > consider it a blocker. > > > > On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov > wrote: > > > > > Hello, Pavel. > > > > > > Is it a blocker? > > > > > > В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет: > > > > Hi Igniters, > > > > > > > > I'd like to include IGNITE-9877 in 2.7, can we do that? > > > > The fix is ready, I'm waiting for TC run. > > > > > > > > Pavel > > > > > > > > On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван > > > > > > wrote: > > > > > > > > > Hi NIkolay, > > > > > > > > > > Thank you for keeping everybody focused! Regarding to my ticket > > > > > IGNITE-5935. > > > > > It is in final stage now. Tests look good. I believe that it will > be > > > > > > merged > > > > > in couple of days (at most). > > > > > > > > > > ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov >: > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > 9 tickets to go! > > > > > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > Taras Ledkov - IGNITE-9882 > > > > > > Petr Ivanov - IGNITE-9852 > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > Roman Kondakov - IGNITE-9663 > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > > > > В Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет: > > > > > > > Hi, > > > > > > > > > > > > > > I've found that IGNITE-9723 was resolved but didn't cherry > picked > > > > > > to > > > > > > > ignite-2.7 branch. So I'll do it. > > > > > > > On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov < > > > > > > nizhi...@apache.org> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > We have 13 tickets mapped to 2.7. > > > > > > > > All tickets assigned to some contributor. > > > > > > > > > > > > > > > > Alexey Gonchruk - IGNITE-9784, IGNITE-9895 > > > > > > > > Vladimir Ozerov - IGNITE-9887 > > > > > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > > Petr Ivanov - IGNITE-9852 > > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > Roman Kondakov - IGNITE-9663 > > > > > > > > Taras Ledkov - IGNITE-9864 > > > > > > > > Igor Seliverstov - IGNITE-9292 > > > > > > > > > > > > > > > > В Пн, 15/10/2018 в 17:49 +0300, Andrey Gura пишет: > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > I'm looking at IGNITE-9737 and IGNITE-9710 which are > critical > > > > > > > > > > issues > > > > > > > > > from my point of view. > > > > > > > > > I need some time for review, possible fixes and merge. > > > > > > > > > I will keep you informed. > > > > > > > > > On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego < > > > > > > isap...@apache.org> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Guys, Python client is in the master and ignite-2.7 > already. > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov < > > > > > > > > > > > > voze...@gridgain.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > > > AI 2.7 will include Python thin client. TC suite is > crucial > > > > > > > > > > part > > > > > > of this > > > > > > > > > > > feature, so we should keep the ticket in AI 2.7 scope. > > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov < > > > > > > > > > > > > nizhi...@apache.org> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > > > > > There is no progress till Friday. > > > > > > > > > > > > We have 14 tickets mapped to 2.7. > > > > > > > > > > > > > > > > > > > > > > > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov > пишет: > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > > > > > > > We made some progress yesterday. > > > > > > > > > > > > > > > > > > > > > > > > > > Please, note, we have 1 new ticket mapped to 2.7 > > > > > > > > > > > > "IGNITE-9852: Create > > > > > > > > > > > > > > > > > > > > > > > > TeamCity suite for Python thin client" > > > > > > > > > > > > > > > > > > > > > > > > > > This ticket doesn't sound like a blocker to me. > Let's > > > > > > > > > > > > exclude it from > > > > > > > > > > > > > > > > > > > > > > > > release scope. > > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > > > > > > > > > Here is the list of
[GitHub] ignite pull request #5012: check PDS 2 (indexing) exit code 130
GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/5012 check PDS 2 (indexing) exit code 130 You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite PDS-2-indexing-130-code Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5012.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5012 commit 8fc004ded2a3e56f36ac73379fbf3537baa8e0c2 Author: Dmitrii Ryabov Date: 2018-10-17T14:25:04Z check exit code 130 ---
[GitHub] ignite pull request #5009: IGNITE-9877 .NET: Fix AmbiguousMatchException in ...
Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/5009 ---
[jira] [Created] (IGNITE-9920) Hadoop: native dependencies are not resolved properly
Vladimir Ozerov created IGNITE-9920: --- Summary: Hadoop: native dependencies are not resolved properly Key: IGNITE-9920 URL: https://issues.apache.org/jira/browse/IGNITE-9920 Project: Ignite Issue Type: Task Components: hadoop Reporter: Vladimir Ozerov Probably caused by Hadoop version update, which was necessary for Java 9+ support. Failed tests: # HadoopSnappyTest.testSnappy # HadoopSnappyFullMapReduceTest.testWholeMapReduceExecution # HadoopTeraSortTest.testTeraSort # HadoopTeraSortTest.testTeraSortGzip # HadoopCommandLineTest.testHiveCommandLine -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9919) IgniteHadoopFileSystemAbstractSelfTest.testRenameIfSrcPathIsAlreadyBeingOpenedToRead fails
Vladimir Ozerov created IGNITE-9919:
---
Summary:
IgniteHadoopFileSystemAbstractSelfTest.testRenameIfSrcPathIsAlreadyBeingOpenedToRead
fails
Key: IGNITE-9919
URL: https://issues.apache.org/jira/browse/IGNITE-9919
Project: Ignite
Issue Type: Task
Components: hadoop
Reporter: Vladimir Ozerov
Reason is unknown, need to investigate.
{code}
java.io.IOException: Stream has been closed: IgfsOutputStreamImpl
[mode=DUAL_ASYNC, writeFut=GridFutureAdapter [ignoreInterrupts=false,
state=DONE, res=true, hash=237512060], fileInfo=IgfsFileInfo [len=0,
blockSize=524288, lockId=afa3a228661-124a3e4e-7712-45a7-830b-8a03ac6be6a2,
affKey=null, fileMap=IgfsFileMap [ranges=null], evictExclude=true],
streamRange=null]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #5003: IGNITE-9882: investigation progress 1
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5003 ---
[jira] [Created] (IGNITE-9918) Default configuration missed
Sergey Kozlov created IGNITE-9918:
-
Summary: Default configuration missed
Key: IGNITE-9918
URL: https://issues.apache.org/jira/browse/IGNITE-9918
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
Node start failed if try to execute {{bin/ignite.sh}} without arguments:
{noformat}
C:\GitRoot\gg-qa\i2test\var\suite-client\ignite\bin>ignite.bat
class org.apache.ignite.IgniteException: Spring XML configuration path is
invalid: config\default-config.xml. Note that
this path should be either absolute or a relative local file system path,
relative to META-INF in classpath or valid URL
to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1014)
at org.apache.ignite.Ignition.start(Ignition.java:351)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Spring XML
configuration path is invalid: config\default-conf
ig.xml. Note that this path should be either absolute or a relative local file
system path, relative to META-INF in clas
spath or valid URL to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3858)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:858)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:730)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:699)
at org.apache.ignite.Ignition.start(Ignition.java:348)
... 1 more
Caused by: java.net.MalformedURLException: no protocol:
config\default-config.xml
at java.net.URL.(URL.java:593)
at java.net.URL.(URL.java:490)
at java.net.URL.(URL.java:439)
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3849)
... 5 more
Failed to start grid: Spring XML configuration path is invalid:
config\default-config.xml. Note that this path should be
either absolute or a relative local file system path, relative to META-INF in
classpath or valid URL to IGNITE_HOME.
{noformat}
Obviously that there's no {{config/default-config.xml}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9917) Write proper tests for start/stop client.
Ivan Bessonov created IGNITE-9917: - Summary: Write proper tests for start/stop client. Key: IGNITE-9917 URL: https://issues.apache.org/jira/browse/IGNITE-9917 Project: Ignite Issue Type: Sub-task Reporter: Ivan Bessonov Assignee: Ivan Bessonov Write proper tests for start/stop client. For now we only have "start client" tests that don't actually check blocking on exchange in proper way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9915) Do not block get/getAll during baseline node stopping.
Ivan Bessonov created IGNITE-9915: - Summary: Do not block get/getAll during baseline node stopping. Key: IGNITE-9915 URL: https://issues.apache.org/jira/browse/IGNITE-9915 Project: Ignite Issue Type: Sub-task Reporter: Ivan Bessonov Assignee: Ivan Bessonov Do not block get/getAll during baseline node stopping. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9916) Do not block SQL operations during exchange.
Ivan Bessonov created IGNITE-9916: - Summary: Do not block SQL operations during exchange. Key: IGNITE-9916 URL: https://issues.apache.org/jira/browse/IGNITE-9916 Project: Ignite Issue Type: Sub-task Reporter: Ivan Bessonov Assignee: Ivan Bessonov Do not block SQL operations during exchange. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9914) SubjectId for TaskEvents is incorrect for remote clients
Andrey Aleksandrov created IGNITE-9914: -- Summary: SubjectId for TaskEvents is incorrect for remote clients Key: IGNITE-9914 URL: https://issues.apache.org/jira/browse/IGNITE-9914 Project: Ignite Issue Type: Bug Components: clients Affects Versions: 2.6 Reporter: Andrey Aleksandrov Assignee: Andrey Aleksandrov Fix For: 2.8 In case if the task was initialized from the remote client as web console then taskEvent.subjectId() will return the incorrect value. It will contain the subject id for the node where this task was deployed. Ignite already have the thread local store for subject id but looks like we have a problem in GridTaskProcessor: UUID subjId = getThreadContext(TC_SUBJ_ID); But it always is null because of the correct value for TC_SUBJ_ID stored in Map map = thCtx.get(); So it should be changed to UUID subjId = (UUID)map.get(TC_SUBJ_ID); -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4983: IGNITE-9875 GridDhtPartitionsStateValidator speed...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4983 ---
Re: Abbreviation code-style requirement.
+1 to > leave abbreviations for common words with single meaning. For example, group -> grp, transaction -> tx, context -> ctx. And optional for the multi-words. ср, 17 окт. 2018 г. в 14:54, Ilya Lantukh : > + 1 from me to make abbreviations optional. > > On Wed, Oct 17, 2018 at 1:00 PM Sergey Antonov > wrote: > > > + 1 > > > > But, I think that we must leave abbreviations for common words with > single > > meaning. For example, group -> grp, transaction -> tx, context -> ctx. > > > > ср, 17 окт. 2018 г. в 12:46, Alexey Zinoviev : > > > > > + 1 > > > I dislike the current list of abbreviations. It gives me a pain to > > support > > > code with unclear variables naming, also I agree that we should avoid > > crazy > > > Java camel long naming like > > > FactoryBuildingCrazyAffinityCallerForComibingInSpace but instead that > we > > > make shorter clear concepts like /counter/, /vertex/, /collection/ and > > etc > > > > > > > > > > > > -- > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > > > > > -- > > BR, Sergey Antonov > > > > > -- > Best regards, > Ilya >
[jira] [Created] (IGNITE-9913) Prevent data updates blocking in case of backup BLT server node leave
Ivan Rakov created IGNITE-9913: -- Summary: Prevent data updates blocking in case of backup BLT server node leave Key: IGNITE-9913 URL: https://issues.apache.org/jira/browse/IGNITE-9913 Project: Ignite Issue Type: Improvement Components: general Reporter: Ivan Rakov Assignee: Ivan Rakov Fix For: 2.8 Ignite cluster performs distributed partition map exchange when any server node leaves or joins the topology. Distributed PME blocks all updates and may take a long time. If all partitions are assigned according to the baseline topology and server node leaves, there's no actual need to perform distributed PME: every cluster node is able to recalculate new affinity assigments and partition states locally. If we'll implement such lightweight PME and handle mapping and lock requests on new topology version correctly, updates won't be stopped on server node leave (except updates of partitions that lost their primary copy). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #5011: IGNITE-9899 Fix processing of TX cache backups by...
GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/5011 IGNITE-9899 Fix processing of TX cache backups by continuous queries. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9899 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5011.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5011 commit 32ff0f95e4e93ee07037f6f9b4d071c344530b5f Author: Denis Mekhanikov Date: 2018-10-17T12:32:13Z IGNITE-9899 Fix processing of TX cache backups by continuous queries. ---
[jira] [Created] (IGNITE-9912) Improve Javadoc suite
Peter Ivanov created IGNITE-9912:
Summary: Improve Javadoc suite
Key: IGNITE-9912
URL: https://issues.apache.org/jira/browse/IGNITE-9912
Project: Ignite
Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov
# Add {{javadoc}} profile to maven execution
# Devise a solution to workaround warning about Hibernate duplicate
package-info (due to Hibernate 4 and 5 modules together in single reactor)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #5002: IGNITE-9898 fix checkpoint thread hangs on await ...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5002 ---
[GitHub] ignite pull request #5010: IGNITE-5565 replace Cron4J with Spring task sched...
GitHub user macrergate opened a pull request: https://github.com/apache/ignite/pull/5010 IGNITE-5565 replace Cron4J with Spring task scheduler You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5565-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5010.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5010 commit 7e00950338df216e678e87346196bbc6b68d151a Author: Sergey Kosarev Date: 2018-01-17T14:31:49Z IGNITE-5565 replace Cron4J with Spring task scheduler commit 253ea9e8adf198876f553cc469dcad70cd869d88 Author: macrergate Date: 2018-10-17T12:17:58Z IGNITE-5565 fixed codestyle and start/stop and removed extra dependency ---
[GitHub] ignite pull request #4996: IGNITE-9830
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4996 ---
[jira] [Created] (IGNITE-9911) CacheMvccSelectForUpdateQueryAbstractTest#testSelectForUpdateAfterAbortedTx periodically hangs
Igor Seliverstov created IGNITE-9911: Summary: CacheMvccSelectForUpdateQueryAbstractTest#testSelectForUpdateAfterAbortedTx periodically hangs Key: IGNITE-9911 URL: https://issues.apache.org/jira/browse/IGNITE-9911 Project: Ignite Issue Type: Task Components: mvcc Reporter: Igor Seliverstov Assignee: Igor Seliverstov Fix For: 2.7 See [TC history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7394250566319069846=testDetails] for details -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9910) [ML] Move the static copy-pasted datasets from examples to special Util class
Aleksey Zinoviev created IGNITE-9910: Summary: [ML] Move the static copy-pasted datasets from examples to special Util class Key: IGNITE-9910 URL: https://issues.apache.org/jira/browse/IGNITE-9910 Project: Ignite Issue Type: Improvement Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 There are a few copy-pasted datasets like Iris, Titanic and etc. They should be refactored to one dataset class with constants -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Applicability of term 'cache' to Apache Ignite
As I see, many people agree that the term *"cache"* is outdated, but consider these changes too disruptive. For me, keeping terminology up-to-date is important part of project development. If we change some of our core terms with more relevant ones, it indeed might cause confusion for current users, but in long term it will help new users to understand what Ignite is and what it isn't. And most short-term problems can easily be avoided by keeping @Deprecated IgniteCache. On Wed, Oct 17, 2018 at 2:59 PM Ilya Lantukh wrote: > Unfortunately, we already use the word *"store"* for many other concepts, > like CacheStore and PageStore. I'd prefer to avoid giving it one more > meaning. > > As already mentioned, *"dataset"* has special meaning for ML folks. > > *"Bucket" *might give wrong association with bucket in a hash table. > > On Wed, Oct 17, 2018 at 1:49 PM Igor Sapego wrote: > >> Well, the obvious term for me is a "Store" or "MemoryStore", as we already >> have persistence store. >> >> Best Regards, >> Igor >> >> >> On Wed, Oct 17, 2018 at 1:19 PM Andrey Kuznetsov >> wrote: >> >> > I'm not an ML expert, so 'dataset' term just reminds me of various >> client >> > drivers to access tables from RDBM servers. For me, the only common >> trait >> > of all kinds of Ignite caches is their asociativity. So if we rename >> them >> > I'd suggest something like KVStore. >> > >> > ср, 17 окт. 2018 г. в 12:56, Alexey Zinoviev : >> > >> > > From my perspective, the main goal is to make easy the explanation >> what >> > is >> > > Ignite on conferences, marketing deals, in papers, in documentation. >> And >> > > the >> > > /cache/ term really reduces the area of Ignite usage in users minds. >> > > >> > > I don't support the critical changes in code base, but I support all >> > > changes >> > > that helps the goal described above in this letter. >> > > >> > > >> > > >> > > -- >> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >> > > >> > >> > >> > -- >> > Best regards, >> > Andrey Kuznetsov. >> > >> > > > -- > Best regards, > Ilya > -- Best regards, Ilya
Re: Applicability of term 'cache' to Apache Ignite
Unfortunately, we already use the word *"store"* for many other concepts, like CacheStore and PageStore. I'd prefer to avoid giving it one more meaning. As already mentioned, *"dataset"* has special meaning for ML folks. *"Bucket" *might give wrong association with bucket in a hash table. On Wed, Oct 17, 2018 at 1:49 PM Igor Sapego wrote: > Well, the obvious term for me is a "Store" or "MemoryStore", as we already > have persistence store. > > Best Regards, > Igor > > > On Wed, Oct 17, 2018 at 1:19 PM Andrey Kuznetsov > wrote: > > > I'm not an ML expert, so 'dataset' term just reminds me of various client > > drivers to access tables from RDBM servers. For me, the only common trait > > of all kinds of Ignite caches is their asociativity. So if we rename them > > I'd suggest something like KVStore. > > > > ср, 17 окт. 2018 г. в 12:56, Alexey Zinoviev : > > > > > From my perspective, the main goal is to make easy the explanation what > > is > > > Ignite on conferences, marketing deals, in papers, in documentation. > And > > > the > > > /cache/ term really reduces the area of Ignite usage in users minds. > > > > > > I don't support the critical changes in code base, but I support all > > > changes > > > that helps the goal described above in this letter. > > > > > > > > > > > > -- > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > > > > > -- > > Best regards, > > Andrey Kuznetsov. > > > -- Best regards, Ilya
Re: Abbreviation code-style requirement.
+ 1 from me to make abbreviations optional. On Wed, Oct 17, 2018 at 1:00 PM Sergey Antonov wrote: > + 1 > > But, I think that we must leave abbreviations for common words with single > meaning. For example, group -> grp, transaction -> tx, context -> ctx. > > ср, 17 окт. 2018 г. в 12:46, Alexey Zinoviev : > > > + 1 > > I dislike the current list of abbreviations. It gives me a pain to > support > > code with unclear variables naming, also I agree that we should avoid > crazy > > Java camel long naming like > > FactoryBuildingCrazyAffinityCallerForComibingInSpace but instead that we > > make shorter clear concepts like /counter/, /vertex/, /collection/ and > etc > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > -- > BR, Sergey Antonov > -- Best regards, Ilya
Re: Applicability of term 'cache' to Apache Ignite
Well, the obvious term for me is a "Store" or "MemoryStore", as we already have persistence store. Best Regards, Igor On Wed, Oct 17, 2018 at 1:19 PM Andrey Kuznetsov wrote: > I'm not an ML expert, so 'dataset' term just reminds me of various client > drivers to access tables from RDBM servers. For me, the only common trait > of all kinds of Ignite caches is their asociativity. So if we rename them > I'd suggest something like KVStore. > > ср, 17 окт. 2018 г. в 12:56, Alexey Zinoviev : > > > From my perspective, the main goal is to make easy the explanation what > is > > Ignite on conferences, marketing deals, in papers, in documentation. And > > the > > /cache/ term really reduces the area of Ignite usage in users minds. > > > > I don't support the critical changes in code base, but I support all > > changes > > that helps the goal described above in this letter. > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > -- > Best regards, > Andrey Kuznetsov. >
[GitHub] ignite pull request #4800: IGNITE-9652: fix missorted modifiers
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4800 ---
Re: Apache Ignite 2.7. Last Mile
Pavel. Ok, I agree to include this ticket into 2.7 Let's do it. В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет: > Nikolay, > > It completely breaks a major feature under certain conditions. I would > consider it a blocker. > > On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov wrote: > > > Hello, Pavel. > > > > Is it a blocker? > > > > В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет: > > > Hi Igniters, > > > > > > I'd like to include IGNITE-9877 in 2.7, can we do that? > > > The fix is ready, I'm waiting for TC run. > > > > > > Pavel > > > > > > On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван > > > > wrote: > > > > > > > Hi NIkolay, > > > > > > > > Thank you for keeping everybody focused! Regarding to my ticket > > > > IGNITE-5935. > > > > It is in final stage now. Tests look good. I believe that it will be > > > > merged > > > > in couple of days (at most). > > > > > > > > ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov : > > > > > > > > > Hello, Igniters. > > > > > > > > > > 9 tickets to go! > > > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > Taras Ledkov - IGNITE-9882 > > > > > Petr Ivanov - IGNITE-9852 > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > Roman Kondakov - IGNITE-9663 > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > > В Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет: > > > > > > Hi, > > > > > > > > > > > > I've found that IGNITE-9723 was resolved but didn't cherry picked > > > > to > > > > > > ignite-2.7 branch. So I'll do it. > > > > > > On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov < > > > > nizhi...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > We have 13 tickets mapped to 2.7. > > > > > > > All tickets assigned to some contributor. > > > > > > > > > > > > > > Alexey Gonchruk - IGNITE-9784, IGNITE-9895 > > > > > > > Vladimir Ozerov - IGNITE-9887 > > > > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > Petr Ivanov - IGNITE-9852 > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > Roman Kondakov - IGNITE-9663 > > > > > > > Taras Ledkov - IGNITE-9864 > > > > > > > Igor Seliverstov - IGNITE-9292 > > > > > > > > > > > > > > В Пн, 15/10/2018 в 17:49 +0300, Andrey Gura пишет: > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > I'm looking at IGNITE-9737 and IGNITE-9710 which are critical > > > > > > > > issues > > > > > > > > from my point of view. > > > > > > > > I need some time for review, possible fixes and merge. > > > > > > > > I will keep you informed. > > > > > > > > On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego < > > > > isap...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Guys, Python client is in the master and ignite-2.7 already. > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov < > > > > > > > > > > voze...@gridgain.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > AI 2.7 will include Python thin client. TC suite is crucial > > > > > > > > part > > > > > of this > > > > > > > > > > feature, so we should keep the ticket in AI 2.7 scope. > > > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov < > > > > > > > > > > nizhi...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > > > There is no progress till Friday. > > > > > > > > > > > We have 14 tickets mapped to 2.7. > > > > > > > > > > > > > > > > > > > > > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет: > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > > > > > We made some progress yesterday. > > > > > > > > > > > > > > > > > > > > > > > > Please, note, we have 1 new ticket mapped to 2.7 > > > > > > > > > > "IGNITE-9852: Create > > > > > > > > > > > > > > > > > > > > > > TeamCity suite for Python thin client" > > > > > > > > > > > > > > > > > > > > > > > > This ticket doesn't sound like a blocker to me. Let's > > > > > > > > > > exclude it from > > > > > > > > > > > > > > > > > > > > > > release scope. > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > > > > > > > Here is the list of remaining tickets(14) mapped to > > > > 2.7. > > > > > > > > > > > > > > > > > > > > > > > > Peter Ivanov - IGNITE-9852, IGNITE-9685, > > > > > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > > > > > > Igor Seliverstov - IGNITE-9749, IGNITE-9292 > > > > > > > > > > > > Dmitry Melnichuk - IGNITE-7782 >
Re: Apache Ignite 2.7. Last Mile
Nikolay, It completely breaks a major feature under certain conditions. I would consider it a blocker. On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov wrote: > Hello, Pavel. > > Is it a blocker? > > В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет: > > Hi Igniters, > > > > I'd like to include IGNITE-9877 in 2.7, can we do that? > > The fix is ready, I'm waiting for TC run. > > > > Pavel > > > > On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван > wrote: > > > > > Hi NIkolay, > > > > > > Thank you for keeping everybody focused! Regarding to my ticket > > > IGNITE-5935. > > > It is in final stage now. Tests look good. I believe that it will be > merged > > > in couple of days (at most). > > > > > > ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov : > > > > > > > Hello, Igniters. > > > > > > > > 9 tickets to go! > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > Taras Ledkov - IGNITE-9882 > > > > Petr Ivanov - IGNITE-9852 > > > > Ivan Pavlukhin - IGNITE-5935 > > > > Roman Kondakov - IGNITE-9663 > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > В Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет: > > > > > Hi, > > > > > > > > > > I've found that IGNITE-9723 was resolved but didn't cherry picked > to > > > > > ignite-2.7 branch. So I'll do it. > > > > > On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov < > nizhi...@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > We have 13 tickets mapped to 2.7. > > > > > > All tickets assigned to some contributor. > > > > > > > > > > > > Alexey Gonchruk - IGNITE-9784, IGNITE-9895 > > > > > > Vladimir Ozerov - IGNITE-9887 > > > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > Petr Ivanov - IGNITE-9852 > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > Roman Kondakov - IGNITE-9663 > > > > > > Taras Ledkov - IGNITE-9864 > > > > > > Igor Seliverstov - IGNITE-9292 > > > > > > > > > > > > В Пн, 15/10/2018 в 17:49 +0300, Andrey Gura пишет: > > > > > > > Nikolay, > > > > > > > > > > > > > > I'm looking at IGNITE-9737 and IGNITE-9710 which are critical > > > > > > issues > > > > > > > from my point of view. > > > > > > > I need some time for review, possible fixes and merge. > > > > > > > I will keep you informed. > > > > > > > On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego < > isap...@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > > > > > Guys, Python client is in the master and ignite-2.7 already. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov < > > > > > > > > voze...@gridgain.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > AI 2.7 will include Python thin client. TC suite is crucial > > > > > > part > > > > of this > > > > > > > > > feature, so we should keep the ticket in AI 2.7 scope. > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov < > > > > > > > > nizhi...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > There is no progress till Friday. > > > > > > > > > > We have 14 tickets mapped to 2.7. > > > > > > > > > > > > > > > > > > > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет: > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > > > We made some progress yesterday. > > > > > > > > > > > > > > > > > > > > > > Please, note, we have 1 new ticket mapped to 2.7 > > > > > > > > "IGNITE-9852: Create > > > > > > > > > > > > > > > > > > > > TeamCity suite for Python thin client" > > > > > > > > > > > > > > > > > > > > > > This ticket doesn't sound like a blocker to me. Let's > > > > > > > > exclude it from > > > > > > > > > > > > > > > > > > > > release scope. > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > > > > > Here is the list of remaining tickets(14) mapped to > 2.7. > > > > > > > > > > > > > > > > > > > > > > Peter Ivanov - IGNITE-9852, IGNITE-9685, > > > > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > > > > > Igor Seliverstov - IGNITE-9749, IGNITE-9292 > > > > > > > > > > > Dmitry Melnichuk - IGNITE-7782 > > > > > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > > > > > Yury Babak - IGNITE-8670 > > > > > > > > > > > Roman Kondakov - IGNITE-7953 > > > > > > > > > > > Igor Sapego - IGNITE-9620 > > > > > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > > > > > > > > > > > > > > Unassigned: > > > > > > > > > > > > > > > > > > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX > hanging. > > > > > > > > > > > > > > > > > > > > >
Re: Applicability of term 'cache' to Apache Ignite
I'm not an ML expert, so 'dataset' term just reminds me of various client drivers to access tables from RDBM servers. For me, the only common trait of all kinds of Ignite caches is their asociativity. So if we rename them I'd suggest something like KVStore. ср, 17 окт. 2018 г. в 12:56, Alexey Zinoviev : > From my perspective, the main goal is to make easy the explanation what is > Ignite on conferences, marketing deals, in papers, in documentation. And > the > /cache/ term really reduces the area of Ignite usage in users minds. > > I don't support the critical changes in code base, but I support all > changes > that helps the goal described above in this letter. > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > -- Best regards, Andrey Kuznetsov.
Re: [DISCUSS] Dropping hadoop-accelerator download
+1 I asked a few guys, who use Ignite with Spark integration and (sometimes) IGFS, nobody use it via Hadoop Accelerator build ср, 17 окт. 2018 г. в 4:12, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > +1 from me. Hadoop Accelerator build is confusing and doesn't provide any > value. > > We already had a similar discussion couple of years back where I shared > some of my thoughts regarding this: > > http://apache-ignite-developers.2346864.n4.nabble.com/ignite-spark-module-in-Hadoop-Accelerator-td12343.html > > -Val > > On Tue, Oct 16, 2018 at 4:45 PM Dmitriy Setrakyan > wrote: > > > Igniters, > > > > I would like to suggest dropping the hadoop accelerator distribution of > > Apache Ignite. Note, that it does not mean dropping any features. We are > > still going to support IGFS, in-memory map reduce, spark integration, > etc. > > However, the hadoop-accelerator downloadable is putting extra pressure on > > the community to test and document, which can be avoided. All the > features > > will still be supported through regular Ignite distribution. > > > > Any objections? > > > > D. > > >
Re: Apache Ignite 2.7. Last Mile
Hello, Pavel. Is it a blocker? В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет: > Hi Igniters, > > I'd like to include IGNITE-9877 in 2.7, can we do that? > The fix is ready, I'm waiting for TC run. > > Pavel > > On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван wrote: > > > Hi NIkolay, > > > > Thank you for keeping everybody focused! Regarding to my ticket > > IGNITE-5935. > > It is in final stage now. Tests look good. I believe that it will be merged > > in couple of days (at most). > > > > ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov : > > > > > Hello, Igniters. > > > > > > 9 tickets to go! > > > > > > Alexey Goncharuk - IGNITE-9784 > > > Dmitriy Govorukhin - IGNITE-9898 > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > Taras Ledkov - IGNITE-9882 > > > Petr Ivanov - IGNITE-9852 > > > Ivan Pavlukhin - IGNITE-5935 > > > Roman Kondakov - IGNITE-9663 > > > Alexey Stelmak - IGNITE-9776 > > > > > > В Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет: > > > > Hi, > > > > > > > > I've found that IGNITE-9723 was resolved but didn't cherry picked to > > > > ignite-2.7 branch. So I'll do it. > > > > On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov > > > > > > wrote: > > > > > > > > > > Hello, Igniters. > > > > > > > > > > We have 13 tickets mapped to 2.7. > > > > > All tickets assigned to some contributor. > > > > > > > > > > Alexey Gonchruk - IGNITE-9784, IGNITE-9895 > > > > > Vladimir Ozerov - IGNITE-9887 > > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > Petr Ivanov - IGNITE-9852 > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > Alexey Stelmak - IGNITE-9776 > > > > > Roman Kondakov - IGNITE-9663 > > > > > Taras Ledkov - IGNITE-9864 > > > > > Igor Seliverstov - IGNITE-9292 > > > > > > > > > > В Пн, 15/10/2018 в 17:49 +0300, Andrey Gura пишет: > > > > > > Nikolay, > > > > > > > > > > > > I'm looking at IGNITE-9737 and IGNITE-9710 which are critical > > > > issues > > > > > > from my point of view. > > > > > > I need some time for review, possible fixes and merge. > > > > > > I will keep you informed. > > > > > > On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego > > > > > > wrote: > > > > > > > > > > > > > > Guys, Python client is in the master and ignite-2.7 already. > > > > > > > > > > > > > > Best Regards, > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov < > > > > > > voze...@gridgain.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > AI 2.7 will include Python thin client. TC suite is crucial > > > > part > > > of this > > > > > > > > feature, so we should keep the ticket in AI 2.7 scope. > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov < > > > > > > nizhi...@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > There is no progress till Friday. > > > > > > > > > We have 14 tickets mapped to 2.7. > > > > > > > > > > > > > > > > > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет: > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > We made some progress yesterday. > > > > > > > > > > > > > > > > > > > > Please, note, we have 1 new ticket mapped to 2.7 > > > > > > "IGNITE-9852: Create > > > > > > > > > > > > > > > > > > TeamCity suite for Python thin client" > > > > > > > > > > > > > > > > > > > > This ticket doesn't sound like a blocker to me. Let's > > > > > > exclude it from > > > > > > > > > > > > > > > > > > release scope. > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > > > Here is the list of remaining tickets(14) mapped to 2.7. > > > > > > > > > > > > > > > > > > > > Peter Ivanov - IGNITE-9852, IGNITE-9685, > > > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > > > > Igor Seliverstov - IGNITE-9749, IGNITE-9292 > > > > > > > > > > Dmitry Melnichuk - IGNITE-7782 > > > > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > > > > Yury Babak - IGNITE-8670 > > > > > > > > > > Roman Kondakov - IGNITE-7953 > > > > > > > > > > Igor Sapego - IGNITE-9620 > > > > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > > > > > > > > > > > > Unassigned: > > > > > > > > > > > > > > > > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет: > > > > > > > > > > > Alexey, we all agreed to merge in 2.7 blockers only. > > > > > > > > > > > > > > > > > > > > > > Is this a blocker? > > > > > > > > > > > > > > > > > > > > > > Anyway, you are more experienced Igniter that I am. > > > > > > > > > > > If you think we should include this ticket to 2.7 - > > > > > > please, do it. > > > > > > > > > > > > > > > > >
Re: Abbreviation code-style requirement.
+ 1 But, I think that we must leave abbreviations for common words with single meaning. For example, group -> grp, transaction -> tx, context -> ctx. ср, 17 окт. 2018 г. в 12:46, Alexey Zinoviev : > + 1 > I dislike the current list of abbreviations. It gives me a pain to support > code with unclear variables naming, also I agree that we should avoid crazy > Java camel long naming like > FactoryBuildingCrazyAffinityCallerForComibingInSpace but instead that we > make shorter clear concepts like /counter/, /vertex/, /collection/ and etc > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > -- BR, Sergey Antonov
Re: Apache Ignite 2.7. Last Mile
Hi Igniters, I'd like to include IGNITE-9877 in 2.7, can we do that? The fix is ready, I'm waiting for TC run. Pavel On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван wrote: > Hi NIkolay, > > Thank you for keeping everybody focused! Regarding to my ticket > IGNITE-5935. > It is in final stage now. Tests look good. I believe that it will be merged > in couple of days (at most). > > ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov : > > > Hello, Igniters. > > > > 9 tickets to go! > > > > Alexey Goncharuk - IGNITE-9784 > > Dmitriy Govorukhin - IGNITE-9898 > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > Taras Ledkov - IGNITE-9882 > > Petr Ivanov - IGNITE-9852 > > Ivan Pavlukhin - IGNITE-5935 > > Roman Kondakov - IGNITE-9663 > > Alexey Stelmak - IGNITE-9776 > > > > В Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет: > > > Hi, > > > > > > I've found that IGNITE-9723 was resolved but didn't cherry picked to > > > ignite-2.7 branch. So I'll do it. > > > On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov > > wrote: > > > > > > > > Hello, Igniters. > > > > > > > > We have 13 tickets mapped to 2.7. > > > > All tickets assigned to some contributor. > > > > > > > > Alexey Gonchruk - IGNITE-9784, IGNITE-9895 > > > > Vladimir Ozerov - IGNITE-9887 > > > > Dmitriy Govorukhin - IGNITE-9898 > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > Petr Ivanov - IGNITE-9852 > > > > Ivan Pavlukhin - IGNITE-5935 > > > > Alexey Stelmak - IGNITE-9776 > > > > Roman Kondakov - IGNITE-9663 > > > > Taras Ledkov - IGNITE-9864 > > > > Igor Seliverstov - IGNITE-9292 > > > > > > > > В Пн, 15/10/2018 в 17:49 +0300, Andrey Gura пишет: > > > > > Nikolay, > > > > > > > > > > I'm looking at IGNITE-9737 and IGNITE-9710 which are critical > issues > > > > > from my point of view. > > > > > I need some time for review, possible fixes and merge. > > > > > I will keep you informed. > > > > > On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego > > wrote: > > > > > > > > > > > > Guys, Python client is in the master and ignite-2.7 already. > > > > > > > > > > > > Best Regards, > > > > > > Igor > > > > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov < > > voze...@gridgain.com> > > > > > > wrote: > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > AI 2.7 will include Python thin client. TC suite is crucial > part > > of this > > > > > > > feature, so we should keep the ticket in AI 2.7 scope. > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov < > > nizhi...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > There is no progress till Friday. > > > > > > > > We have 14 tickets mapped to 2.7. > > > > > > > > > > > > > > > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет: > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > We made some progress yesterday. > > > > > > > > > > > > > > > > > > Please, note, we have 1 new ticket mapped to 2.7 > > "IGNITE-9852: Create > > > > > > > > > > > > > > > > TeamCity suite for Python thin client" > > > > > > > > > > > > > > > > > > This ticket doesn't sound like a blocker to me. Let's > > exclude it from > > > > > > > > > > > > > > > > release scope. > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > Here is the list of remaining tickets(14) mapped to 2.7. > > > > > > > > > > > > > > > > > > Peter Ivanov - IGNITE-9852, IGNITE-9685, > > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > > > Igor Seliverstov - IGNITE-9749, IGNITE-9292 > > > > > > > > > Dmitry Melnichuk - IGNITE-7782 > > > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > > > Yury Babak - IGNITE-8670 > > > > > > > > > Roman Kondakov - IGNITE-7953 > > > > > > > > > Igor Sapego - IGNITE-9620 > > > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > > > > > > > > > > Unassigned: > > > > > > > > > > > > > > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging. > > > > > > > > > > > > > > > > > > > > > > > > > > > В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет: > > > > > > > > > > Alexey, we all agreed to merge in 2.7 blockers only. > > > > > > > > > > > > > > > > > > > > Is this a blocker? > > > > > > > > > > > > > > > > > > > > Anyway, you are more experienced Igniter that I am. > > > > > > > > > > If you think we should include this ticket to 2.7 - > > please, do it. > > > > > > > > > > > > > > > > > > > > В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет: > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > > > I am waiting for final benchmark results for 9784, > after > > that I > > > > > > > > > > > > > > will > > > > > > > > merge > > > > > > > > > > > the change. > > > > > > > > > > > > > > > > > > > > > > On the subject of Ignite 2.7 scope, our fellow Igniter > > Alexey > > > > > > > > > > > > > > > > Platonov
Re: Applicability of term 'cache' to Apache Ignite
>From my perspective, the main goal is to make easy the explanation what is Ignite on conferences, marketing deals, in papers, in documentation. And the /cache/ term really reduces the area of Ignite usage in users minds. I don't support the critical changes in code base, but I support all changes that helps the goal described above in this letter. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
[GitHub] ignite pull request #5009: IGNITE-9877 .NET: Fix AmbiguousMatchException in ...
GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/5009 IGNITE-9877 .NET: Fix AmbiguousMatchException in LINQ under .NET Core 2.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-9877 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5009.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5009 commit 51d30c8f312443a5fbe5032c4018cb83a2f12381 Author: Pavel Tupitsyn Date: 2018-10-17T08:51:34Z Update ifdefs to exclude NETCOREAPP2_1 commit 15158ffaecbccd2c407d0e58e40d0695c37ae152 Author: Pavel Tupitsyn Date: 2018-10-17T08:56:14Z Ignore test instead of failing it commit 88dce6dd7f45ad9a0720ae7cb5c9d63885febeae Author: Pavel Tupitsyn Date: 2018-10-17T09:40:27Z Fix ambiguity for Contains method retrieval commit 86c473e828e6e11a94bb1c43a562f22156473dd3 Author: Pavel Tupitsyn Date: 2018-10-17T09:50:28Z cleanup ---
Re: Applicability of term 'cache' to Apache Ignite
I'm sorry, but the IgniteDataset can not be used like a basic term, due to it's ML specific term and also we have a few kind of datasets (that are not equivalents of IgniteCache/Space and etc) like IgniteDataset, PartitionBasedDataset, LocalCachedDataset and so on. Of course, we could find a dataset as a primitive in Spark (but the main reason to add this term there was a collaboration with Python - oriented data scientists) The real 'dataset' concept includes a lot of operations under the 'datasets': different math functions and etc My suggestion: IDataBucket -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Abbreviation code-style requirement.
+ 1 I dislike the current list of abbreviations. It gives me a pain to support code with unclear variables naming, also I agree that we should avoid crazy Java camel long naming like FactoryBuildingCrazyAffinityCallerForComibingInSpace but instead that we make shorter clear concepts like /counter/, /vertex/, /collection/ and etc -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
[jira] [Created] (IGNITE-9909) Merge FsyncWalManager and WalManager
Anton Kalashnikov created IGNITE-9909: - Summary: Merge FsyncWalManager and WalManager Key: IGNITE-9909 URL: https://issues.apache.org/jira/browse/IGNITE-9909 Project: Ignite Issue Type: Improvement Reporter: Anton Kalashnikov Assignee: Anton Kalashnikov Now we have two similar WAL managers FileWriteAheadLogManager and FsyncModeFileWriteAheadLogManager and because of similarity it is too difficult to support them. It is need to extract unique part from them and leave only one manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Apache Ignite 2.7. Last Mile
Hi NIkolay, Thank you for keeping everybody focused! Regarding to my ticket IGNITE-5935. It is in final stage now. Tests look good. I believe that it will be merged in couple of days (at most). ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov : > Hello, Igniters. > > 9 tickets to go! > > Alexey Goncharuk - IGNITE-9784 > Dmitriy Govorukhin - IGNITE-9898 > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > Taras Ledkov - IGNITE-9882 > Petr Ivanov - IGNITE-9852 > Ivan Pavlukhin - IGNITE-5935 > Roman Kondakov - IGNITE-9663 > Alexey Stelmak - IGNITE-9776 > > В Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет: > > Hi, > > > > I've found that IGNITE-9723 was resolved but didn't cherry picked to > > ignite-2.7 branch. So I'll do it. > > On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov > wrote: > > > > > > Hello, Igniters. > > > > > > We have 13 tickets mapped to 2.7. > > > All tickets assigned to some contributor. > > > > > > Alexey Gonchruk - IGNITE-9784, IGNITE-9895 > > > Vladimir Ozerov - IGNITE-9887 > > > Dmitriy Govorukhin - IGNITE-9898 > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > Petr Ivanov - IGNITE-9852 > > > Ivan Pavlukhin - IGNITE-5935 > > > Alexey Stelmak - IGNITE-9776 > > > Roman Kondakov - IGNITE-9663 > > > Taras Ledkov - IGNITE-9864 > > > Igor Seliverstov - IGNITE-9292 > > > > > > В Пн, 15/10/2018 в 17:49 +0300, Andrey Gura пишет: > > > > Nikolay, > > > > > > > > I'm looking at IGNITE-9737 and IGNITE-9710 which are critical issues > > > > from my point of view. > > > > I need some time for review, possible fixes and merge. > > > > I will keep you informed. > > > > On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego > wrote: > > > > > > > > > > Guys, Python client is in the master and ignite-2.7 already. > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov < > voze...@gridgain.com> > > > > > wrote: > > > > > > > > > > > Nikolay, > > > > > > > > > > > > AI 2.7 will include Python thin client. TC suite is crucial part > of this > > > > > > feature, so we should keep the ticket in AI 2.7 scope. > > > > > > > > > > > > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov < > nizhi...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > There is no progress till Friday. > > > > > > > We have 14 tickets mapped to 2.7. > > > > > > > > > > > > > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет: > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > We made some progress yesterday. > > > > > > > > > > > > > > > > Please, note, we have 1 new ticket mapped to 2.7 > "IGNITE-9852: Create > > > > > > > > > > > > > > TeamCity suite for Python thin client" > > > > > > > > > > > > > > > > This ticket doesn't sound like a blocker to me. Let's > exclude it from > > > > > > > > > > > > > > release scope. > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > Here is the list of remaining tickets(14) mapped to 2.7. > > > > > > > > > > > > > > > > Peter Ivanov - IGNITE-9852, IGNITE-9685, > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > > Igor Seliverstov - IGNITE-9749, IGNITE-9292 > > > > > > > > Dmitry Melnichuk - IGNITE-7782 > > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > > Yury Babak - IGNITE-8670 > > > > > > > > Roman Kondakov - IGNITE-7953 > > > > > > > > Igor Sapego - IGNITE-9620 > > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > > > > > > > > Unassigned: > > > > > > > > > > > > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging. > > > > > > > > > > > > > > > > > > > > > > > > В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет: > > > > > > > > > Alexey, we all agreed to merge in 2.7 blockers only. > > > > > > > > > > > > > > > > > > Is this a blocker? > > > > > > > > > > > > > > > > > > Anyway, you are more experienced Igniter that I am. > > > > > > > > > If you think we should include this ticket to 2.7 - > please, do it. > > > > > > > > > > > > > > > > > > В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет: > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > I am waiting for final benchmark results for 9784, after > that I > > > > > > > > > > > > will > > > > > > > merge > > > > > > > > > > the change. > > > > > > > > > > > > > > > > > > > > On the subject of Ignite 2.7 scope, our fellow Igniter > Alexey > > > > > > > > > > > > > > Platonov have > > > > > > > > > > found another case when a failure handler is incorrectly > called on > > > > > > > > > > > > > > node > > > > > > > > > > stop: https://issues.apache.org/jira/browse/IGNITE-9834. > The case > > > > > > > > > > > > > > is rare, > > > > > > > > > > but it is quite an unpleasant UX. Should we include it > to 2.7 as > > > > > > > > > > > > > > well? > > > > > > > > > > > > > > > > > > > > чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov
Re: Apache Ignite 2.7. Last Mile
Hello, Igniters. 9 tickets to go! Alexey Goncharuk - IGNITE-9784 Dmitriy Govorukhin - IGNITE-9898 Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 Taras Ledkov - IGNITE-9882 Petr Ivanov - IGNITE-9852 Ivan Pavlukhin - IGNITE-5935 Roman Kondakov - IGNITE-9663 Alexey Stelmak - IGNITE-9776 В Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет: > Hi, > > I've found that IGNITE-9723 was resolved but didn't cherry picked to > ignite-2.7 branch. So I'll do it. > On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov wrote: > > > > Hello, Igniters. > > > > We have 13 tickets mapped to 2.7. > > All tickets assigned to some contributor. > > > > Alexey Gonchruk - IGNITE-9784, IGNITE-9895 > > Vladimir Ozerov - IGNITE-9887 > > Dmitriy Govorukhin - IGNITE-9898 > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > Petr Ivanov - IGNITE-9852 > > Ivan Pavlukhin - IGNITE-5935 > > Alexey Stelmak - IGNITE-9776 > > Roman Kondakov - IGNITE-9663 > > Taras Ledkov - IGNITE-9864 > > Igor Seliverstov - IGNITE-9292 > > > > В Пн, 15/10/2018 в 17:49 +0300, Andrey Gura пишет: > > > Nikolay, > > > > > > I'm looking at IGNITE-9737 and IGNITE-9710 which are critical issues > > > from my point of view. > > > I need some time for review, possible fixes and merge. > > > I will keep you informed. > > > On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego wrote: > > > > > > > > Guys, Python client is in the master and ignite-2.7 already. > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov > > > > wrote: > > > > > > > > > Nikolay, > > > > > > > > > > AI 2.7 will include Python thin client. TC suite is crucial part of > > > > > this > > > > > feature, so we should keep the ticket in AI 2.7 scope. > > > > > > > > > > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov > > > > > wrote: > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > There is no progress till Friday. > > > > > > We have 14 tickets mapped to 2.7. > > > > > > > > > > > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет: > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > We made some progress yesterday. > > > > > > > > > > > > > > Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: > > > > > > > Create > > > > > > > > > > > > TeamCity suite for Python thin client" > > > > > > > > > > > > > > This ticket doesn't sound like a blocker to me. Let's exclude it > > > > > > > from > > > > > > > > > > > > release scope. > > > > > > > Thoughts? > > > > > > > > > > > > > > Here is the list of remaining tickets(14) mapped to 2.7. > > > > > > > > > > > > > > Peter Ivanov - IGNITE-9852, IGNITE-9685, > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > > Andrey Kuznetsov - IGNITE-9737, IGNITE-9710 > > > > > > > Igor Seliverstov - IGNITE-9749, IGNITE-9292 > > > > > > > Dmitry Melnichuk - IGNITE-7782 > > > > > > > Ivan Pavlukhin - IGNITE-5935 > > > > > > > Yury Babak - IGNITE-8670 > > > > > > > Roman Kondakov - IGNITE-7953 > > > > > > > Igor Sapego - IGNITE-9620 > > > > > > > Alexey Stelmak - IGNITE-9776 > > > > > > > > > > > > > > Unassigned: > > > > > > > > > > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging. > > > > > > > > > > > > > > > > > > > > > В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет: > > > > > > > > Alexey, we all agreed to merge in 2.7 blockers only. > > > > > > > > > > > > > > > > Is this a blocker? > > > > > > > > > > > > > > > > Anyway, you are more experienced Igniter that I am. > > > > > > > > If you think we should include this ticket to 2.7 - please, do > > > > > > > > it. > > > > > > > > > > > > > > > > В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет: > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > I am waiting for final benchmark results for 9784, after that > > > > > > > > > I > > > > > > > > > > will > > > > > > merge > > > > > > > > > the change. > > > > > > > > > > > > > > > > > > On the subject of Ignite 2.7 scope, our fellow Igniter Alexey > > > > > > > > > > > > Platonov have > > > > > > > > > found another case when a failure handler is incorrectly > > > > > > > > > called on > > > > > > > > > > > > node > > > > > > > > > stop: https://issues.apache.org/jira/browse/IGNITE-9834. The > > > > > > > > > case > > > > > > > > > > > > is rare, > > > > > > > > > but it is quite an unpleasant UX. Should we include it to 2.7 > > > > > > > > > as > > > > > > > > > > > > well? > > > > > > > > > > > > > > > > > > чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov > > > > > > > > > > > > > > > > > > > > : > > > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > We made a good progress yesterday. > > > > > > > > > > > > > > > > > > > > Here is the list of remaining tickets(17) mapped to 2.7: > > > > > > > > > > > > > > > > > > > > Alexey Goncharuk - IGNITE-9784 > > > > > > > > > > Taras Ledkov -
Re: Python thin client
Dmitry, I've trying to use python thin client with Ignite 2.7 it dosn't work Please help to investigate Problem reproduced on several others machines Issue: https://issues.apache.org/jira/browse/IGNITE-9908 вт, 16 окт. 2018 г. в 4:36, Dmitry Melnichuk : > Igor, > > I do not have access to edit wiki pages, so please fill it. > > All the features are supported, except for: > > - Query API: ScanQuery with filter, > - Binary API: Get object in BinaryObject form, BinaryObject building, > - Additional Features: Best effort affinity, > - Type registration: Enum registration, Type name registration. > > On 10/15/18 9:17 PM, Igor Sapego wrote: > > Dmitry, > > > > Since Python thin client is now in master, can you please add it to our > > "Thin clients features" wiki page, so we can track the feature parity > > of our clients? Or just tell me which features are supported, so I can > fill > > it myself. > > > > [1] - > > https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features > > > > Best Regards, > > Igor > > >
[jira] [Created] (IGNITE-9908) thin python: Can't use client with windows
Stepan Pilschikov created IGNITE-9908:
-
Summary: thin python: Can't use client with windows
Key: IGNITE-9908
URL: https://issues.apache.org/jira/browse/IGNITE-9908
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.7
Environment: Windows 10 1803
Python 3.7
Client module installed from latest sources, branch - master
Ignite compiled from latest sources
Reporter: Stepan Pilschikov
Trying to use thin python client on Windows and have exception
Python excetion:
{code}
Traceback (most recent call last):
File "C:\dev\test\put_value.py", line 5, in
cache = client.get_or_create_cache("test_3")
File "[ignite path]\platforms\python\pyignite\client.py", line 306, in
get_or_create_cache
return Cache(self, settings, with_get=True)
File "[ignite path]\platforms\python\pyignite\cache.py", line 116, in __init__
result = func(client, settings)
File "[ignite path]\platforms\python\pyignite\api\cache_config.py", line 151,
in cache_get_or_create
'cache_name': name,
File "[ignite path]\platforms\python\pyignite\queries\__init__.py", line 287,
in perform
response_ctype, recv_buffer = response_struct.parse(conn)
File "[ignite path]\platforms\python\pyignite\queries\__init__.py", line 66,
in parse
buffer = client.recv(ctypes.sizeof(header_class))
File "[ignite path]\platforms\python\pyignite\connection\__init__.py", line
292, in recv
result += self._recv(buffersize-pref_size, flags)
File "[ignite path]\platforms\python\pyignite\connection\__init__.py", line
316, in _recv
raise SocketError('Socket connection broken.')
OSError: Socket connection broken.
{code}
In ignite logs:
{code}
[11:19:20,522][SEVERE][client-connector-#47][ClientListenerNioListener] Failed
to parse client request.
class org.apache.ignite.binary.BinaryObjectException: Unexpected field type
[pos=10, expected=String, actual=0]
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlagNoHandles(BinaryReaderExImpl.java:1679)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.readString(BinaryReaderExImpl.java:1057)
at
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheGetOrCreateWithNameRequest.(ClientCacheGetOrCreateWithNameRequest.java:41)
at
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:342)
at
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:238)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:140)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:45)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
Python code:
{code}
from pyignite import Client
client = Client()
client.connect('127.0.0.1', 10800)
cache = client.get_or_create_cache("test_3")
cache.put("key3", -3.3)
{code}
All others thin clients from same sources and on the same ignite binary works
well
On linux from same sources python client works well too
Troubles only with python and windows
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
