[GitHub] ignite pull request #3387: IGNITE-6598 .NET: Implement IIgnite.AddCacheConfi...

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

[jira] [Created] (IGNITE-7444) SQL: add native batch execution support for UPDATE, MERGE and DELETE commands

Roman Kondakov created IGNITE-7444: -- Summary: SQL: add native batch execution support for UPDATE, MERGE and DELETE commands Key: IGNITE-7444 URL: https://issues.apache.org/jira/browse/IGNITE-7444

Re: Ignite Semaphore Bug 7090

Thanks Tim! I hope Vlad can review your patch. If this does not happen in 2-3 days I will take a look. Can you please let me know on weekend if I need to? --Yakov 2018-01-16 23:36 GMT+03:00 Tim Onyschak : > Hey all, > > I created a patch and posted to user group, was told

[jira] [Created] (IGNITE-7443) ODBC: use native batching capabilities on the server side

Vladimir Ozerov created IGNITE-7443: --- Summary: ODBC: use native batching capabilities on the server side Key: IGNITE-7443 URL: https://issues.apache.org/jira/browse/IGNITE-7443 Project: Ignite

[GitHub] ignite pull request #3298: IGNITE-6022: Implemented native batch execution s...

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

Re: IGNITE-6252 patch

Hi Sunny, Thanks for the notification. Just found this PR. Will review it a bit later. Igor On Tue, Jan 16, 2018 at 7:15 PM, Sunny Chan, CLSA wrote: > Hi Igor, > > Any luck with the review and merge of the patch? > > Thanks > > -Original Message- > From: Denis

RE: IGNITE-6252 patch

Hi Igor, Any luck with the review and merge of the patch? Thanks -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Friday, January 05, 2018 4:29 AM To: dev@ignite.apache.org; Igor Rudyak Cc: Nikolai Tikhonov Subject: Re: IGNITE-6252 patch Hello, I hope Igor R.

RE: Adopting mock framework (ex. Mockito) for unit tests

As discussed, updated the PR with the change to put the mockito version at the parent POM and using it on the cassandra module. https://github.com/apache/ignite/pull/3088 Thanks. -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Wednesday, January 17, 2018 9:55 AM

Re: Adopting mock framework (ex. Mockito) for unit tests

Looks we came to a consensus. Jason, please change the PR the way you say > I will change my PR to add the dependency at parent POM level and use it only > for my test in ignite-cassandra. Igor should review it shortly. — Denis > On Jan 16, 2018, at 5:33 PM, Jason Man, CLSA

RE: Adopting mock framework (ex. Mockito) for unit tests

Agree with Vladimir/Denis/Igor on using it for specific tests/components. What I meant by 'adopt' is to be able use it to facilitate testing of Ignite code somewhere. It doesn’t mean we should change our overall testing approach overnight and try to use it everywhere. In the case of testing

Ignite Semaphore Bug 7090

Hey all, I created a patch and posted to user group, was told feed back would be left on the jira. I wanted to see if we could get a fix in with 2.4, could somebody please review. http://apache-ignite-users.70518.x6.nabble.com/Semaphore-Stuck-when-no-acquirers-to-assign-permit-td18639.html

Re: Ignite not friendly for Monitoring

Assigned the version 2.5 to the ticket. Let's try to make progress on this before then. On Tue, Jan 16, 2018 at 12:03 PM, Denis Magda wrote: > Serge, > > Thanks for taking over this. Think we’re moving in a right direction with > your proposal: > > * I would add a top-level

Re: Ignite not friendly for Monitoring

Serge, Thanks for taking over this. Think we’re moving in a right direction with your proposal: * I would add a top-level domain for “Integrations”. All the integrations with Kafka, Spark, Storm, etc. should go there. * Second-level domains number can grow over the time per a top-level layer.

Re: Adopting mock framework (ex. Mockito) for unit tests

Agree with Igor’s opinion. If it simplifies Cassandra integration testing cycles and maintenance then we should go for it for *this* component only. No need to push it to all the component we have. — Denis > On Jan 16, 2018, at 10:24 AM, Igor Rudyak wrote: > > It will be

Re: Thin client: Java bindings

Alexey, Pavel agreed to add transactions to the protocol in 2.5 release: https://issues.apache.org/jira/browse/IGNITE-7369 — Denis > On Jan 16, 2018, at 2:02 AM, Alexey Kukushkin > wrote: > > Dmitriy, > >

Re: Thin client: Java bindings

Not sure the protocol should care of invoke() or any compute grid methods. Technically the user add a computation or entry processor to the class path of remote nodes and then trigger them using a simple operation support by the protocol. But do users and we really need this? Usually invoke and

[GitHub] ignite pull request #3147: Ignite 7050

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

Re: Adopting mock framework (ex. Mockito) for unit tests

It will be good to clarify what do you mean by adopt? Can't we just start using it as is for specific cases? I understand that there are some cases which probably not the best scenario for Mockito. At the same time there are lot's of other cases (like in IGNITE-6853

[jira] [Created] (IGNITE-7442) Data load hangs with SQL on-heap cache enabled

Mikhail Cherkasov created IGNITE-7442: - Summary: Data load hangs with SQL on-heap cache enabled Key: IGNITE-7442 URL: https://issues.apache.org/jira/browse/IGNITE-7442 Project: Ignite

Re: Spring3 support

Hi Andrey, I agree with you after migration to jav8/9 there's no way to support spring3 in Ignite. So I think we shouldn't integrate this patch into master and people who need spring3 support can apply the patch to ignite 2.3 release and use their own build. Thanks, Mike. 2018-01-16 18:23

[GitHub] ignite pull request #3388: IGNITE-7418: Add RMSProp parameter update algorit...

GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/3388 IGNITE-7418: Add RMSProp parameter update algorithm You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7418

Re: Handling slashes in cache names

>> How about using both escaping and a text file with the name? One can think of the escaped name as of a kind of ID, which happens to be human-readable when the name is in ASCII, and as unreadable as an UUID when the name is in UTF. This way we have all the readability in the common case (when

Re: Spring3 support

Guys, I doubt that we should include spring-3 module in Apache Ignite 2.4 because we will drop Java 7 support. Only Spring Framework 4.x supports Java 8 without any limitations. Thoughts? On Tue, Jan 16, 2018 at 6:01 PM, Michael Cherkasov wrote: > Hi all, > > as I

Re: Spring3 support

Hi all, as I can see there are no objections, also the fix was reviewed by Anton V and Andrey G: https://issues.apache.org/jira/browse/IGNITE-7050 Could one of committer please integrate the change? Thanks, Mike . 2018-01-12 18:06 GMT+03:00 Michael Cherkasov : >

[jira] [Created] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property

Denis Mekhanikov created IGNITE-7441: Summary: Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property Key: IGNITE-7441 URL: https://issues.apache.org/jira/browse/IGNITE-7441 Project: Ignite

[GitHub] ignite pull request #3387: IGNITE-6598 .NET: Implement IIgnite.AddCacheConfi...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3387 IGNITE-6598 .NET: Implement IIgnite.AddCacheConfiguration You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6598

[jira] [Created] (IGNITE-7440) .NET: Thin client: AddCacheConfiguration

Pavel Tupitsyn created IGNITE-7440: -- Summary: .NET: Thin client: AddCacheConfiguration Key: IGNITE-7440 URL: https://issues.apache.org/jira/browse/IGNITE-7440 Project: Ignite Issue Type:

Re: Ignite not friendly for Monitoring

It might be an issue: https://issues.apache.org/jira/browse/IGNITE-3690 I'm going to update it when the domain list will be agreed upon by the community. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-7439) CLI AUTH: implement user credential storage and default admin user creation

Taras Ledkov created IGNITE-7439: Summary: CLI AUTH: implement user credential storage and default admin user creation Key: IGNITE-7439 URL: https://issues.apache.org/jira/browse/IGNITE-7439 Project:

Re: Username/password authentication for thin clients

What do you think about usage bcrypt [1], [2] to store encrypted password? [1] https://stackoverflow.com/questions/1561174/sha512-vs-blowfish-and-bcrypt [2] https://en.wikipedia.org/wiki/Bcrypt On 15.01.2018 11:19, Vladimir Ozerov wrote: 2) Credentials will be stored in a form of [username

[GitHub] ignite pull request #3376: ignite-7412 Fixed race in WAL manager with mmap e...

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

RE: Handling slashes in cache names

How about using both escaping and a text file with the name? One can think of the escaped name as of a kind of ID, which happens to be human-readable when the name is in ASCII, and as unreadable as an UUID when the name is in UTF. This way we have all the readability in the common case (when name

Re: Adopting mock framework (ex. Mockito) for unit tests

Mocking is a good testing technique, but over years we failed to adopt it in Ignite. The reason is high project complexity, when a lot of components are interact with each other, and it is very hard to extract clean interfaces out of it. We definitely could do better with our OOP, but you should

[GitHub] ignite pull request #3367: IGNITE-7397: Fix wrong cache configuration for ML...

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

[GitHub] ignite pull request #3386: IGNITE-7359: prototype for ddl vs cache ops synch...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/3386 IGNITE-7359: prototype for ddl vs cache ops synchronization You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-7438) LSQR: Sparse Equations and Least Squares for Lin Regression

Yury Babak created IGNITE-7438: -- Summary: LSQR: Sparse Equations and Least Squares for Lin Regression Key: IGNITE-7438 URL: https://issues.apache.org/jira/browse/IGNITE-7438 Project: Ignite

[jira] [Created] (IGNITE-7437) Partition based dataset implementation

Yury Babak created IGNITE-7437: -- Summary: Partition based dataset implementation Key: IGNITE-7437 URL: https://issues.apache.org/jira/browse/IGNITE-7437 Project: Ignite Issue Type: New Feature

Re: Handling slashes in cache names

> folder named by ID and txt file inside should do the trick Agree On Tue, Jan 16, 2018 at 1:02 PM, Dmitriy Setrakyan wrote: > On Mon, Jan 15, 2018 at 7:31 AM, Pavel Tupitsyn > wrote: > > > > You will never ever relate smth like "fdee0456adcc" to

[GitHub] ignite pull request #3363: IGNITE-5725 Adapt TracerTest for TC builds.

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

Re: Adopting mock framework (ex. Mockito) for unit tests

Hi Jason, I heartily support unit testing practices and introducing a mocking framework into ignite development environment. Today I can hardly find a single unit test in Apache Ignite, which does not allow me to use the best TDD and CI/CD practices like running tests on every commit (or even on

[GitHub] ignite pull request #3368: IGNITE-7350: Distributed MLP cleanup/refactoring.

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

[jira] [Created] (IGNITE-7436) Username/password authentication for thin clients

Taras Ledkov created IGNITE-7436: Summary: Username/password authentication for thin clients Key: IGNITE-7436 URL: https://issues.apache.org/jira/browse/IGNITE-7436 Project: Ignite Issue

Adopting mock framework (ex. Mockito) for unit tests

Hi Igniters, I'd like to discuss the topic of adopting a mock framework such as Mockito into Ignite's project for writing unit tests. Here's a simple article that illustrate why using a mock object for testing is necessary, and why using a framework is better than doing it yourself:

[GitHub] ignite pull request #3360: IGNITE-7378: WAL converter: add records statistic...

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

[GitHub] ignite pull request #3385: IGNITE-7378: WAL converter: add records statistic...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3385 IGNITE-7378: WAL converter: add records statistic to WAL reader dev-util You can merge this pull request into a Git repository by running: $ git pull

Re: Thin client: Java bindings

Got it, thanks! On Tue, Jan 16, 2018 at 2:02 AM, Alexey Kukushkin wrote: > Dmitriy, > > Although having invoke() was really important for us, implementing invoke() > does not look trivial (need to think about real multi-lingual and > cross-platform design) and we do

Re: Handling slashes in cache names

On Mon, Jan 15, 2018 at 7:31 AM, Pavel Tupitsyn wrote: > > You will never ever relate smth like "fdee0456adcc" to "мои_данные". > > As a user, why do I need to understand file names in Ignite work directory? > Because it is better to have an understandable and human

Re: Thin client: Java bindings

Dmitriy, Although having invoke() was really important for us, implementing invoke() does not look trivial (need to think about real multi-lingual and cross-platform design) and we do not have time to implement it on the first phase. Currently thin client protocol does not support it so we would

Re: Handling slashes in cache names

On Mon, Jan 15, 2018 at 7:11 AM, Pavel Tupitsyn wrote: > > try creating a directory on all nodes > And then a new node appears with a different kind of file system.. > If a new node cannot create an existing cache, it should not be allowed to start.

Re: Ignite not friendly for Monitoring

Is there a Jira ticket for it? On Mon, Jan 15, 2018 at 7:48 AM, Serge Puchnin wrote: > Igniters, > > It's a right idea! > > Let's try to revitalize it and make a move on. > > As a first step, I would like to propose a list of a top-level domain. > > -- the phase 1 >

Re: IGNITE-6853: Cassandra cache store does not clean prepared statements cache when remove old cassandra session

Jason, can you please start a separate thread about using Mockito for testing Ignite? D. On Mon, Jan 15, 2018 at 6:13 PM, Jason Man, CLSA wrote: > Thanks. Just replied on the jira thread as well. Thanks. > > -Original Message- > From: Denis Magda

[GitHub] ignite pull request #3384: IGNITE-7248 "Schema not found" error when setting...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3384 IGNITE-7248 "Schema not found" error when setting streaming mode for JDBC driver You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3354: IGNITE-7380: Avoid updating PagePartitionCounters...

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

Re: Apache Ignite 2.4 release

Denis, I'll review https://issues.apache.org/jira/browse/IGNITE-6902 On Fri, Jan 12, 2018 at 11:45 PM, Denis Magda wrote: > Here is the page create before: > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 < >

Re: Thin client: Java bindings

Hi Alexey, Thanks for a detailed email. I think your approach is correct. Are you planning to implement the full JCache API for the Java thin client? If yes, I think you are missing the invoke(...) methods. Also, would be nice to support transactions as well. D. On Tue, Jan 16, 2018 at 12:03

[jira] [Created] (IGNITE-7434) Thin client Java API - cache query API

Alexey Kukushkin created IGNITE-7434: Summary: Thin client Java API - cache query API Key: IGNITE-7434 URL: https://issues.apache.org/jira/browse/IGNITE-7434 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7435) Thin client Java API - fields query API

Alexey Kukushkin created IGNITE-7435: Summary: Thin client Java API - fields query API Key: IGNITE-7435 URL: https://issues.apache.org/jira/browse/IGNITE-7435 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7433) Thin client Java API - cache clear

Alexey Kukushkin created IGNITE-7433: Summary: Thin client Java API - cache clear Key: IGNITE-7433 URL: https://issues.apache.org/jira/browse/IGNITE-7433 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7432) Thin client Java API - cache atomic get/put/replace/remove

Alexey Kukushkin created IGNITE-7432: Summary: Thin client Java API - cache atomic get/put/replace/remove Key: IGNITE-7432 URL: https://issues.apache.org/jira/browse/IGNITE-7432 Project: Ignite

[jira] [Created] (IGNITE-7431) Thin client Java API - cache replace/remove API

Alexey Kukushkin created IGNITE-7431: Summary: Thin client Java API - cache replace/remove API Key: IGNITE-7431 URL: https://issues.apache.org/jira/browse/IGNITE-7431 Project: Ignite

[jira] [Created] (IGNITE-7430) Thin client Java API - cache putAll/getAll

Alexey Kukushkin created IGNITE-7430: Summary: Thin client Java API - cache putAll/getAll Key: IGNITE-7430 URL: https://issues.apache.org/jira/browse/IGNITE-7430 Project: Ignite Issue

[jira] [Created] (IGNITE-7429) Thin client Java API - cache put/get/contains

Alexey Kukushkin created IGNITE-7429: Summary: Thin client Java API - cache put/get/contains Key: IGNITE-7429 URL: https://issues.apache.org/jira/browse/IGNITE-7429 Project: Ignite Issue

[jira] [Created] (IGNITE-7427) Thin client Java API - failover

Alexey Kukushkin created IGNITE-7427: Summary: Thin client Java API - failover Key: IGNITE-7427 URL: https://issues.apache.org/jira/browse/IGNITE-7427 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7426) Thin client Java API - encryption

Alexey Kukushkin created IGNITE-7426: Summary: Thin client Java API - encryption Key: IGNITE-7426 URL: https://issues.apache.org/jira/browse/IGNITE-7426 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7425) Thin client Java API - binary objects

Alexey Kukushkin created IGNITE-7425: Summary: Thin client Java API - binary objects Key: IGNITE-7425 URL: https://issues.apache.org/jira/browse/IGNITE-7425 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7424) Thin client Java API - cache enumeration

Alexey Kukushkin created IGNITE-7424: Summary: Thin client Java API - cache enumeration Key: IGNITE-7424 URL: https://issues.apache.org/jira/browse/IGNITE-7424 Project: Ignite Issue

[jira] [Created] (IGNITE-7423) Thin client Java API - cache management

Alexey Kukushkin created IGNITE-7423: Summary: Thin client Java API - cache management Key: IGNITE-7423 URL: https://issues.apache.org/jira/browse/IGNITE-7423 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7422) Thin client Java API - startClient

Alexey Kukushkin created IGNITE-7422: Summary: Thin client Java API - startClient Key: IGNITE-7422 URL: https://issues.apache.org/jira/browse/IGNITE-7422 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7421) Thin client Java API - data grid API

Alexey Kukushkin created IGNITE-7421: Summary: Thin client Java API - data grid API Key: IGNITE-7421 URL: https://issues.apache.org/jira/browse/IGNITE-7421 Project: Ignite Issue Type:

Thin client: Java bindings

Igniters, I am working on a project where users will use Ignite via a thin client protocol. The API will be Java and the client will have to support failover and encryption. I know community already developed the thin client protocol and .NET bindings and is going to develop failover and