[jira] [Created] (IGNITE-5445) ServerImpl can't process NodeFailedMessage about itself

Alexander Belyak created IGNITE-5445: Summary: ServerImpl can't process NodeFailedMessage about itself Key: IGNITE-5445 URL: https://issues.apache.org/jira/browse/IGNITE-5445 Project: Ignite

Re: Configuration issues with IGFS in Ignite 1.9

Vova, Could you take a look at the issue? — Denis > On Jun 7, 2017, at 1:40 PM, Konstantin Boudnik wrote: > > Guys, > > after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing > a number of issues introduced by changed script interfaces and > similar. However,

Re: Suggested changes for Apache Ignite Release procedure

+1 > On Jun 7, 2017, at 3:40 AM, Sergey Kozlov wrote: > > Hi, Igniters > > I'd start the discussion for following changes of release procedure. > As you may know we provided not source artifacts only but also a set of > binaries that makes using of the release is more

Re: Key type name and value type name for CREATE TABLE

Vova, > On Jun 7, 2017, at 1:20 AM, Vladimir Ozerov wrote: > > Valya, > > It doesn't affect builder invoked from DML engine, as it know how to find > these names. As per users who want to call IgniteCache.put() on a cache > created through SQL - sorry, they will have

[jira] [Created] (IGNITE-5444) Collections.singletonList is not properly serialized by binary marshaller

Valentin Kulichenko created IGNITE-5444: --- Summary: Collections.singletonList is not properly serialized by binary marshaller Key: IGNITE-5444 URL: https://issues.apache.org/jira/browse/IGNITE-5444

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

Hi Nick, How exactly do you replace the class loader and can you give a little bit more detail about why you do this? As for the issues, here are my comments: 1. Can you clarify this? In which scenario it doesn't work and why? 2. Why do you deploy domain classes in the first place? Ignite

Re: Data compression in Ignite 2.0

Vyacheslav, Anton, Are there any ideas and/or prototypes for the API? Your design suggestions seem to make sense, but I would like to see how it all this will like from user's standpoint. -Val On Wed, Jun 7, 2017 at 1:06 AM, Антон Чураев wrote: > Vyacheslav, correct me

Configuration issues with IGFS in Ignite 1.9

Guys, after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing a number of issues introduced by changed script interfaces and similar. However, the one which I still can not fix so far is this. The secondary file system is configured like this:

[jira] [Created] (IGNITE-5443) The bunch of javadoc warnings

Sergey Kozlov created IGNITE-5443: - Summary: The bunch of javadoc warnings Key: IGNITE-5443 URL: https://issues.apache.org/jira/browse/IGNITE-5443 Project: Ignite Issue Type: Bug

Re: "Review workflow" changes to prevent "broken review" issues.

Igniters, Dmitry, basically agree It's no secret that Ignite is a very complex project, and contributors need a very high experience to become a committer. But this is a potential problem for scaling the community and project development. I think that one of the options for solving the growth

Re: New version of Web Console released

Thanks Alexey! for the pointers. For the ORM alternate case the use case is the below (basically today we are thinking of using Ignite with MyBatis with Ignite being the L2 cache (among other things) & MyBatis being the persistence framework, the question is can Ignite do the cache with the Web

Re: New version of Web Console released

Sure i will do that..thanks! Regards, Muthu On Wed, Jun 7, 2017 at 5:06 AM, Alexey Kuznetsov wrote: > Muthu, > > It is better to start separate thread on user list about your use case. > > On Wed, Jun 7, 2017 at 4:22 PM, Muthu wrote: > >> >>

[jira] [Created] (IGNITE-5442) Linq Conditional statement will fail for some types

Sergey Stronchinskiy created IGNITE-5442: Summary: Linq Conditional statement will fail for some types Key: IGNITE-5442 URL: https://issues.apache.org/jira/browse/IGNITE-5442 Project: Ignite

[GitHub] ignite pull request #2106: IGNITE-4370: Implemented writing of batch of para...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2106 IGNITE-4370: Implemented writing of batch of parameters for ODBC. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2105: Ignite 5432

GitHub user a1vanov opened a pull request: https://github.com/apache/ignite/pull/2105 Ignite 5432 Fix for test IgniteMarshallerCacheClassNameConflictTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/a1vanov/ignite ignite-5432

[jira] [Created] (IGNITE-5441) .NET: Stack trace is lost for exceptions in ICacheStore

Pavel Tupitsyn created IGNITE-5441: -- Summary: .NET: Stack trace is lost for exceptions in ICacheStore Key: IGNITE-5441 URL: https://issues.apache.org/jira/browse/IGNITE-5441 Project: Ignite

[GitHub] ignite pull request #2104: IGNITE-5170 .NET: Compute peer deployment example

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2104 IGNITE-5170 .NET: Compute peer deployment example You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-5170

[jira] [Created] (IGNITE-5440) JDBC thin: support SQL esacpe processing

Taras Ledkov created IGNITE-5440: Summary: JDBC thin: support SQL esacpe processing Key: IGNITE-5440 URL: https://issues.apache.org/jira/browse/IGNITE-5440 Project: Ignite Issue Type: Task

Optimize transaction prepare step when store is enabled IGNITE-1553

Hi, Igntrs! Feel free to reviewing the ticket https://issues.apache.org/jira/browse/IGNITE-1553 https://github.com/apache/ignite/pull/2091 -- *Best Regards,* *Kuznetsov Aleksey*

Re: Suggested changes for Apache Ignite Release procedure

Huge +1 On Wed, Jun 7, 2017 at 1:40 PM, Sergey Kozlov wrote: > Hi, Igniters > > I'd start the discussion for following changes of release procedure. > As you may know we provided not source artifacts only but also a set of > binaries that makes using of the release is more

[jira] [Created] (IGNITE-5439) JDBC thin: support query cancel

Taras Ledkov created IGNITE-5439: Summary: JDBC thin: support query cancel Key: IGNITE-5439 URL: https://issues.apache.org/jira/browse/IGNITE-5439 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5438) DBC thin: support query timeout

Taras Ledkov created IGNITE-5438: Summary: DBC thin: support query timeout Key: IGNITE-5438 URL: https://issues.apache.org/jira/browse/IGNITE-5438 Project: Ignite Issue Type: Task

Re: IGNITE-5432

Hi Alexey, I've added you to the contributors' list. Please assign the issue to yourself. --AG 2017-06-07 14:47 GMT+03:00 Alexey Ivanov : > Hi, everybody > > I'd like fix this issue: > > https://issues.apache.org/jira/browse/IGNITE-5432 > > Alexey Ivanov (a1vanov) > >

[jira] [Created] (IGNITE-5437) SQL: Incorrect partition is derived from query when argument type differs from column type

Sergey Kalashnikov created IGNITE-5437: -- Summary: SQL: Incorrect partition is derived from query when argument type differs from column type Key: IGNITE-5437 URL:

[GitHub] ignite pull request #1852: ignite-5030

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1852 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1852: ignite-5030

GitHub user daradurvs reopened a pull request: https://github.com/apache/ignite/pull/1852 ignite-5030 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5030 Alternatively you can review and apply these

[GitHub] ignite pull request #1651: ignite-4211

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1651 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1852: ignite-5030

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1852 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1852: ignite-5030

GitHub user daradurvs reopened a pull request: https://github.com/apache/ignite/pull/1852 ignite-5030 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5030 Alternatively you can review and apply these

[jira] [Created] (IGNITE-5436) .NET: CacheConfiguration.GroupName

Pavel Tupitsyn created IGNITE-5436: -- Summary: .NET: CacheConfiguration.GroupName Key: IGNITE-5436 URL: https://issues.apache.org/jira/browse/IGNITE-5436 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5435) JDBC thin: support statement close on completion

Taras Ledkov created IGNITE-5435: Summary: JDBC thin: support statement close on completion Key: IGNITE-5435 URL: https://issues.apache.org/jira/browse/IGNITE-5435 Project: Ignite Issue

Re: New version of Web Console released

Muthu, It is better to start separate thread on user list about your use case. On Wed, Jun 7, 2017 at 4:22 PM, Muthu wrote: > > Thanks Alexey! for the pointers. For the ORM alternate case the use case > is the below (basically today we are thinking of using Ignite

IGNITE-5432

Hi, everybody I'd like fix this issue: https://issues.apache.org/jira/browse/IGNITE-5432 Alexey Ivanov (a1vanov)

Re: IGNITE-5229 is ready for review

Roman, Today I added some tips how to request review in most efficient way. See thread '*"Review workflow" changes to prevent "broken review" issues*' for details. I'd like to ask you to help me to check my theory that these tips works. Could you please ask review using tips from

[GitHub] ignite pull request #2103: IGNITE-5431 Better handling of cache SQL flag inc...

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2103 IGNITE-5431 Better handling of cache SQL flag incompatibility. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2102: IGNITE-5196 Ignite JDBC Driver fix

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/2102 IGNITE-5196 Ignite JDBC Driver fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite jdbc-fix Alternatively you can

[jira] [Created] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch

Aleksey Chetaev created IGNITE-5434: --- Summary: Yardstick sql benchmarks broken on Ignite-5267 branch Key: IGNITE-5434 URL: https://issues.apache.org/jira/browse/IGNITE-5434 Project: Ignite

[GitHub] ignite pull request #2101: IGNITE-5430

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2101 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: "Review workflow" changes to prevent "broken review" issues.

Page updated. On Wed, Jun 7, 2017 at 1:33 PM, Anton Vinogradov wrote: > Dmitriy, > > Got it, > I'll add this as an optional "Tips to pass review quickly". > > On Tue, Jun 6, 2017 at 7:11 PM, Dmitriy Setrakyan > wrote: > >> On Tue, Jun 6, 2017 at

Suggested changes for Apache Ignite Release procedure

Hi, Igniters I'd start the discussion for following changes of release procedure. As you may know we provided not source artifacts only but also a set of binaries that makes using of the release is more friendly namely: - binary farbic artifact - binary hadoop artifact - articats in Apache

Re: "Review workflow" changes to prevent "broken review" issues.

Dmitriy, Got it, I'll add this as an optional "Tips to pass review quickly". On Tue, Jun 6, 2017 at 7:11 PM, Dmitriy Setrakyan wrote: > On Tue, Jun 6, 2017 at 7:40 AM, Anton Vinogradov > > wrote: > > > Igniters, > > > > Since we found that

[jira] [Created] (IGNITE-5433) Incorrect warning when "default" memory policy is used

Ksenia Rybakova created IGNITE-5433: --- Summary: Incorrect warning when "default" memory policy is used Key: IGNITE-5433 URL: https://issues.apache.org/jira/browse/IGNITE-5433 Project: Ignite

[jira] [Created] (IGNITE-5432) Test IgniteMarshallerCacheClassNameConflictTest failed

Alexey Ivanov created IGNITE-5432: - Summary: Test IgniteMarshallerCacheClassNameConflictTest failed Key: IGNITE-5432 URL: https://issues.apache.org/jira/browse/IGNITE-5432 Project: Ignite

Re: Persistent Distributed Store Metrics

Denis, Thanks for the review. I addressed your comments and merged the changes to ignite-5267 branch. 2017-06-06 22:56 GMT+03:00 Denis Magda : > > On Jun 5, 2017, at 8:02 PM, Konstantin Boudnik wrote: > > > > On Mon, Jun 05, 2017 at 07:41PM, Dmitriy

[GitHub] ignite pull request #2101: IGNITE-5430

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

[GitHub] ignite pull request #2100: IGNITE-5422

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

[jira] [Created] (IGNITE-5431) Better exception message when SQL cache flag doesn't match

Vladimir Ozerov created IGNITE-5431: --- Summary: Better exception message when SQL cache flag doesn't match Key: IGNITE-5431 URL: https://issues.apache.org/jira/browse/IGNITE-5431 Project: Ignite

Re: Key type name and value type name for CREATE TABLE

Sergi, This will require additional coordination between nodes, so I would not do that for now. We have more serious problem here - binary metadata in current implementation is not suited for DDL operations. We will feel it better when start working on ALTER TABLE command, when single attribute

[GitHub] ignite pull request #2085: IGNITE-5400 .NET: IgniteConfiguration.SqlConnecto...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2085 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2099: IGNITE-5325 Cache group param in CREATE TABLE

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2099 IGNITE-5325 Cache group param in CREATE TABLE You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5325

Re: is IGNITE-3142 actual now

OK, thank you, Denis! 2017-06-06 21:04 GMT+03:00 Denis Magda : > Vadim, > > Please try to run the reproducer attached. If the error pops up then the > bug needs to be fixed. > > — > Denis > > > On Jun 6, 2017, at 4:36 AM, Вадим Опольский > wrote: > > > >

Re: Key type name and value type name for CREATE TABLE

Vova, May be it makes sense to have an increasing version instead of UUID? Like sql_myschema_Person_1_Key. So that user will be able to pass just a table name `Person` to our API and receive a correct latest type name for that table. What do you think? Sergi 2017-06-07 11:20 GMT+03:00

[jira] [Created] (IGNITE-5430) Mask cache name for CREATE TABLE operation

Vladimir Ozerov created IGNITE-5430: --- Summary: Mask cache name for CREATE TABLE operation Key: IGNITE-5430 URL: https://issues.apache.org/jira/browse/IGNITE-5430 Project: Ignite Issue

Re: Key type name and value type name for CREATE TABLE

Valya, It doesn't affect builder invoked from DML engine, as it know how to find these names. As per users who want to call IgniteCache.put() on a cache created through SQL - sorry, they will have hard times resolving actual type name. This is OK for the first release, provided that we mask type

Re: Key type name and value type name for CREATE TABLE

Dima, Currently key and val type names for the table "myschema"."Person" will be something like this. key: "sql_myschema_Person_[RANDOM_UUID]_Key" val: "sql_myschema_Person_[RANDOM_UUID]" On Wed, Jun 7, 2017 at 5:42 AM, Dmitriy Setrakyan wrote: > Vova, > > I am not sure

Re: Data compression in Ignite 2.0

Vyacheslav, correct me if something wrong We could provide opportunity of choose between CPU usage and MEM/NET usage for users by compression some attributes of stored objects. You have learned design, and it is possible to localize changes in marshalling without performance affect and current

Re: Persistent Store Stabilization for release

I am currently in the middle of the debugging - the issue does not look related to the persistent store changes now. 2017-06-07 5:47 GMT+03:00 Dmitriy Setrakyan : > On Tue, Jun 6, 2017 at 1:21 AM, Semyon Boikov > wrote: > > > Does anybody monitor

Re: New version of Web Console released

Denis, >>>Sounds great! BTW, was this ticket resolved as a part of the release: >>> https://issues.apache.org/jira/browse/IGNITE-5303 (supporting multiple RDBMS configurations from the wizard) Yes we fixed this issue, now it is on testing with all major RDBMS. -- Alexey Kuznetsov

Re: New version of Web Console released

Muthu, >> Is the web console not part of or deploy-able from the ignite fabric distrib Yes. It is not part of binary distribution. You can build it from sources or use Docker image (see: https://hub.docker.com/r/apacheignite/web-console-standalone/tags/) >> .but i do not find any directory named

[jira] [Created] (IGNITE-5429) Affinity run: optimize partition reservations for caches in the same group

Semen Boikov created IGNITE-5429: Summary: Affinity run: optimize partition reservations for caches in the same group Key: IGNITE-5429 URL: https://issues.apache.org/jira/browse/IGNITE-5429 Project: