Re: supporting different configuration format json,yaml...

Dmitriy, We don't need to support different config formats on server in order to add that to thin clients. Thin client protocol provides a way to create a cache with custom config [1]. It is up to thin client library authors to use any config format they like and then convert it into

Re: SqlLine script and Java9

Not yet. After 2.5 release, I plan to prepare a roadmap for Apache Ignite support of future Java releases (based on their’s current release cycle) and to coordinate corresponding works for introducing support of future Java versions. > On 15 May 2018, at 01:55, Dmitriy Setrakyan

Re: Topology-wide notification on critical errors

Ilya, adding of message that will be sent to all other nodes still doesn't make mentioned task easier. You still should understand where to find problem description and what exactly. Only helpful case here is using NoOpFailureHandler because node can just hang but still be in topology so any

Re: abbrevation rules plugin

I'd like to thank GridGain's engineers for the plugin's donation. I believe that the plugin will help Ignite's developers prepare PR with the higher quality of code style what will reduce reviewer's time for PR checking. Dmitry thank you for the task's pushing! On Mon, May 14, 2018 at 7:27 PM,

Re: supporting different configuration format json,yaml...

Actually sometimes users ask about JSON configuration (e.g. was PR in vertx-ignite project). But it's non trivial task because it will require development of some DSL (or set of DSL's) and will make adding new configuration elements some kind of pain while we should be focused on basic

Re: One more round for PR review

Hi Alexey, thank you for review. Hi Igor, could you please merge this PR? вт, 15 мая 2018 г. в 11:18, Alexey Kuznetsov : > Looks good for me now. > > On Tue, May 15, 2018 at 12:38 AM, Dmitry Pavlov > wrote: > > > Hi Alexey K, > > > > could you

[jira] [Created] (IGNITE-8495) CPP Thin: Implement thin client start and connection establishment

Igor Sapego created IGNITE-8495: --- Summary: CPP Thin: Implement thin client start and connection establishment Key: IGNITE-8495 URL: https://issues.apache.org/jira/browse/IGNITE-8495 Project: Ignite

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Done. Alexander, Alexey, Dmitriy, thank you. вт, 15 мая 2018 г. в 13:29, Dmitriy Govorukhin : > Dmitriy, > > Looks good for me please merge. > > On Tue, May 15, 2018 at 11:20 AM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > >> Dmitriy, >> >> Ok, I

Re: [jira] [Created] (IGNITE-8497) Ignite stops the node in the middle of checkpointing upon receiving a SIGINT

HI Ivan R. , I understand now, thank you. Probably we could use title "Ignite triggers checkpoint upon receiving a SIGINT even if it not required" вт, 15 мая 2018 г. в 16:08, Ivan Rakov : > It's a regular priority bug and should be fixed. > Issue doesn't cause any kind of

Re: supporting different configuration format json,yaml...

Hello! Maybe we should take .Net configuration as a standard, extend it to JSON and YAML? https://apacheignite-net.readme.io/docs/configuration It should be fairly robust, and there's much less boilerplate. Regards, -- Ilya Kasnacheev 2018-05-15 16:09 GMT+03:00 Pavel Kovalenko

[GitHub] ignite pull request #4000: tickTime was tuned in attempt to fix tests instab...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4000 tickTime was tuned in attempt to fix tests instability on TC You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8499) validate_indexes command doesn't detect absent rows in cache data tree

Ivan Rakov created IGNITE-8499: -- Summary: validate_indexes command doesn't detect absent rows in cache data tree Key: IGNITE-8499 URL: https://issues.apache.org/jira/browse/IGNITE-8499 Project: Ignite

[GitHub] ignite pull request #3959: IGNITE-8446 Ability to check and completely fill ...

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

[GitHub] ignite pull request #4003: IGNITE-8500 - Dynamic Cassandra cache creation te...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/4003 IGNITE-8500 - Dynamic Cassandra cache creation test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8500

[GitHub] ignite pull request #4002: IGNITE-8498 JDBC: fix unordered stream compatibil...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/4002 IGNITE-8498 JDBC: fix unordered stream compatibility check You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #4001: IGNITE-8499 validate_indexes command doesn't dete...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/4001 IGNITE-8499 validate_indexes command doesn't detect absent rows in ca… You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8500) [Cassandra] Allow dynamic cache creation with Cassandra Store

Dmitry Karachentsev created IGNITE-8500: --- Summary: [Cassandra] Allow dynamic cache creation with Cassandra Store Key: IGNITE-8500 URL: https://issues.apache.org/jira/browse/IGNITE-8500 Project:

Re: supporting different configuration format json,yaml...

Folks, I guess when work on a thin client will be completed, we get more newcomers who use go/python/php/js. And we can do ignite more friendly for them, support familiar formats for configuration. On Tue, May 15, 2018 at 12:13 PM, Dmitry Pavlov wrote: > Hi Igniters, > >

Re: Abandoned Patch Available JIRA tickets

Hi Igniters, By common efforts from maintainers, committers and experienced contributors, it was possible to reduce the number of PA tasks - waiting for review to 88, - with no activity for 1 month and waiting for review to 24. 'No activity' tasks are more than a quarter from all patches

Re: [jira] [Created] (IGNITE-8497) Ignite stops the node in the middle of checkpointing upon receiving a SIGINT

Hi Igniters, Ivan, To my mind it is not a bug. Ignite would be able to restore memory state without waiting checkpoint to be completed. Note checkpoint may be very long running operation. Sincerely, Dmitriy Pavlov вт, 15 мая 2018 г. в 15:35, Ivan Artukhov (JIRA) : > Ivan

Re: Thin clients features wiki page

Thanks for proposals, guys, I will do this. Denis, Readme.io is not very convenient for some big tables. They look OK, while they have 3-4 columns, but if we are going to add more clients (or should I say "when") it is going to be a mess. This may be a one more argument when we consider to change

[GitHub] ignite pull request #3999: IGNITE-8493: refactor arrayToString, decrease hea...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/3999 IGNITE-8493: refactor arrayToString, decrease heap pressure. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8493

Re: [jira] [Created] (IGNITE-8497) Ignite stops the node in the middle of checkpointing upon receiving a SIGINT

It's a regular priority bug and should be fixed. Issue doesn't cause any kind of data loss. It's harmless, but still undesirable: even if checkpoint wasn't running, it will be triggered and then immediately interrupted by Ignition.stop(true). Such behavior increases time of following node

Re: supporting different configuration format json,yaml...

+1 to Dmitriy G. proposal. Since we're moving Ignite towards outside of Java world, we should definitely care about config usability for users who are not familiar with Java/Spring. If we take a look at any of our XML-configs, we can see a lot of boilerplate like "", "" - terms which say nothing

Re: SqlLine script and Java9

Petr, do we really need to check Java version for SqlLine at all? I think it will work with any version of Java, so restricting it to a certain version is just wrong. What do you think about removing the Java version check altogether from the SqlLine script? D. On Tue, May 15, 2018 at 10:21

[jira] [Created] (IGNITE-8494) CPP Thin: Implement Thin CPP client

Igor Sapego created IGNITE-8494: --- Summary: CPP Thin: Implement Thin CPP client Key: IGNITE-8494 URL: https://issues.apache.org/jira/browse/IGNITE-8494 Project: Ignite Issue Type: New Feature

Re: Null check removal in IGNITE-5779

Hi Igor, Could you please help with answering to this question? Sincerely, Dmitriy Pavlov вт, 15 мая 2018 г. в 5:18, Sunny Chan, CLSA : > Hello, > > > > In Ignite-5779 patch, CassandraSessionImpl.java line 289 a null check for row > has been removed (before the change: >

Re: supporting different configuration format json,yaml...

Hi Igniters, In general I aggree with adding new format, e.g. JSON is more popular than XML for new applications. In the same time I've never heard that user asked this in the user list. Or did I missed such topics? Sincerely, Dmitriy Pavlov вт, 15 мая 2018 г. в 9:31, Pavel Tupitsyn

[GitHub] ignite pull request #3914: Ignite-6430: CacheGroupsMetricsRebalanceTest.test...

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

Re: supporting different configuration format json,yaml...

I don't think we need to add new formats on server side as there may be a lot of different formats for different clients. On the other hand, supporting additional formats may be non trivial and error-prone, while adding little to a user experience. For clients, I see no problem in adding for

[jira] [Created] (IGNITE-8497) Ignite stops the node in the middle of checkpointing upon receiving a SIGINT

Ivan Artukhov created IGNITE-8497: - Summary: Ignite stops the node in the middle of checkpointing upon receiving a SIGINT Key: IGNITE-8497 URL: https://issues.apache.org/jira/browse/IGNITE-8497

[jira] [Created] (IGNITE-8493) [Test] GridToStringBuilder fails with NPE deals with primitive arrays operations.

Stanilovsky Evgeny created IGNITE-8493: -- Summary: [Test] GridToStringBuilder fails with NPE deals with primitive arrays operations. Key: IGNITE-8493 URL: https://issues.apache.org/jira/browse/IGNITE-8493

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Dmitriy, Looks good for me please merge. On Tue, May 15, 2018 at 11:20 AM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Dmitriy, > > Ok, I will do it soon. > > On Mon, May 14, 2018 at 8:41 PM, Dmitry Pavlov > wrote: > >> Hi Dmitriy G, >> >> could you

[GitHub] ignite pull request #4004: IGNITE-8501: Retry on GridServiceNotFoundExceptio...

GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/4004 IGNITE-8501: Retry on GridServiceNotFoundException in GridServiceProxy needs to be fixed You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8502) Ignite client can hang during a rejoin

Mikhail Cherkasov created IGNITE-8502: - Summary: Ignite client can hang during a rejoin Key: IGNITE-8502 URL: https://issues.apache.org/jira/browse/IGNITE-8502 Project: Ignite Issue

[jira] [Created] (IGNITE-8503) IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart has flaky failure: Entry which should be expired by TTL policy is available after grid restart

Dmitriy Pavlov created IGNITE-8503: -- Summary: IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart has flaky failure: Entry which should be expired by TTL policy is available after grid restart Key: IGNITE-8503

Re: Using a cache as an affinity co-located processing buffer in Ignite.Net

Hi Raymond, Was this question answered? Sincerely, Dmitriy Pavlov вт, 1 мая 2018 г. в 0:20, Raymond Wilson : > Cross posting to dev list for comment on cache interceptor availability on > Ignite .Net client. > > -Original Message- > From: Raymond Wilson

Re: supporting different configuration format json,yaml...

How are you going to translate this YAML config to Spring config? How would you deal with something like [1]? [1] - https://github.com/apache/ignite/blob/master/modules/platforms/cpp/odbc-test/config/queries-ssl-32.xml Best Regards, Igor On Tue, May 15, 2018 at 7:10 PM, Pavel Kovalenko

Re: management events for visor and web console tasks

Hi Andrei, Actually I did not understood this issue. What do you mean by tasks? Probably visor experts may provide feedback. Would you like to contribute fix with providing some new events? Could you mention ticket? Sincerely, Dmitriy Pavlov пт, 27 апр. 2018 г. в 16:40, Andrei Aleksandrov

Re: supporting different configuration format json,yaml...

Igor, Just get one of the config samples and translate it directly to YAML: XML - https://pastebin.com/wtQXXq8f YAML - https://pastebin.com/akGu3e81 2018-05-15 18:49 GMT+03:00 Igor Sapego : > Guys, if you think the YAML or JSON would be better, how about > you provide us a

Re: work with files and directories

+1 also for something like "resource manager". Recently, I've found for myself sonarcloud.io tool for code analisys. It's free for open source project and I've made Ignite project initial run [1]. I've prepeared analisys for mysefl and found a lot of duplicated code blocks [1]. Of course it's

Ignite hang on a complex SQL join occurring on 2 server nodes

The scenario is 1- Data is loaded from cassandra to a lookup cache -> replicated cache 2- Data is fetched from kafka input topic to a map 3- the map is inserted - using putall method - to another cache -> partitioned cache 4- a complex join is done between both caches 5- The result set is

work with files and directories

Hi Ignite, Do we have a general approach to work with a file and directories? I see many duplication logic for write through .tmp file. For example, GridCacheDatabaseSharedManager.writeCheckpointEntry(); GridCacheDatabaseSharedManage.nodeStart();

Re: supporting different configuration format json,yaml...

Guys, if you think the YAML or JSON would be better, how about you provide us a brief example of how such configs are going to look, so we can compare and see, if this ever have any sense. Best Regards, Igor On Tue, May 15, 2018 at 4:20 PM, Ilya Kasnacheev wrote: >

Re: work with files and directories

Hi Maxim, FileWriteAheadLogManager & FsyncModeFileWriteAheadLogManager were intentionally copy-pasted in hope we will soon delete FsyncManager. But it is still shows this tool works good. Probably we could integrate this tool to our processes. Sincerely, Dmitriy Pavlov вт, 15 мая 2018 г. в

[GitHub] ignite pull request #3940: IGNITE-8354 Ignite Continuosly refreshes Cassandr...

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

Re: Thin clients features wiki page

Hi Igor, Thanks for creating this! One question: what is `Multithreading` feature? Pavel On Tue, May 15, 2018 at 9:45 PM, Denis Magda wrote: > Igor, > > That's a valid point. Will see how it goes. As for the new documentation > engine, there are no more arguments. We will

Re: supporting different configuration format json,yaml...

JSON sucks for config files anyway, there are no comments, no schemas, quotes are required around keys, etc Just answer one question: what issue are we trying to solve? XML is not a problem IMO, complexity of our config is. On Tue, May 15, 2018 at 8:00 PM, Igor Sapego wrote:

Re: supporting different configuration format json,yaml...

Pavel, One can use json-schema if necessary. Of course, XML is more powerful in many aspects, but produces more eye fatigue for humans. Of course, we are to stay with XML if switching to another configuration format requires significant effort. BTW, first time I heard about JSON from [1] : "

Re: Thin clients features wiki page

Igor, That's a valid point. Will see how it goes. As for the new documentation engine, there are no more arguments. We will try to migrate within 2.6. Just need to find more contributors who would help with this. -- Denis On Tue, May 15, 2018 at 2:11 AM, Igor Sapego wrote:

RE: Using a cache as an affinity co-located processing buffer in Ignite.Net

Hi Dmitriy, My question regarding cache interceptor availability in .Net is still outstanding. I have working code using a continuous query, but am interested in cache interceptor if this is a better solution. Thanks. Raymond. *From:* Dmitry Pavlov [mailto:dpavlov@gmail.com]

Re: async operation is not fair async

Alexey, Any updates? On Mon, May 14, 2018 at 6:19 PM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Alexey, > > Could you please add more description information for this task? [1] > Perhaps, base steps for implementation. > > [1] https://issues.apache.org/jira/browse/IGNITE-8475

Re: work with files and directories

+1 to this approach, It can be also very helpful in failover scenarios when something wrong happened with disk. In this case we're reducing the number of points of failure. 2018-05-15 18:37 GMT+03:00 Dmitriy Govorukhin : > Hi Ignite, > > Do we have a general

Re: One more round for PR review

Looks good for me now. On Tue, May 15, 2018 at 12:38 AM, Dmitry Pavlov wrote: > Hi Alexey K, > > could you please check that all proposals were applied? > > Sincerely, > Dmitriy Pavlov > > чт, 10 мая 2018 г. в 22:59, Igor Rudyak : > > > Hi guys, > > > >

[GitHub] ignite pull request #3997: IGNITE-8449 no need for checkpoint lock in case o...

GitHub user macrergate opened a pull request: https://github.com/apache/ignite/pull/3997 IGNITE-8449 no need for checkpoint lock in case of stale updates You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Dmitriy, Ok, I will do it soon. On Mon, May 14, 2018 at 8:41 PM, Dmitry Pavlov wrote: > Hi Dmitriy G, > > could you please pick up this review? > > Sincerely, > Dmitriy Pavlov > > чт, 10 мая 2018 г. в 15:50, Александр Меньшиков : > >> Hi, >> >> I

[jira] [Created] (IGNITE-8490) Web Console: Update to AngularJS 1.7.x

Alexey Kuznetsov created IGNITE-8490: Summary: Web Console: Update to AngularJS 1.7.x Key: IGNITE-8490 URL: https://issues.apache.org/jira/browse/IGNITE-8490 Project: Ignite Issue Type:

[GitHub] ignite pull request #3998: ignite-2.5.1-p2

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3998 ignite-2.5.1-p2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p2 Alternatively you can

[jira] [Created] (IGNITE-8492) JDBC: Add a note about authentication for thin driver to docs

Taras Ledkov created IGNITE-8492: Summary: JDBC: Add a note about authentication for thin driver to docs Key: IGNITE-8492 URL: https://issues.apache.org/jira/browse/IGNITE-8492 Project: Ignite

[jira] [Created] (IGNITE-8504) Web console: minor update webpack tweaks

Ilya Borisov created IGNITE-8504: Summary: Web console: minor update webpack tweaks Key: IGNITE-8504 URL: https://issues.apache.org/jira/browse/IGNITE-8504 Project: Ignite Issue Type:

Re: supporting different configuration format json,yaml...

Guys, Spring is IoC and you can't offer any format that can replace Spring. It will just limited DSL. Once again. We have enough problems with main functionality. Why do you want to focus on minor features? вт, 15 мая 2018 г., 23:26 Andrey Kuznetsov : > Pavel, > > One can

Re: work with files and directories

Andrey, I think the main idea of that not about how to unify writing content to file. It's about creating peristence files and folders. For other persistence components (WAL, Checkpoint, etc.) it should be like FileFactory object with methods like "public File getOrCreatePartitionFile(...),

[jira] [Created] (IGNITE-8505) Web Console: Add optional description for SQL Notebook

Alexey Kuznetsov created IGNITE-8505: Summary: Web Console: Add optional description for SQL Notebook Key: IGNITE-8505 URL: https://issues.apache.org/jira/browse/IGNITE-8505 Project: Ignite