[GitHub] ignite pull request #5439: IGNITE-10238

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/5439 IGNITE-10238 Fix possible deadlock of system threads. You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite ignite-10238

[GitHub] ignite pull request #5400: IGNITE-10192 OptimizedMarshallerTest#testAllocati...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5400 ---

[GitHub] ignite pull request #5404: IGNITE-10285 Implement job stealing for U.doInPar...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5404 ---

[GitHub] ignite pull request #5410: IGNITE-10197 unexpected IllegalArgumentException ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5410 ---

[GitHub] ignite pull request #5379: IGNITE-10098 TcpCommunicationSpi for .NET misses ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5379 ---

[GitHub] ignite pull request #5253: IGNITE-10142 Cache 8 tests optimization

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5253 ---

[GitHub] ignite pull request #4933: IGNITE-9558

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4933 ---

[GitHub] ignite pull request #5427: IGNITE-10321 Bug in CacheContinuousWithTransforme...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5427 ---

[GitHub] ignite pull request #5440: IGNITE-9339 Form-field-size improvements

GitHub user Klaster1 opened a pull request: https://github.com/apache/ignite/pull/5440 IGNITE-9339 Form-field-size improvements @nva please review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #5440: IGNITE-9339 Form-field-size improvements

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5440 ---

[jira] [Created] (IGNITE-10338) Add Disk page compression test suites to TC

Sergi Vladykin created IGNITE-10338: --- Summary: Add Disk page compression test suites to TC Key: IGNITE-10338 URL: https://issues.apache.org/jira/browse/IGNITE-10338 Project: Ignite Issue

Re: [IMPORTANT] Future of Binary Objects

Do we discuss here Core features only or the roadmap for all components? вт, 20 нояб. 2018 г. в 10:05, Vladimir Ozerov : > Igniters, > > It is very likely that Apache Ignite 3.0 will be released next year. So we > need to start thinking about major product improvements. I'd like to start > with

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

Hi, this is an intentionally failed test with a ticket, I've now muted it on TC. вт, 20 нояб. 2018 г. в 07:38, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your changes can lead to this failure(s): We're grateful that

Re: [IMPORTANT] Future of Binary Objects

Hi Alexey, Binary Objects only. On Tue, Nov 20, 2018 at 10:50 AM Alexey Zinoviev wrote: > Do we discuss here Core features only or the roadmap for all components? > > вт, 20 нояб. 2018 г. в 10:05, Vladimir Ozerov : > > > Igniters, > > > > It is very likely that Apache Ignite 3.0 will be

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

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

Re: Disk page compression for Ignite persistent store

Denis, See inline. пн, 19 нояб. 2018 г. в 20:17, Denis Magda : > Hi Sergi, > > Didn't know you were cooking this dish in the background ) Excellent. Just > to be sure, that's part of this IEP, right? > >

Re: Network partitioning

Hi, Ignite comes with partition loss policies that might be useful: https://apacheignite.readme.io/docs/partition-loss-policies As for the network segmentation, check out GridGain that provides this for Ignite users. Denis On Sat, Nov 17, 2018 at 7:39 AM Vj Anand wrote: > Hi Ignite

[IMPORTANT] Future of Binary Objects

Igniters, It is very likely that Apache Ignite 3.0 will be released next year. So we need to start thinking about major product improvements. I'd like to start with binary objects. Currently they are one of the main limiting factors for the product. They are fat - 30+ bytes overhead on average,

Rename "cache group" to "tablespace"?

Igniters, We had several discussion about cache groups [1]. Our current consensus is that this is not that good design decision - bad scan performance, no API. A kind of shortcut to solve memory consumption problems. For this reason we try to avoid exposing "cache group" to API when possible.

Re: Rename "cache group" to "tablespace"?

I really like the idea. On Mon, Nov 19, 2018, 23:45 Vladimir Ozerov Igniters, > > We had several discussion about cache groups [1]. Our current consensus is > that this is not that good design decision - bad scan performance, no API. > A kind of shortcut to solve memory consumption problems. For

Re: Apache Ignite 2.7. Last Mile

Hello, Dmitrii. I see 2 tickets for this improvement: IGNITE-602 - [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion [1] IGNITE-9209 - GridDistributedTxMapping.toString() returns broken string [2] Should we revert both commits? [1]

[GitHub] ignite pull request #5424: GG PE 2.7.1

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/5424 GG PE 2.7.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.7.1 Alternatively you can review and apply

[jira] [Created] (IGNITE-10317) “Failed to do service reassignment” on server stop with singleton service

Grigory Domozhirov created IGNITE-10317: --- Summary: “Failed to do service reassignment” on server stop with singleton service Key: IGNITE-10317 URL: https://issues.apache.org/jira/browse/IGNITE-10317

[GitHub] ignite pull request #2476: Ignite-5983: Memory policy metrics should be avai...

Github user shroman closed the pull request at: https://github.com/apache/ignite/pull/2476 ---

[jira] [Created] (IGNITE-10318) Web console: use newer panels in query notebook screen

Ilya Borisov created IGNITE-10318: - Summary: Web console: use newer panels in query notebook screen Key: IGNITE-10318 URL: https://issues.apache.org/jira/browse/IGNITE-10318 Project: Ignite

[GitHub] ololo3000 opened a new pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix.

ololo3000 opened a new pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix. URL: https://github.com/apache/ignite-teamcity-bot/pull/74 This is an automated message from the Apache Git Service. To respond

Schema in CacheConfig is not updated after DDL commands(Add/drop column, Create/drop index)

When user performs column and index modification operation in SQL(ex create index, drop index, add column, drop column), QueryEntity in CacheConfiguration for the modified cache is not updated. Here's my analysis QueryEntity in QuerySchema is a local copy of the original QueryEntity, so the

Re: Schema in CacheConfig is not updated after DDL commands(Add/drop column, Create/drop index)

Hi, In this case Spark integration should be fixed. as we never stated that DDL updates will be reflected in IgniteCache.getConfiguration(). On Mon, Nov 19, 2018 at 11:58 AM Ray wrote: > When user performs column and index modification operation in SQL(ex create > index, drop index, add

[GitHub] ignite pull request #5425: IGNITE-10300 Fixed correct message in case of use...

GitHub user voropava opened a pull request: https://github.com/apache/ignite/pull/5425 IGNITE-10300 Fixed correct message in case of user/password retries e… …xceeded. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-10320) Web Console: Memory leak in char component

Alexey Kuznetsov created IGNITE-10320: - Summary: Web Console: Memory leak in char component Key: IGNITE-10320 URL: https://issues.apache.org/jira/browse/IGNITE-10320 Project: Ignite

[jira] [Created] (IGNITE-10319) Handle suite compilation error failure

PetrovMikhail created IGNITE-10319: -- Summary: Handle suite compilation error failure Key: IGNITE-10319 URL: https://issues.apache.org/jira/browse/IGNITE-10319 Project: Ignite Issue Type:

[GitHub] ignite pull request #5422: IGNITE-10314 QueryEntity is not updated when colu...

Github user ldzhjn closed the pull request at: https://github.com/apache/ignite/pull/5422 ---

Spark dataframe API will get wrong schema if user executes add/drop column DDL

Currently, when user performs add/remove column DDL, the QueryEntity will not change. This result in Spark getting wrong schema because Spark relies on QueryEntity to construct data frame schema. In Vladimir Ozerov's reply in dev list,

Disk page compression for Ignite persistent store

Folks, I've implemented page compression for persistent store and going to merge it to master. https://github.com/apache/ignite/pull/5200 Some design notes: It employs "hole punching" approach, it means that the pages are kept uncompressed in memory, but when they get written to disk, they

Re: Apache Ignite 2.7. Last Mile

I agree to revert and make fix for 2.8. So, we will have more time to test it. пн, 19 нояб. 2018 г., 10:53 Vladimir Ozerov voze...@gridgain.com: > +1 for revert. > > On Sun, Nov 18, 2018 at 11:31 PM Dmitriy Pavlov > wrote: > > > I personally don't mind. > > > > But I would like Dmitry Ryabov

Re: Disk page compression for Ignite persistent store

Hi Sergi, It is not clear for me will your changes affect PageSnapshot WAL record. Is it possible to add compression support for PageSnapshot WAL record as well, to reduce WAL size? Thanks. On Mon, Nov 19, 2018 at 1:01 PM Sergi Vladykin wrote: > Folks, > > I've implemented page compression

Re: Disk page compression for Ignite persistent store

Right now the functionality has nothing to do with WAL, but your idea definitely makes sense and worth being implemented as a next step. Sergi пн, 19 нояб. 2018 г. в 13:58, Andrey Mashenkov : > Hi Sergi, > > It is not clear for me will your changes affect PageSnapshot WAL record. > Is it

Re: Brainstorm: Make TC Run All faster

Hi, I would like to understand following. We are going to make TC green. We are going to make TC fast. Are we going to do it in parallel? пн, 19 нояб. 2018 г. в 08:39, Petr Ivanov : > > Concerning current TeamCity compute capacity — I think we should invest into > it’s stability at first: there

Re: Disk page compression for Ignite persistent store

Hello! You have zstd default level of 3. In my tests, zstd usually performed much better with compression level 2. Please consider. I admire your effort! Regards, -- Ilya Kasnacheev пн, 19 нояб. 2018 г. в 14:02, Sergi Vladykin : > Right now the functionality has nothing to do with WAL, but

[GitHub] ignite pull request #5426: IGNITE-9996: Final fix

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/5426 IGNITE-9996: Final fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-9996-2.7-final-fix Alternatively you can

[jira] [Created] (IGNITE-10321) Bug CacheContinuousWithTransformerReplicatedSelfTest.LocalEventListener causes certain tests to flack.

Ivan Bessonov created IGNITE-10321: -- Summary: Bug CacheContinuousWithTransformerReplicatedSelfTest.LocalEventListener causes certain tests to flack. Key: IGNITE-10321 URL:

[GitHub] ignite pull request #5427: IGNITE-10321 Bug in CacheContinuousWithTransforme...

GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/5427 IGNITE-10321 Bug in CacheContinuousWithTransformerReplicatedSelfTest.LocalEventListener causes certain tests to flak. You can merge this pull request into a Git repository by running: $

[jira] [Created] (IGNITE-10322) MVCC TX: Clean out messages.

Igor Seliverstov created IGNITE-10322: - Summary: MVCC TX: Clean out messages. Key: IGNITE-10322 URL: https://issues.apache.org/jira/browse/IGNITE-10322 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-10323) Contol utility --deactivate on non-activate cluster produse NPE and handler stop nodes

ARomantsov created IGNITE-10323: --- Summary: Contol utility --deactivate on non-activate cluster produse NPE and handler stop nodes Key: IGNITE-10323 URL: https://issues.apache.org/jira/browse/IGNITE-10323

[GitHub] SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix.

SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix. URL: https://github.com/apache/ignite-teamcity-bot/pull/74#discussion_r234597233 ## File path:

[GitHub] SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix.

SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix. URL: https://github.com/apache/ignite-teamcity-bot/pull/74#discussion_r234600605 ## File path:

[GitHub] SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix.

SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix. URL: https://github.com/apache/ignite-teamcity-bot/pull/74#discussion_r234598100 ## File path:

[GitHub] SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix.

SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix. URL: https://github.com/apache/ignite-teamcity-bot/pull/74#discussion_r234602866 ## File path:

[GitHub] SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix.

SomeFire commented on a change in pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix. URL: https://github.com/apache/ignite-teamcity-bot/pull/74#discussion_r234601602 ## File path:

[GitHub] ololo3000 opened a new pull request #75: IGNITE-10319 Suite compilation error failure handling added

ololo3000 opened a new pull request #75: IGNITE-10319 Suite compilation error failure handling added URL: https://github.com/apache/ignite-teamcity-bot/pull/75 This is an automated message from the Apache Git Service. To

[jira] [Created] (IGNITE-10324) Disallow fallback to Scanner in control.sh when asking password

Pavel Voronkin created IGNITE-10324: --- Summary: Disallow fallback to Scanner in control.sh when asking password Key: IGNITE-10324 URL: https://issues.apache.org/jira/browse/IGNITE-10324 Project:

[jira] [Created] (IGNITE-10325) Spark Data Frame - Thin Client

Nikolay Izhikov created IGNITE-10325: Summary: Spark Data Frame - Thin Client Key: IGNITE-10325 URL: https://issues.apache.org/jira/browse/IGNITE-10325 Project: Ignite Issue Type:

Re: [DISCUSSION] Spark Data Frame through Thin Client

IGNITE-10325 created. ср, 7 нояб. 2018 г., 11:42 Ray ray...@cisco.com: > From my past experience with Spark Data Frame API, the thick client > approach > leads to many usability problems. > > Ex. > >

[GitHub] ignite pull request #5428: IGNITE-10298 Fixed deadlock during checkpointer a...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5428 IGNITE-10298 Fixed deadlock during checkpointer and caches start for 2.4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #5429: ignite-8432: Test for column name case in PK and ...

GitHub user pavel-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/5429 ignite-8432: Test for column name case in PK and CREATE TABLE. Although, bug have been fixed during IGNITE-8052, added test for this special case: primary keys list is case sensitive;

[GitHub] ignite pull request #4837: IGNITE-8717

Github user antonovsergey93 closed the pull request at: https://github.com/apache/ignite/pull/4837 ---

[jira] [Created] (IGNITE-10326) Add trusted suites

PetrovMikhail created IGNITE-10326: -- Summary: Add trusted suites Key: IGNITE-10326 URL: https://issues.apache.org/jira/browse/IGNITE-10326 Project: Ignite Issue Type: Task

Re: Disk page compression for Ignite persistent store

Ilya, Zstd itself has default compression level 3. I just used that number to be consistent with the library defaults. I will check if there is a significant difference in performance. Sergi пн, 19 нояб. 2018 г. в 14:59, Ilya Kasnacheev : > Hello! > > You have zstd default level of 3. In my

[GitHub] ignite pull request #5430: IGNITE-9872 [Test falied] IgniteSinkConnectorTest...

GitHub user Max-Pudov opened a pull request: https://github.com/apache/ignite/pull/5430 IGNITE-9872 [Test falied] IgniteSinkConnectorTest.testSinkPutsWithout… …Transformation (updating Kafka to 2.0.1) You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (IGNITE-10327) Claster take NPE due cache stop and stop by handler

ARomantsov created IGNITE-10327: --- Summary: Claster take NPE due cache stop and stop by handler Key: IGNITE-10327 URL: https://issues.apache.org/jira/browse/IGNITE-10327 Project: Ignite Issue

[jira] [Created] (IGNITE-10328) Allow to destroy cache in code which were created via SQL

Eduard Shangareev created IGNITE-10328: -- Summary: Allow to destroy cache in code which were created via SQL Key: IGNITE-10328 URL: https://issues.apache.org/jira/browse/IGNITE-10328 Project:

[jira] [Created] (IGNITE-10329) Create JDBC "query" and "query join" benchmarks and compare them with Postgres and MySQL

Vladimir Ozerov created IGNITE-10329: Summary: Create JDBC "query" and "query join" benchmarks and compare them with Postgres and MySQL Key: IGNITE-10329 URL:

[jira] [Created] (IGNITE-10330) Implement disk page compression

Sergi Vladykin created IGNITE-10330: --- Summary: Implement disk page compression Key: IGNITE-10330 URL: https://issues.apache.org/jira/browse/IGNITE-10330 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-10331) Document Disk page compression

Sergi Vladykin created IGNITE-10331: --- Summary: Document Disk page compression Key: IGNITE-10331 URL: https://issues.apache.org/jira/browse/IGNITE-10331 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-10332) Add Ignite.NET configuration for disk page compression

Sergi Vladykin created IGNITE-10332: --- Summary: Add Ignite.NET configuration for disk page compression Key: IGNITE-10332 URL: https://issues.apache.org/jira/browse/IGNITE-10332 Project: Ignite

[jira] [Created] (IGNITE-10333) CPP: Move to newer C++ standard and drop VS 2010 support

Igor Sapego created IGNITE-10333: Summary: CPP: Move to newer C++ standard and drop VS 2010 support Key: IGNITE-10333 URL: https://issues.apache.org/jira/browse/IGNITE-10333 Project: Ignite

Re: Update our C++ library to C++11 standard

I've filed a ticket for this task [1]. [1] - https://issues.apache.org/jira/browse/IGNITE-10333 Best Regards, Igor On Mon, Nov 12, 2018 at 1:39 PM Igor Sapego wrote: > Vladimir, > > I'd wish we could do that, but unfortunately, even VS 2017 does not > support all C++11 (and even C++03)

[GitHub] ignite pull request #5431: Ignite 10328

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/5431 Ignite 10328 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10328 Alternatively you can review and apply

Re: Time to remove automated messages from the devlist?

Dmitriy, If a person wants to track all new tickets, then he may go to JIRA, create a filter for Ignite tickets and subscribe to it. JIRA has a pretty flexible configuration of filters and subscriptions, so you can specify exactly what issues you are interested in, and how often you want to

Re: Time to remove automated messages from the devlist?

Denis, we need because contributors do not announce their intent/designs/etc manually. It is the best way ever? No, of course. We have consensus on PR removal, so let's do it and see results. пн, 19 нояб. 2018 г. в 18:11, Denis Mekhanikov : > Dmitriy, > > If a person wants to track all new

[GitHub] ignite pull request #5432: Ignite 2.5.1 p160

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/5432 Ignite 2.5.1 p160 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p160 Alternatively you can

proposed realization KILL QUERY command

Hi Igniters, Earlier we agreed about syntax KILL QUERY '[node_order].[query_counter]', e.g. KILL QUERY '25.123' for single query or KILL QUERY '25.*' for all queries on the node. Which is part of IEP-29

[GitHub] ignite pull request #5433: IGNITE-10044 Proper LOST partitions handling

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5433 IGNITE-10044 Proper LOST partitions handling You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10044

Re: Schema in CacheConfig is not updated after DDL commands(Add/drop column, Create/drop index)

Vladimir, What is the best way to get current schema information (list of tables, columns, etc.)? -Val On Mon, Nov 19, 2018 at 1:21 AM Vladimir Ozerov wrote: > Hi, > > In this case Spark integration should be fixed. as we never stated that DDL > updates will be reflected in

Re: Schema in CacheConfig is not updated after DDL commands(Add/drop column, Create/drop index)

There is no public API currently. This information can be extracted using JDBC metadata requests. On Mon, Nov 19, 2018 at 6:50 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Vladimir, > > What is the best way to get current schema information (list of tables, > columns, etc.)?

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Guys, Syntax like *KILL QUERY '25.1234'* look a bit cryptic to me. I'm going to look up in documentation, which parameter goes first in this query every time I use it. I like the syntax, that Igor suggested more. Will it be better if we make *nodeId* and *queryId *named properties? Something

[jira] [Created] (IGNITE-10334) XAException not causing a rollback exception to propagate to application server

Dionysis Stavropoulos created IGNITE-10334: -- Summary: XAException not causing a rollback exception to propagate to application server Key: IGNITE-10334 URL:

[jira] [Created] (IGNITE-10335) move ML examples datasets files to resources

Oleg Ignatenko created IGNITE-10335: --- Summary: move ML examples datasets files to resources Key: IGNITE-10335 URL: https://issues.apache.org/jira/browse/IGNITE-10335 Project: Ignite Issue

Re: proposed realization KILL QUERY command

Hi Yuriy, I think we can use MANAGEMENT_POOL for this. It is already used for some internal Ignite tasks, and it appears to be a good candidate to process cancel requests. But there are several things which are not clear enough for me at the moment: 1) How user is going to get the list of

[GitHub] ignite pull request #5420: for tests

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/5420 ---

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

I can't reproduce this tests locally, also the test is successful on TC in last two days. Looks like the failure relates to an engine of .NET Core platform because the test passes without failures at .NET framework [1] in comparison to .NET Core [2]. [1]

Re: Disk page compression for Ignite persistent store

Hi Sergi, Didn't know you were cooking this dish in the background ) Excellent. Just to be sure, that's part of this IEP, right? https://cwiki.apache.org/confluence/display/IGNITE/IEP-20%3A+Data+Compression+in+Ignite#IEP-20:DataCompressioninIgnite-Withoutin-memorycompression Since we can

[GitHub] ignite pull request #5435: temporary PR to verify renamed tests on Teamcity ...

GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/5435 temporary PR to verify renamed tests on Teamcity for review of 10174 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #5434: IGNITE-10335 move ML examples datasets files to r...

GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/5434 IGNITE-10335 move ML examples datasets files to resources You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-10337) [TC Bot] Test ticket

PetrovMikhail created IGNITE-10337: -- Summary: [TC Bot] Test ticket Key: IGNITE-10337 URL: https://issues.apache.org/jira/browse/IGNITE-10337 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #5438: Tde with fixes

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/5438 Tde with fixes You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite TDE-with-fixes Alternatively you can review and apply these

[GitHub] ignite pull request #5437: Ignite 2.4.8 p7 test

GitHub user aealeksandrov opened a pull request: https://github.com/apache/ignite/pull/5437 Ignite 2.4.8 p7 test For team city run only. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.8-p7-test

[GitHub] ignite pull request #5436: IGNITE-10043 Do not reset LOST partitions when on...

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5436 IGNITE-10043 Do not reset LOST partitions when only one node is left in a cluster You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-10336) [TC Bot] Running build can cause bot to think there are no failures

Dmitriy Pavlov created IGNITE-10336: --- Summary: [TC Bot] Running build can cause bot to think there are no failures Key: IGNITE-10336 URL: https://issues.apache.org/jira/browse/IGNITE-10336 Project:

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Hi Denis, It's not a problem, the full query id could be get from additional column from *running_queries* view. So you may not known real meaning of each of part of the string to use it. Is it works? пн, 19 нояб. 2018 г. в 19:02, Denis Mekhanikov : > Guys, > > Syntax like *KILL QUERY

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Denis, I partially agree with you. But there are several problem with syntax proposed by you: 1) This is harder to implement technically - more parsing logic to implement. Ok, this is our internal problem, users do not care about it 2) User will have to consult to docs in any case 3) "nodeId" is

[GitHub] asfgit closed pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix.

asfgit closed pull request #74: IGNITE-10275 Refactor of visa caching. Jira spam fix. URL: https://github.com/apache/ignite-teamcity-bot/pull/74 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As