[jira] [Updated] (IGNITE-4317) Redesign Queries Screen

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-4317:
---
Assignee: Andrey Novikov  (was: Pavel Konstantinov)

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Attachments: chart settings.png, scan.png
>
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4317) Redesign Queries Screen

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766323#comment-15766323
 ] 

Pavel Konstantinov commented on IGNITE-4317:


'Allow non-collocated loins' doesn't work.
Query
"select count(*) from Person p
inner join Department d on d.id=p.depid
inner join Organization o on o.id = d.orgid"

returns the same result for both modes.

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Attachments: chart settings.png, scan.png
>
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4467) Web Console: Refactor CSS

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-4467:


 Summary: Web Console: Refactor CSS
 Key: IGNITE-4467
 URL: https://issues.apache.org/jira/browse/IGNITE-4467
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 1.8
Reporter: Alexey Kuznetsov
Assignee: Dmitriy Shabalin
 Fix For: 2.0


We need to refactor CSS styles to make them more components oriented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4391) Web Console: Implement grouping by company in Admin panel

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766295#comment-15766295
 ] 

Pavel Konstantinov commented on IGNITE-4391:


Tested. It is acceptable now.

> Web Console: Implement grouping by company in Admin panel
> -
>
> Key: IGNITE-4391
> URL: https://issues.apache.org/jira/browse/IGNITE-4391
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.0
>
>
> It will be useful to have different view on same data:
> # list by name (current)
> # group by company
> # group by country



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-4391) Web Console: Implement grouping by company in Admin panel

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-4391.
--

> Web Console: Implement grouping by company in Admin panel
> -
>
> Key: IGNITE-4391
> URL: https://issues.apache.org/jira/browse/IGNITE-4391
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> It will be useful to have different view on same data:
> # list by name (current)
> # group by company
> # group by country



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4466) Web console - Admin panel: show different message for 'Grant\Revoke admin' actions

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-4466:
--

 Summary: Web console - Admin panel: show different message for 
'Grant\Revoke admin' actions
 Key: IGNITE-4466
 URL: https://issues.apache.org/jira/browse/IGNITE-4466
 Project: Ignite
  Issue Type: Task
  Components: wizards
Reporter: Pavel Konstantinov
Priority: Trivial


Currently we show the same message for these two different actions. It is not 
clear what exactly was performed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4391) Web Console: Implement grouping by company in Admin panel

[Vasiliy Sisko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766263#comment-15766263
 ] 

Vasiliy Sisko commented on IGNITE-4391:
---

Tested. Implemented counting of values in dropdown filters.

> Web Console: Implement grouping by company in Admin panel
> -
>
> Key: IGNITE-4391
> URL: https://issues.apache.org/jira/browse/IGNITE-4391
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.0
>
>
> It will be useful to have different view on same data:
> # list by name (current)
> # group by company
> # group by country



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4465) Read-through is not properly working with multiple gets executed in parallel

[Valentin Kulichenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Valentin Kulichenko updated IGNITE-4465:

Attachment: ReadThroughTest.java

> Read-through is not properly working with multiple gets executed in parallel
> 
>
> Key: IGNITE-4465
> URL: https://issues.apache.org/jira/browse/IGNITE-4465
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.9
>
> Attachments: ReadThroughTest.java
>
>
> The issue is sporadic and very hard to isolate, however I managed to create a 
> test that reproduces it. Basically, the scenario is the following:
> * We have one server and one client.
> * The client creates a cache with read through enabled.
> * The client then executes bunch of jobs (number of jobs is bigger than 
> number of threads in server's public pool) asynchronously in parallel.
> * {{CacheStore.load()}} method is called more than once and invocations go 
> one after another (sometimes even in the same thread!) with an interval of a 
> bit more than one second, which is the duration of load (there is a 
> {{Thread.sleep(1000)}} in the implementation.
> * In addition, statistics show that number of misses go up to 50 which is 
> number of jobs. I would not expect more than 16 there. First 16 jobs executed 
> in parallel can all register miss at the same time before load happens. But 
> all consecutive execution must read the value from cache.
> Test is attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4465) Read-through is not properly working with multiple gets executed in parallel

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-4465:
---

 Summary: Read-through is not properly working with multiple gets 
executed in parallel
 Key: IGNITE-4465
 URL: https://issues.apache.org/jira/browse/IGNITE-4465
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.8
Reporter: Valentin Kulichenko
Priority: Critical
 Fix For: 1.9


The issue is sporadic and very hard to isolate, however I managed to create a 
test that reproduces it. Basically, the scenario is the following:
* We have one server and one client.
* The client creates a cache with read through enabled.
* The client then executes bunch of jobs (number of jobs is bigger than number 
of threads in server's public pool) asynchronously in parallel.
* {{CacheStore.load()}} method is called more than once and invocations go one 
after another (sometimes even in the same thread!) with an interval of a bit 
more than one second, which is the duration of load (there is a 
{{Thread.sleep(1000)}} in the implementation.
* In addition, statistics show that number of misses go up to 50 which is 
number of jobs. I would not expect more than 16 there. First 16 jobs executed 
in parallel can all register miss at the same time before load happens. But all 
consecutive execution must read the value from cache.

Test is attached.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4317) Redesign Queries Screen

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov resolved IGNITE-4317.

Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Andrey Novikov)

Fixed problem with 'Allow non-collocated joins'.

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Attachments: chart settings.png, scan.png
>
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4391) Web Console: Implement grouping by company in Admin panel

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-4391:
---
Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

> Web Console: Implement grouping by company in Admin panel
> -
>
> Key: IGNITE-4391
> URL: https://issues.apache.org/jira/browse/IGNITE-4391
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.0
>
>
> It will be useful to have different view on same data:
> # list by name (current)
> # group by company
> # group by country



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4348) Documentation: RDBMS Integration using Web Console

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-4348:
-
Attachment: SchemaImport-2.png

> Documentation: RDBMS Integration using Web Console
> --
>
> Key: IGNITE-4348
> URL: https://issues.apache.org/jira/browse/IGNITE-4348
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.0
>
> Attachments: SchemaImport-2.png, WP_20161220_11_33_55_Pro.jpg
>
>
> Ignite has a documentation which describes how to set up "automatic 
> persistence" relying on the schema-import tool.
> https://apacheignite-mix.readme.io/docs/automatic-persistence
> Let's create a similar one but basing it on Web Console capabilities briefly 
> listed on this page
> https://ignite.apache.org/features/rdbmsintegration.html
> The schema-import based document has to be removed after that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4396) Web console: Failed to edit File system checkpoint spi paths.

[Vasiliy Sisko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765954#comment-15765954
 ] 

Vasiliy Sisko commented on IGNITE-4396:
---

Tested. Fixed removing of rows.

> Web console: Failed to edit File system checkpoint spi paths.
> -
>
> Key: IGNITE-4396
> URL: https://issues.apache.org/jira/browse/IGNITE-4396
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 2.0
>
>
> # Add FIle system checkpoint spi configuration.
> # Add some paths.
> # Try to remove or edit path.
> angular.js:13920 TypeError: Cannot create property 'FS' on string 'b'
> at fn (eval at compile (angular.js:14817), :4:813)
> at expensiveCheckFn (angular.js:15906)
> at callback (angular.js:25885)
> at Scope.$eval (angular.js:17682)
> at Scope.$apply (angular.js:17782)
> at HTMLElement. (angular.js:25890)
> at HTMLElement.dispatch (jquery.js:5201)
> at HTMLElement.elemData.handle (jquery.js:5009)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4439) Create attribute based node filter

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765550#comment-15765550
 ] 

ASF GitHub Bot commented on IGNITE-4439:


GitHub user vkulichenko opened a pull request:

https://github.com/apache/ignite/pull/1369

IGNITE-4439 - Attribute based node filter



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vkulichenko/ignite ignite-4439

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1369.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 #1369


commit bc3da349d89d09aaf836a7de9d32edac7648c755
Author: Valentin Kulichenko 
Date:   2016-12-20T23:10:29Z

IGNITE-4439 - Attribute based node filter




> Create attribute based node filter
> --
>
> Key: IGNITE-4439
> URL: https://issues.apache.org/jira/browse/IGNITE-4439
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 1.9
>
>
> We have a {{CacheConfiguration.nodeFilter}} configuration property which 
> takes a predicate that defines on which nodes cache is deployed. Therefore 
> using it implies creating a new class and deploying it on all nodes.
> However, in vast majority of cases users filter out nodes based on custom 
> attributes, so it can be useful to provide such implementation out of the box.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4169) Data streamer mode for DML

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765170#comment-15765170
 ] 

Denis Magda commented on IGNITE-4169:
-

[~al.psc], please assign the ticket to me once you're done with it. I'll 
document the new parameters usage on the DML page. Presently we shouldn't 
modify it because I've not finished with its review yet. Will do this week.

> Data streamer mode for DML
> --
>
> Key: IGNITE-4169
> URL: https://issues.apache.org/jira/browse/IGNITE-4169
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> SQL INSERT and MERGE are supposed to support data streamer mode which should 
> be turned on by JDBC connection string param.
> Note: particular details of usage means and implementation of this mode, as 
> well as urgency of this feature are yet to be discussed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4230) Create documentation for the integration with Tableau

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765161#comment-15765161
 ] 

Denis Magda commented on IGNITE-4230:
-

Thanks Igor! Please give me some time for review.

> Create documentation for the integration with Tableau
> -
>
> Key: IGNITE-4230
> URL: https://issues.apache.org/jira/browse/IGNITE-4230
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.0
>
>
> Let's create a simple documentation that will show how to connect from 
> Tableau to Ignite and what steps have to be performed to fulfill this.
> The documentation has to be placed under this section:
> https://apacheignite-mix.readme.io/docs/overview-1
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Connecting-to-Ignite-from-Tableau-td12065.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4230) Create documentation for the integration with Tableau

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-4230:
---

Assignee: Denis Magda  (was: Igor Sapego)

> Create documentation for the integration with Tableau
> -
>
> Key: IGNITE-4230
> URL: https://issues.apache.org/jira/browse/IGNITE-4230
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.0
>
>
> Let's create a simple documentation that will show how to connect from 
> Tableau to Ignite and what steps have to be performed to fulfill this.
> The documentation has to be placed under this section:
> https://apacheignite-mix.readme.io/docs/overview-1
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Connecting-to-Ignite-from-Tableau-td12065.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4212) Ignite Benchmarking Simplification and Automation

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765156#comment-15765156
 ] 

Denis Magda commented on IGNITE-4212:
-

Oleg, we already create AMIs for AWS 
(https://apacheignite.readme.io/docs/aws-deployment).
When this feature is released all the benchmark will be a part of it.

> Ignite Benchmarking Simplification and Automation
> -
>
> Key: IGNITE-4212
> URL: https://issues.apache.org/jira/browse/IGNITE-4212
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Oleg Ostanin
> Fix For: 2.0
>
>
> There is a plenty of useful Yardstick benchmarks located in ignite-yardstick 
> module that is used by the community to check Ignite performance across 
> deployments of different configurations.
> However, it's not easy to start with the benchmarking process because the 
> user needs to download Ignite, build and set up benchmarks and only after 
> that run them.
> The goal of this task is to simplify the process in the following way:
> 1) ignite-yardstick benchmarks have to be pre-compiled and available with 
> every Ignite deliverable.
> 2) every deliverable must contain an executable (bat or sh file) with a clear 
> instruction on how to start a specific benchmark from the console.
> 3) the executable has to use some default yardstick configuration. The first 
> configuration should be intented for local execution (multicast IP finder) 
> and the second needs to be AWS oriented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4212) Ignite Benchmarking Simplification and Automation

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765151#comment-15765151
 ] 

Denis Magda commented on IGNITE-4212:
-

Summarizing the discussion happened on the dev list. Let's reconsider the task 
a bit.

We need to create "benchmarks" folder and put it under the root of an Apache 
Ignite distribution. The structure of this folder is shown below.

apache_ignite_root_folder
-- bin
-- examples
...
-- benchmarks
— bin (contains scripts needed to run the benchmarks)
— src (contains benchmarks sources and a pom.xml in order to create a 
project in an IDE instantaneously)
— config (configs for amazon and well as for local benchmarks execution)
— libs (compiled and ready-to-run benchmarks)
— README.txt (instructions how to run the benchmarks)

More details can be found here.

> Ignite Benchmarking Simplification and Automation
> -
>
> Key: IGNITE-4212
> URL: https://issues.apache.org/jira/browse/IGNITE-4212
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Oleg Ostanin
> Fix For: 2.0
>
>
> There is a plenty of useful Yardstick benchmarks located in ignite-yardstick 
> module that is used by the community to check Ignite performance across 
> deployments of different configurations.
> However, it's not easy to start with the benchmarking process because the 
> user needs to download Ignite, build and set up benchmarks and only after 
> that run them.
> The goal of this task is to simplify the process in the following way:
> 1) ignite-yardstick benchmarks have to be pre-compiled and available with 
> every Ignite deliverable.
> 2) every deliverable must contain an executable (bat or sh file) with a clear 
> instruction on how to start a specific benchmark from the console.
> 3) the executable has to use some default yardstick configuration. The first 
> configuration should be intented for local execution (multicast IP finder) 
> and the second needs to be AWS oriented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4348) Documentation: RDBMS Integration using Web Console

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-4348:
---

Assignee: Denis Magda  (was: Prachi Garg)

> Documentation: RDBMS Integration using Web Console
> --
>
> Key: IGNITE-4348
> URL: https://issues.apache.org/jira/browse/IGNITE-4348
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.0
>
> Attachments: WP_20161220_11_33_55_Pro.jpg
>
>
> Ignite has a documentation which describes how to set up "automatic 
> persistence" relying on the schema-import tool.
> https://apacheignite-mix.readme.io/docs/automatic-persistence
> Let's create a similar one but basing it on Web Console capabilities briefly 
> listed on this page
> https://ignite.apache.org/features/rdbmsintegration.html
> The schema-import based document has to be removed after that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4348) Documentation: RDBMS Integration using Web Console

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765089#comment-15765089
 ] 

Denis Magda edited comment on IGNITE-4348 at 12/20/16 7:53 PM:
---

Here is a sketch. Please provide your comments before I send it out to the 
designer. Let's discuss it on the dev list.
http://apache-ignite-developers.2346864.n4.nabble.com/Diagram-for-RDBMS-Schema-Import-with-Web-Console-td13196.html


was (Author: dmagda):
Here is a sketch. Please provide your comments before I send it out to the 
designer. Let's discuss it on the dev list.



> Documentation: RDBMS Integration using Web Console
> --
>
> Key: IGNITE-4348
> URL: https://issues.apache.org/jira/browse/IGNITE-4348
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.0
>
> Attachments: WP_20161220_11_33_55_Pro.jpg
>
>
> Ignite has a documentation which describes how to set up "automatic 
> persistence" relying on the schema-import tool.
> https://apacheignite-mix.readme.io/docs/automatic-persistence
> Let's create a similar one but basing it on Web Console capabilities briefly 
> listed on this page
> https://ignite.apache.org/features/rdbmsintegration.html
> The schema-import based document has to be removed after that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4348) Documentation: RDBMS Integration using Web Console

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-4348:

Attachment: WP_20161220_11_33_55_Pro.jpg

Here is a sketch. Please provide your comments before I send it out to the 
designer. Let's discuss it on the dev list.



> Documentation: RDBMS Integration using Web Console
> --
>
> Key: IGNITE-4348
> URL: https://issues.apache.org/jira/browse/IGNITE-4348
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.0
>
> Attachments: WP_20161220_11_33_55_Pro.jpg
>
>
> Ignite has a documentation which describes how to set up "automatic 
> persistence" relying on the schema-import tool.
> https://apacheignite-mix.readme.io/docs/automatic-persistence
> Let's create a similar one but basing it on Web Console capabilities briefly 
> listed on this page
> https://ignite.apache.org/features/rdbmsintegration.html
> The schema-import based document has to be removed after that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4269) Implement batch statements in JDBC driver

[Alexander Paschenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764858#comment-15764858
 ] 

Alexander Paschenko commented on IGNITE-4269:
-

Per recommendation from [~dsetrakyan] on dev list, working on removing 
redundant query tasks from JDBC driver in case of DML statements.

> Implement batch statements in JDBC driver
> -
>
> Key: IGNITE-4269
> URL: https://issues.apache.org/jira/browse/IGNITE-4269
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> In the course of review of initial DML implementation, it has been agreed 
> that the first attempt to implement batching (via series of individual 
> queries) is rather incorrect (effectively series of individual queries 
> instead of one larger query). So it's been decided not to include batching 
> into initial release and rather implement it the right way shortly in nearest 
> releases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4169) Data streamer mode for DML

[Alexander Paschenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764852#comment-15764852
 ] 

Alexander Paschenko commented on IGNITE-4169:
-

Per recommendation from [~dmagda] on dev list, added params for per node buffer 
size and parallel ops count. Working on example for streamed SQL INSERTs.

> Data streamer mode for DML
> --
>
> Key: IGNITE-4169
> URL: https://issues.apache.org/jira/browse/IGNITE-4169
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> SQL INSERT and MERGE are supposed to support data streamer mode which should 
> be turned on by JDBC connection string param.
> Note: particular details of usage means and implementation of this mode, as 
> well as urgency of this feature are yet to be discussed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4462) Remove grid name from HadoopIgfsEndpoint

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764655#comment-15764655
 ] 

ASF GitHub Bot commented on IGNITE-4462:


GitHub user taras-ledkov opened a pull request:

https://github.com/apache/ignite/pull/1368

IGNITE-4462: Remove grid name from HadoopIgfsEndpoint



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4462

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1368.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 #1368


commit 128e4d737b8a58585d3703917c7d1fc186796821
Author: tledkov-gridgain 
Date:   2016-12-20T16:52:49Z

IGNITE-4462: Remove grid name from HadoopIgfsEndpoint




> Remove grid name from HadoopIgfsEndpoint
> 
>
> Key: IGNITE-4462
> URL: https://issues.apache.org/jira/browse/IGNITE-4462
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.8
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> When the {{HadoopIgfsWrapper}} creates IGFS delegate with it must not find 
> the ignite instance by the the name. 
> The collection of available ignite instances must be scanned and the first 
> instance with the target file system will be used If the several nodes are 
> available on the specified host  / localhost / current VM process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4157) Use discovery custom messages instead of marshaller cache

[Sergey Chugunov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764641#comment-15764641
 ] 

Sergey Chugunov edited comment on IGNITE-4157 at 12/20/16 4:50 PM:
---

Implemented happy-path for #4, *Use communication messages to request missing 
mappings instead of discovery messages*.


was (Author: sergey-chugunov):
Implemented happy-path for #4.

> Use discovery custom messages instead of marshaller cache
> -
>
> Key: IGNITE-4157
> URL: https://issues.apache.org/jira/browse/IGNITE-4157
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
> Fix For: 2.0
>
>
> Currently we use system caches for keeping classname to class ID mapping and 
> for storing binary metadata
> This has several serious disadvantages:
> 1) We need to introduce at least two additional thread pools for each of 
> these caches
> 2) Since cache operations require stable topology, registering a class ID or 
> updating metadata inside a transaction or another cache operation is tricky 
> and deadlock-prone.
> 3) It may be beneficial in some cases to have nodes with no caches at all, 
> currently this is impossible because system caches are always present.
> 4) Reading binary metadata leads to huge local contention, caching metadata 
> values in a local map doubles memory consumption
> I suggest we use discovery custom events for these purposes. Each node will 
> have a corresponding local map (state) which will be updated inside custom 
> event handler. From the first point of view, this should remove all the 
> disadvantages above.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4157) Use discovery custom messages instead of marshaller cache

[Sergey Chugunov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764641#comment-15764641
 ] 

Sergey Chugunov commented on IGNITE-4157:
-

Implemented happy-path for #4.

> Use discovery custom messages instead of marshaller cache
> -
>
> Key: IGNITE-4157
> URL: https://issues.apache.org/jira/browse/IGNITE-4157
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
> Fix For: 2.0
>
>
> Currently we use system caches for keeping classname to class ID mapping and 
> for storing binary metadata
> This has several serious disadvantages:
> 1) We need to introduce at least two additional thread pools for each of 
> these caches
> 2) Since cache operations require stable topology, registering a class ID or 
> updating metadata inside a transaction or another cache operation is tricky 
> and deadlock-prone.
> 3) It may be beneficial in some cases to have nodes with no caches at all, 
> currently this is impossible because system caches are always present.
> 4) Reading binary metadata leads to huge local contention, caching metadata 
> values in a local map doubles memory consumption
> I suggest we use discovery custom events for these purposes. Each node will 
> have a corresponding local map (state) which will be updated inside custom 
> event handler. From the first point of view, this should remove all the 
> disadvantages above.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1443) CPP: Implement cache continuous queries.

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764624#comment-15764624
 ] 

Pavel Tupitsyn commented on IGNITE-1443:


Looks good. Merged to master.

> CPP: Implement cache continuous queries.
> 
>
> Key: IGNITE-1443
> URL: https://issues.apache.org/jira/browse/IGNITE-1443
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: cpp, important, roadmap
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1443) CPP: Implement cache continuous queries.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764620#comment-15764620
 ] 

ASF GitHub Bot commented on IGNITE-1443:


Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/1343


> CPP: Implement cache continuous queries.
> 
>
> Key: IGNITE-1443
> URL: https://issues.apache.org/jira/browse/IGNITE-1443
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: cpp, important, roadmap
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1443) CPP: Implement cache continuous queries.

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-1443:
---
Issue Type: New Feature  (was: Task)

> CPP: Implement cache continuous queries.
> 
>
> Key: IGNITE-1443
> URL: https://issues.apache.org/jira/browse/IGNITE-1443
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: cpp, important, roadmap
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4212) Ignite Benchmarking Simplification and Automation

[Oleg Ostanin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764524#comment-15764524
 ] 

Oleg Ostanin commented on IGNITE-4212:
--

I've managed to run a compiled ignite-yardstick module on AWS and for now it 
takes some extra effort to configure instances after they have been started. 
I think if we want to make benchmarks run a single step operation we need to go 
further and create a custom properly pre-configured AMI.

> Ignite Benchmarking Simplification and Automation
> -
>
> Key: IGNITE-4212
> URL: https://issues.apache.org/jira/browse/IGNITE-4212
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Oleg Ostanin
> Fix For: 2.0
>
>
> There is a plenty of useful Yardstick benchmarks located in ignite-yardstick 
> module that is used by the community to check Ignite performance across 
> deployments of different configurations.
> However, it's not easy to start with the benchmarking process because the 
> user needs to download Ignite, build and set up benchmarks and only after 
> that run them.
> The goal of this task is to simplify the process in the following way:
> 1) ignite-yardstick benchmarks have to be pre-compiled and available with 
> every Ignite deliverable.
> 2) every deliverable must contain an executable (bat or sh file) with a clear 
> instruction on how to start a specific benchmark from the console.
> 3) the executable has to use some default yardstick configuration. The first 
> configuration should be intented for local execution (multicast IP finder) 
> and the second needs to be AWS oriented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4424) REPLICATED cache isn't synced across nodes

[Anton Vinogradov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764520#comment-15764520
 ] 

Anton Vinogradov commented on IGNITE-4424:
--

Problem found. 
cctx.mvcc().addAtomicFuture(...) happens not under topology.readlock (it 
already released)
So, exchange is not waiting for putAll operation finish.

Dummy hotfix (relocation of this code to readlock section solved the issue).
Fixing code in proper way.

> REPLICATED cache isn't synced across nodes
> --
>
> Key: IGNITE-4424
> URL: https://issues.apache.org/jira/browse/IGNITE-4424
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.8
>Reporter: Andrew Mashenkov
>Assignee: Anton Vinogradov
>Priority: Blocker
> Fix For: 2.0
>
> Attachments: ReplicatedCacheRebalanceFails.java, 
> ReplicatedCacheRebalanceFails.java, ignite-d8e433e4.log
>
>
> Replicated cache sometimes won't sync across nodes properly.
> PFA a reproducer code.
> All nodes are started at the same time on different machines:
> * Ignition.start() // Blocks until node is up
> * Only one of the nodes performs next: getOrCreateCache() then putAll() 
> * All the other nodes block on this before proceeding. 
> * All of the nodes perform next:
> ** getOrCreateCache() // Again
> ** cache.localSize(CachePeekMode.ALL)
> All nodes should see filled cache, but sometimes some nodes see empty cache. 
> LocalSize call can be replaced by iterating over cache, but result will be 
> same.
> Much more rarely, cluster degradation is possible and one part of cluster see 
> empty cache while another see filled cache. Logs contain no errors at all. It 
> takes about two hours running test in infinite loop to catch this rare error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4372) Set up code coverage reports

[Ksenia Rybakova (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764480#comment-15764480
 ] 

Ksenia Rybakova commented on IGNITE-4372:
-

- SonarQube + Jacoco was choosen. I've created experimental configs at 
TeamCity. Jacoco reports are generated during tests execution. But when I try 
to generate sonar statistics with code coverage, sonar goal fails with an error
{noformat}
[ERROR] Failed to execute goal 
org.sonarsource.scanner.maven:sonar-maven-plugin:3.1.1:sonar (default-cli) on 
project apache-ignite: Line 252 is out of range in the file 
src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java (lines: 
249)
{noformat}
Workaround/solution is not found so far.

> Set up code coverage reports
> 
>
> Key: IGNITE-4372
> URL: https://issues.apache.org/jira/browse/IGNITE-4372
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4372) Set up code coverage reports

[Ksenia Rybakova (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764480#comment-15764480
 ] 

Ksenia Rybakova edited comment on IGNITE-4372 at 12/20/16 3:41 PM:
---

- SonarQube + Jacoco was choosen. I've created experimental configs at 
TeamCity. Jacoco reports are generated during tests execution. But when I try 
to generate sonar statistics with code coverage, sonar goal fails with an error
{noformat}
[ERROR] Failed to execute goal 
org.sonarsource.scanner.maven:sonar-maven-plugin:3.1.1:sonar (default-cli) on 
project apache-ignite: Line 252 is out of range in the file 
src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java (lines: 
249)
{noformat}
Workaround/fix is not found so far.


was (Author: krybakova):
- SonarQube + Jacoco was choosen. I've created experimental configs at 
TeamCity. Jacoco reports are generated during tests execution. But when I try 
to generate sonar statistics with code coverage, sonar goal fails with an error
{noformat}
[ERROR] Failed to execute goal 
org.sonarsource.scanner.maven:sonar-maven-plugin:3.1.1:sonar (default-cli) on 
project apache-ignite: Line 252 is out of range in the file 
src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java (lines: 
249)
{noformat}
Workaround/solution is not found so far.

> Set up code coverage reports
> 
>
> Key: IGNITE-4372
> URL: https://issues.apache.org/jira/browse/IGNITE-4372
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4464) JclLogger ignores IGNITE_QUIET system property

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-4464:
-
Assignee: (was: Andrew Mashenkov)

> JclLogger ignores IGNITE_QUIET system property
> --
>
> Key: IGNITE-4464
> URL: https://issues.apache.org/jira/browse/IGNITE-4464
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>  Labels: easyfix, newbie
> Fix For: 2.0
>
>
> {{JclLogger}} writes in quiet mode into {{System.out}} regardless of the 
> value of {{IGNITE_QUEIT}} system property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4464) JclLogger ignores IGNITE_QUIET system property

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-4464:
-
Labels: easyfix newbie  (was: easyfix)

> JclLogger ignores IGNITE_QUIET system property
> --
>
> Key: IGNITE-4464
> URL: https://issues.apache.org/jira/browse/IGNITE-4464
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: easyfix, newbie
> Fix For: 2.0
>
>
> {{JclLogger}} writes in quiet mode into {{System.out}} regardless of the 
> value of {{IGNITE_QUEIT}} system property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4464) JclLogger ignores IGNITE_QUIET system property

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-4464:
-
Labels: easyfix  (was: )

> JclLogger ignores IGNITE_QUIET system property
> --
>
> Key: IGNITE-4464
> URL: https://issues.apache.org/jira/browse/IGNITE-4464
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: easyfix, newbie
> Fix For: 2.0
>
>
> {{JclLogger}} writes in quiet mode into {{System.out}} regardless of the 
> value of {{IGNITE_QUEIT}} system property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4464) JclLogger ignores IGNITE_QUIET system property

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-4464:


 Summary: JclLogger ignores IGNITE_QUIET system property
 Key: IGNITE-4464
 URL: https://issues.apache.org/jira/browse/IGNITE-4464
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.7
Reporter: Andrew Mashenkov
Assignee: Andrew Mashenkov
 Fix For: 2.0


{{Slf4jLogger}} writes in quiet mode into {{System.out}} regardless of the 
value of {{IGNITE_QUEIT}} system property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4464) JclLogger ignores IGNITE_QUIET system property

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-4464:
-
Description: {{JclLogger}} writes in quiet mode into {{System.out}} 
regardless of the value of {{IGNITE_QUEIT}} system property.  (was: 
{{Slf4jLogger}} writes in quiet mode into {{System.out}} regardless of the 
value of {{IGNITE_QUEIT}} system property.)

> JclLogger ignores IGNITE_QUIET system property
> --
>
> Key: IGNITE-4464
> URL: https://issues.apache.org/jira/browse/IGNITE-4464
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.0
>
>
> {{JclLogger}} writes in quiet mode into {{System.out}} regardless of the 
> value of {{IGNITE_QUEIT}} system property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4248) Slf4jLogger ignores IGNITE_QUIET system property

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764383#comment-15764383
 ] 

ASF GitHub Bot commented on IGNITE-4248:


GitHub user AMashenkov opened a pull request:

https://github.com/apache/ignite/pull/1367

IGNITE-4248: Slf4jLogger ignores IGNITE_QUIET system property

Fixed.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4248

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1367.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 #1367


commit 295859884fa48f05313f26fd3b33b6c85c64a09e
Author: Andrey V. Mashenkov 
Date:   2016-12-20T14:54:34Z

Minors




> Slf4jLogger ignores IGNITE_QUIET system property
> 
>
> Key: IGNITE-4248
> URL: https://issues.apache.org/jira/browse/IGNITE-4248
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
> Fix For: 2.0
>
>
> {{Slf4jLogger}} writes in quiet mode into {{System.out}} regardless of the 
> value of {{IGNITE_QUEIT}} system property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2466) OutOfMemory when PRIMARY_SYNC mode is used

[Dmitry Karachentsev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764329#comment-15764329
 ] 

Dmitry Karachentsev commented on IGNITE-2466:
-

[PR#1366|https://github.com/apache/ignite/pull/1366]

> OutOfMemory when PRIMARY_SYNC mode is used
> --
>
> Key: IGNITE-2466
> URL: https://issues.apache.org/jira/browse/IGNITE-2466
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
> Attachments: MemTest.java, example-ignite.xml
>
>
> To reproduce, run two server nodes with 2g of heap each and then MemTest. 
> Servers will fail with OOME. If backups are disabled or there is only one 
> server node, it works.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4109) BinaryType.isEnum() throws an exception if typeId==0

[Dmitry Karachentsev (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Karachentsev reassigned IGNITE-4109:
---

Assignee: Dmitry Karachentsev

> BinaryType.isEnum() throws an exception if typeId==0
> 
>
> Key: IGNITE-4109
> URL: https://issues.apache.org/jira/browse/IGNITE-4109
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> If {{typeId==0}} and full class name is written in the binary format, 
> {{BinaryType.isEnum()}} method fails with the exception:
> {noformat}
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to get 
> binary type details [typeId=0]
>   at 
> org.apache.ignite.internal.binary.BinaryTypeProxy.target(BinaryTypeProxy.java:99)
>  ~[ignite-core-1.6.7.jar:1.6.7]
>   at 
> org.apache.ignite.internal.binary.BinaryTypeProxy.isEnum(BinaryTypeProxy.java:86)
>  ~[ignite-core-1.6.7.jar:1.6.7]
> {noformat}
> This happens because {{BinaryTypeProxy.target()}} method ignores this case. 
> If {{typeId==0}}, It should look up full class name from the object and 
> convert it to the actual type ID before trying to fetch metadata.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4248) Slf4jLogger ignores IGNITE_QUIET system property

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-4248:
-
Fix Version/s: 2.0

> Slf4jLogger ignores IGNITE_QUIET system property
> 
>
> Key: IGNITE-4248
> URL: https://issues.apache.org/jira/browse/IGNITE-4248
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
> Fix For: 2.0
>
>
> {{Slf4jLogger}} writes in quiet mode into {{System.out}} regardless of the 
> value of {{IGNITE_QUEIT}} system property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4230) Create documentation for the integration with Tableau

[Igor Sapego (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764270#comment-15764270
 ] 

Igor Sapego edited comment on IGNITE-4230 at 12/20/16 1:56 PM:
---

Draft can be found here: https://apacheignite-mix.readme.io/v1.8/docs/tableau.


was (Author: isapego):
Draft can be found here: 
https://dash.readme.io/project/apacheignite-mix/v1.8/docs/tableau.

> Create documentation for the integration with Tableau
> -
>
> Key: IGNITE-4230
> URL: https://issues.apache.org/jira/browse/IGNITE-4230
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.0
>
>
> Let's create a simple documentation that will show how to connect from 
> Tableau to Ignite and what steps have to be performed to fulfill this.
> The documentation has to be placed under this section:
> https://apacheignite-mix.readme.io/docs/overview-1
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Connecting-to-Ignite-from-Tableau-td12065.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4454) Web console: add information on query panel UI about node query was executed on

[Alina Goncarko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764268#comment-15764268
 ] 

Alina Goncarko commented on IGNITE-4454:


[~pkonstantinov], could You please reply to my comment? 

> Web console: add information on query panel  UI about node query was executed 
> on
> 
>
> Key: IGNITE-4454
> URL: https://issues.apache.org/jira/browse/IGNITE-4454
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alina Goncarko
>Priority: Minor
>
> Currently we show only query text  and do not show node in case of 'Execute 
> on selected node'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4230) Create documentation for the integration with Tableau

[Igor Sapego (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764270#comment-15764270
 ] 

Igor Sapego commented on IGNITE-4230:
-

Draft can be found here: 
https://dash.readme.io/project/apacheignite-mix/v1.8/docs/tableau.

> Create documentation for the integration with Tableau
> -
>
> Key: IGNITE-4230
> URL: https://issues.apache.org/jira/browse/IGNITE-4230
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.0
>
>
> Let's create a simple documentation that will show how to connect from 
> Tableau to Ignite and what steps have to be performed to fulfill this.
> The documentation has to be placed under this section:
> https://apacheignite-mix.readme.io/docs/overview-1
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Connecting-to-Ignite-from-Tableau-td12065.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4248) Slf4jLogger ignores IGNITE_QUIET system property

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov reassigned IGNITE-4248:


Assignee: Andrew Mashenkov

> Slf4jLogger ignores IGNITE_QUIET system property
> 
>
> Key: IGNITE-4248
> URL: https://issues.apache.org/jira/browse/IGNITE-4248
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>
> {{Slf4jLogger}} writes in quiet mode into {{System.out}} regardless of the 
> value of {{IGNITE_QUEIT}} system property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4457) Define cache plugin API in .NET

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-4457:
---
Summary: Define cache plugin API in .NET  (was: .NET: Define cache plugin 
API in .NET)

> Define cache plugin API in .NET
> ---
>
> Key: IGNITE-4457
> URL: https://issues.apache.org/jira/browse/IGNITE-4457
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Define cache plugin API in .NET similar to Java API:
> * {{CacheConfiguration.PluginConfigurations}}
> * {{ICachePluginProvider}}
> * {{ICachePluginContext}}
> Fundamental difference to Ignite plugins (IGNITE-4441), which are local, is 
> that {{CachePluginConfiguration}} is sent to remote nodes and providers are 
> created there. So we'll need {{PlatformCachePluginConfiguration}} and 
> {{PlatformCachePluginProvider}} on Java side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4457) .NET: Define cache plugin API in .NET

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-4457:
--

Assignee: Pavel Tupitsyn

> .NET: Define cache plugin API in .NET
> -
>
> Key: IGNITE-4457
> URL: https://issues.apache.org/jira/browse/IGNITE-4457
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Define cache plugin API in .NET similar to Java API:
> * {{CacheConfiguration.PluginConfigurations}}
> * {{ICachePluginProvider}}
> * {{ICachePluginContext}}
> Fundamental difference to Ignite plugins (IGNITE-4441), which are local, is 
> that {{CachePluginConfiguration}} is sent to remote nodes and providers are 
> created there. So we'll need {{PlatformCachePluginConfiguration}} and 
> {{PlatformCachePluginProvider}} on Java side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4359) .NET: Support DateTime properties in LINQ

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn resolved IGNITE-4359.

Resolution: Fixed
  Assignee: (was: Pavel Tupitsyn)

> .NET: Support DateTime properties in LINQ
> -
>
> Key: IGNITE-4359
> URL: https://issues.apache.org/jira/browse/IGNITE-4359
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Support {{DateTime}} properties such as Year, Month, Day in LINQ. See how 
> {{String.Length}} property is supported in {{MethodVisitor}}.
> See http://www.h2database.com/html/functions.html for supported SQL functions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4428) Hadoop: move HadoopMapReducePlanner and dependent classes to public space.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4428:

Priority: Major  (was: Critical)

> Hadoop: move HadoopMapReducePlanner and dependent classes to public space.
> --
>
> Key: IGNITE-4428
> URL: https://issues.apache.org/jira/browse/IGNITE-4428
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> Currently these classes are located in private package. Need to move the to 
> public.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2466) OutOfMemory when PRIMARY_SYNC mode is used

[Dmitry Karachentsev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764051#comment-15764051
 ] 

Dmitry Karachentsev commented on IGNITE-2466:
-

Semen,

I've implemented your suggestion, but anyway it looks like incomplete solution. 
Because we count number of messages, not their size.
F.e. in attached test, with such approach on default settings, OOME will be 
thrown. So we need reduce message queue limit down to 128. With acknowledge 
check everything will be fine, without it - again OOME.

Maybe better solution would be additionally check heap state and message sizes 
received from client node? If there is a risk of OOME - stop receiving them 
(only for messages from clients).

> OutOfMemory when PRIMARY_SYNC mode is used
> --
>
> Key: IGNITE-2466
> URL: https://issues.apache.org/jira/browse/IGNITE-2466
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
> Attachments: MemTest.java, example-ignite.xml
>
>
> To reproduce, run two server nodes with 2g of heap each and then MemTest. 
> Servers will fail with OOME. If backups are disabled or there is only one 
> server node, it works.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4396) Web console: Failed to edit File system checkpoint spi paths.

[Dmitriy Shabalin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764024#comment-15764024
 ] 

Dmitriy Shabalin commented on IGNITE-4396:
--

added fix


> Web console: Failed to edit File system checkpoint spi paths.
> -
>
> Key: IGNITE-4396
> URL: https://issues.apache.org/jira/browse/IGNITE-4396
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Shabalin
> Fix For: 2.0
>
>
> # Add FIle system checkpoint spi configuration.
> # Add some paths.
> # Try to remove or edit path.
> angular.js:13920 TypeError: Cannot create property 'FS' on string 'b'
> at fn (eval at compile (angular.js:14817), :4:813)
> at expensiveCheckFn (angular.js:15906)
> at callback (angular.js:25885)
> at Scope.$eval (angular.js:17682)
> at Scope.$apply (angular.js:17782)
> at HTMLElement. (angular.js:25890)
> at HTMLElement.dispatch (jquery.js:5201)
> at HTMLElement.elemData.handle (jquery.js:5009)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4317) Redesign Queries Screen

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763837#comment-15763837
 ] 

Pavel Konstantinov edited comment on IGNITE-4317 at 12/20/16 10:12 AM:
---

Tested with demo mode:
# the option 'allow non-collocated joins' is unavailable (unclickable) in demo 
mode


was (Author: pkonstantinov):
Tested with demo mode:
# the option 'allow non-collocated joins' is unavailable in demo mode

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Attachments: chart settings.png, scan.png
>
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4317) Redesign Queries Screen

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-4317:
---
Assignee: Andrey Novikov  (was: Pavel Konstantinov)

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Attachments: chart settings.png, scan.png
>
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4269) Implement batch statements in JDBC driver

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4269:

Fix Version/s: (was: 1.8)
   2.0

> Implement batch statements in JDBC driver
> -
>
> Key: IGNITE-4269
> URL: https://issues.apache.org/jira/browse/IGNITE-4269
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> In the course of review of initial DML implementation, it has been agreed 
> that the first attempt to implement batching (via series of individual 
> queries) is rather incorrect (effectively series of individual queries 
> instead of one larger query). So it's been decided not to include batching 
> into initial release and rather implement it the right way shortly in nearest 
> releases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4317) Redesign Queries Screen

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763837#comment-15763837
 ] 

Pavel Konstantinov commented on IGNITE-4317:


Tested with demo mode:
# the option 'allow non-collocated joins' is unavailable in demo mode

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Attachments: chart settings.png, scan.png
>
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4268:

Affects Version/s: 1.8

> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond 
> to key or its fields - direct modification would probably damage the index as 
> well as hash map integrity, so UPDATE for such cases would need to do first 
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be 
> implemented in later releases shortly to deliver initial implementation on 
> time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4269) Implement batch statements in JDBC driver

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4269:

Component/s: SQL

> Implement batch statements in JDBC driver
> -
>
> Key: IGNITE-4269
> URL: https://issues.apache.org/jira/browse/IGNITE-4269
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> In the course of review of initial DML implementation, it has been agreed 
> that the first attempt to implement batching (via series of individual 
> queries) is rather incorrect (effectively series of individual queries 
> instead of one larger query). So it's been decided not to include batching 
> into initial release and rather implement it the right way shortly in nearest 
> releases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4391) Web Console: Implement grouping by company in Admin panel

[Dmitriy Shabalin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763834#comment-15763834
 ] 

Dmitriy Shabalin commented on IGNITE-4391:
--

Fixed, pls check it

> Web Console: Implement grouping by company in Admin panel
> -
>
> Key: IGNITE-4391
> URL: https://issues.apache.org/jira/browse/IGNITE-4391
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
>
> It will be useful to have different view on same data:
> # list by name (current)
> # group by company
> # group by country



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4268:

Component/s: SQL

> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond 
> to key or its fields - direct modification would probably damage the index as 
> well as hash map integrity, so UPDATE for such cases would need to do first 
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be 
> implemented in later releases shortly to deliver initial implementation on 
> time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4169) Data streamer mode for DML

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4169:

Fix Version/s: (was: 1.8)
   2.0

> Data streamer mode for DML
> --
>
> Key: IGNITE-4169
> URL: https://issues.apache.org/jira/browse/IGNITE-4169
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> SQL INSERT and MERGE are supposed to support data streamer mode which should 
> be turned on by JDBC connection string param.
> Note: particular details of usage means and implementation of this mode, as 
> well as urgency of this feature are yet to be discussed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4268:

Fix Version/s: 2.0

> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond 
> to key or its fields - direct modification would probably damage the index as 
> well as hash map integrity, so UPDATE for such cases would need to do first 
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be 
> implemented in later releases shortly to deliver initial implementation on 
> time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4169) Data streamer mode for DML

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4169:

Affects Version/s: 1.8

> Data streamer mode for DML
> --
>
> Key: IGNITE-4169
> URL: https://issues.apache.org/jira/browse/IGNITE-4169
> Project: Ignite
>  Issue Type: New Feature
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> SQL INSERT and MERGE are supposed to support data streamer mode which should 
> be turned on by JDBC connection string param.
> Note: particular details of usage means and implementation of this mode, as 
> well as urgency of this feature are yet to be discussed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1521) Exception when running sql benchmark on AWS

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1521:

Component/s: (was: SQL)
 yardstick

> Exception when running sql benchmark on AWS
> ---
>
> Key: IGNITE-1521
> URL: https://issues.apache.org/jira/browse/IGNITE-1521
> Project: Ignite
>  Issue Type: Bug
>  Components: yardstick
>Affects Versions: ignite-1.4
>Reporter: Ilya Suntsov
>
> 1. I fork this repo: https://github.com/apacheignite/yardstick-ignite
> 2. Clone it
> 3. Used the following docs for start SQL benchmarks on AWS:
> https://github.com/yardstick-benchmarks/yardstick-docker
> And got the following exception:
> {noformat}
> ERROR: Shutting down benchmark driver to unexpected exception.
> Type '--help' for usage.
> java.lang.NoSuchMethodError: 
> org.apache.ignite.internal.processors.cache.query.GridCacheTwoStepQuery.(Ljava/util/Set;Ljava/lang/String;[Ljava/lang/Object;)V
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:216)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:859)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:807)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:662)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:660)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:660)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:618)
>   at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:85)
>   at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:61)
>   at 
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-2143) inner join produce wrong result and is very slow

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-2143.
-
   Resolution: Duplicate
Fix Version/s: 1.8

> inner join produce wrong result and is very slow
> 
>
> Key: IGNITE-2143
> URL: https://issues.apache.org/jira/browse/IGNITE-2143
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5.0.final
> Environment: 3 nodes in docker containers.
>Reporter: Sergey Soldatov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: config.xml, ignite-cache-1.0.0.jar
>
>
> I have following query for gitarchive records processing.  
> {code}
> select 
>  lang, count(distinct ForkTable.repo_url) as cnt 
> from (
>  select repo_url, lang from gitrecord where type = 'ForkEvent' and 
>  lang is not null group by lang, repo_url) as ForkTable 
> inner join (
>  select repo_url, html_url from gitrecord where type='PullRequestEvent'   
>  
>  group by repo_url, html_url) as PullTable 
> on 
>  ForkTable.repo_url = PullTable.repo_url 
> group by lang 
> order by cnt desc
> {code}
> And there are two major problems:
> 1. It produces an incorrect result if it's running in cluster mode.
> 2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
> Spark for the same query
> Steps to reproduce:
> 1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
> {code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
> 2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
> 3. run ignite with attached config.xml 
> 4. run spark-shell
> {code}
> spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
> http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
> /usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
> spark://{spark-master}:7077
> {code}
> 5. load data and execute the query:
> {code}
> import org.apache.ignite._
> import org.apache.ignite.configuration._
> import org.apache.ignite.cache.query._
> import org.apache.ignite.spark._
> import org.apache.ignite.lang.IgniteBiPredicate
> import io.dtk._
> val df = sqlContext.read.json("/Data/*.gz")
> Ignition.setClientMode(true)
> val cacheName = "gitrecords"
> val rdd = df.select("id", "repo.url", 
> "payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
>  => (row.getString(0), new GitRecord(0, 
> row.getString(1),row.getString(2),row.getString(3),row.getString(4
> val cfg = new 
> CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
> val ic = new IgniteContext[String,GitRecord](sc, 
> "/usr/lib/ignite-hadoop/config/config.xml")
> val sharedRDD = ic.fromCache(cfg)
> sharedRDD.savePairs(rdd)
> sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as cnt from 
> (select repo_url, lang from gitrecord where type = 'ForkEvent' and lang is 
> not null group by lang, repo_url) as ForkTable inner join (select repo_url, 
> html_url from gitrecord where type='PullRequestEvent' group by repo_url, 
> html_url) as PullTable on ForkTable.repo_url = PullTable.repo_url group by 
> lang order by cnt desc").show
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2143) inner join produce wrong result and is very slow

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-2143.
---

> inner join produce wrong result and is very slow
> 
>
> Key: IGNITE-2143
> URL: https://issues.apache.org/jira/browse/IGNITE-2143
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5.0.final
> Environment: 3 nodes in docker containers.
>Reporter: Sergey Soldatov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: config.xml, ignite-cache-1.0.0.jar
>
>
> I have following query for gitarchive records processing.  
> {code}
> select 
>  lang, count(distinct ForkTable.repo_url) as cnt 
> from (
>  select repo_url, lang from gitrecord where type = 'ForkEvent' and 
>  lang is not null group by lang, repo_url) as ForkTable 
> inner join (
>  select repo_url, html_url from gitrecord where type='PullRequestEvent'   
>  
>  group by repo_url, html_url) as PullTable 
> on 
>  ForkTable.repo_url = PullTable.repo_url 
> group by lang 
> order by cnt desc
> {code}
> And there are two major problems:
> 1. It produces an incorrect result if it's running in cluster mode.
> 2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
> Spark for the same query
> Steps to reproduce:
> 1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
> {code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
> 2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
> 3. run ignite with attached config.xml 
> 4. run spark-shell
> {code}
> spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
> http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
> /usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
> spark://{spark-master}:7077
> {code}
> 5. load data and execute the query:
> {code}
> import org.apache.ignite._
> import org.apache.ignite.configuration._
> import org.apache.ignite.cache.query._
> import org.apache.ignite.spark._
> import org.apache.ignite.lang.IgniteBiPredicate
> import io.dtk._
> val df = sqlContext.read.json("/Data/*.gz")
> Ignition.setClientMode(true)
> val cacheName = "gitrecords"
> val rdd = df.select("id", "repo.url", 
> "payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
>  => (row.getString(0), new GitRecord(0, 
> row.getString(1),row.getString(2),row.getString(3),row.getString(4
> val cfg = new 
> CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
> val ic = new IgniteContext[String,GitRecord](sc, 
> "/usr/lib/ignite-hadoop/config/config.xml")
> val sharedRDD = ic.fromCache(cfg)
> sharedRDD.savePairs(rdd)
> sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as cnt from 
> (select repo_url, lang from gitrecord where type = 'ForkEvent' and lang is 
> not null group by lang, repo_url) as ForkTable inner join (select repo_url, 
> html_url from gitrecord where type='PullRequestEvent' group by repo_url, 
> html_url) as PullTable on ForkTable.repo_url = PullTable.repo_url group by 
> lang order by cnt desc").show
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2143) inner join produce wrong result and is very slow

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763826#comment-15763826
 ] 

Vladimir Ozerov commented on IGNITE-2143:
-

HI Sergey,

AFAIK problem with COUNT(DISTINCT) and GROUP BY clause was fixed some time ago: 
IGNITE-3448. Closing this ticket as duplicate. Please feel free to re-open if 
the problem is still there.

> inner join produce wrong result and is very slow
> 
>
> Key: IGNITE-2143
> URL: https://issues.apache.org/jira/browse/IGNITE-2143
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5.0.final
> Environment: 3 nodes in docker containers.
>Reporter: Sergey Soldatov
>Priority: Critical
> Attachments: config.xml, ignite-cache-1.0.0.jar
>
>
> I have following query for gitarchive records processing.  
> {code}
> select 
>  lang, count(distinct ForkTable.repo_url) as cnt 
> from (
>  select repo_url, lang from gitrecord where type = 'ForkEvent' and 
>  lang is not null group by lang, repo_url) as ForkTable 
> inner join (
>  select repo_url, html_url from gitrecord where type='PullRequestEvent'   
>  
>  group by repo_url, html_url) as PullTable 
> on 
>  ForkTable.repo_url = PullTable.repo_url 
> group by lang 
> order by cnt desc
> {code}
> And there are two major problems:
> 1. It produces an incorrect result if it's running in cluster mode.
> 2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
> Spark for the same query
> Steps to reproduce:
> 1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
> {code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
> 2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
> 3. run ignite with attached config.xml 
> 4. run spark-shell
> {code}
> spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
> http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
> /usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
> spark://{spark-master}:7077
> {code}
> 5. load data and execute the query:
> {code}
> import org.apache.ignite._
> import org.apache.ignite.configuration._
> import org.apache.ignite.cache.query._
> import org.apache.ignite.spark._
> import org.apache.ignite.lang.IgniteBiPredicate
> import io.dtk._
> val df = sqlContext.read.json("/Data/*.gz")
> Ignition.setClientMode(true)
> val cacheName = "gitrecords"
> val rdd = df.select("id", "repo.url", 
> "payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
>  => (row.getString(0), new GitRecord(0, 
> row.getString(1),row.getString(2),row.getString(3),row.getString(4
> val cfg = new 
> CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
> val ic = new IgniteContext[String,GitRecord](sc, 
> "/usr/lib/ignite-hadoop/config/config.xml")
> val sharedRDD = ic.fromCache(cfg)
> sharedRDD.savePairs(rdd)
> sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as cnt from 
> (select repo_url, lang from gitrecord where type = 'ForkEvent' and lang is 
> not null group by lang, repo_url) as ForkTable inner join (select repo_url, 
> html_url from gitrecord where type='PullRequestEvent' group by repo_url, 
> html_url) as PullTable on ForkTable.repo_url = PullTable.repo_url group by 
> lang order by cnt desc").show
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4354) DML: BinaryObjectBuilder does not sort fields in some cases

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4354:

Priority: Major  (was: Critical)

> DML: BinaryObjectBuilder does not sort fields in some cases
> ---
>
> Key: IGNITE-4354
> URL: https://issues.apache.org/jira/browse/IGNITE-4354
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>  Labels: DML
> Fix For: 2.0
>
>
> One of the setField methods uses TreeMap<> to sort fields, depending on 
> BinaryUtils.FIELDS_SORTED_ORDER.
> However, there are other places where assignedVals is initialized (setField, 
> removeField) which are not updated to use TreeMap.
> Make sure to put this logic in one place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1577) IlligateStateException when removing index during stop

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763817#comment-15763817
 ] 

Vladimir Ozerov commented on IGNITE-1577:
-

Decreasing priority to {{Major}}. Definitely not critical.

> IlligateStateException when removing index during stop
> --
>
> Key: IGNITE-1577
> URL: https://issues.apache.org/jira/browse/IGNITE-1577
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Dmitriy Setrakyan
>Assignee: Sergi Vladykin
> Fix For: 2.0
>
>
> I ran string example which queries the streamed words onto 2 data nodes (2GB 
> each, started with ExampleNodeStartup class), and while running, killed 1 
> node. I also had 1 StreamWords and 1 QueryWords process.
> Got this error on the stopping node.
> {code}
> java.lang.IllegalStateException: Failed to remove from index (grid is 
> stopping).
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:837)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:433)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.clearIndex(GridCacheMapEntry.java:3553)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:3374)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager$CleanupWorker.body(GridCacheTtlManager.java:136)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3018) Cache affinity calculation is slow with large nodes number

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3018:

Priority: Major  (was: Critical)

> Cache affinity calculation is slow with large nodes number
> --
>
> Key: IGNITE-3018
> URL: https://issues.apache.org/jira/browse/IGNITE-3018
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
> Attachments: 003.png, 064.png, 100.png, 128.png, 200.png, 300.png, 
> 400.png, 500.png, 600.png
>
>
> With large number of cache server nodes (> 200)  RendezvousAffinityFunction 
> and FairAffinityFunction work pretty slow .
> For RendezvousAffinityFunction.assignPartitions can take hundredes of 
> milliseconds, for FairAffinityFunction it can take seconds.
> For RendezvousAffinityFunction most time is spent in MD5 hash calculation and 
> nodes list sorting. As optimization we can try to cache {partion, node} MD5 
> hash or try another hash function. Also several minor optimizations are 
> possible (avoid unncecessary allocations, only one thread local 'get', etc).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1577) IlligateStateException when removing index during stop

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1577:

Priority: Major  (was: Critical)

> IlligateStateException when removing index during stop
> --
>
> Key: IGNITE-1577
> URL: https://issues.apache.org/jira/browse/IGNITE-1577
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Dmitriy Setrakyan
>Assignee: Sergi Vladykin
> Fix For: 2.0
>
>
> I ran string example which queries the streamed words onto 2 data nodes (2GB 
> each, started with ExampleNodeStartup class), and while running, killed 1 
> node. I also had 1 StreamWords and 1 QueryWords process.
> Got this error on the stopping node.
> {code}
> java.lang.IllegalStateException: Failed to remove from index (grid is 
> stopping).
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:837)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:433)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.clearIndex(GridCacheMapEntry.java:3553)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:3374)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager$CleanupWorker.body(GridCacheTtlManager.java:136)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1521) Exception when running sql benchmark on AWS

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1521:

Priority: Major  (was: Critical)

> Exception when running sql benchmark on AWS
> ---
>
> Key: IGNITE-1521
> URL: https://issues.apache.org/jira/browse/IGNITE-1521
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Ilya Suntsov
>
> 1. I fork this repo: https://github.com/apacheignite/yardstick-ignite
> 2. Clone it
> 3. Used the following docs for start SQL benchmarks on AWS:
> https://github.com/yardstick-benchmarks/yardstick-docker
> And got the following exception:
> {noformat}
> ERROR: Shutting down benchmark driver to unexpected exception.
> Type '--help' for usage.
> java.lang.NoSuchMethodError: 
> org.apache.ignite.internal.processors.cache.query.GridCacheTwoStepQuery.(Ljava/util/Set;Ljava/lang/String;[Ljava/lang/Object;)V
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:216)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:859)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:807)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:662)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:660)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:660)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:618)
>   at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:85)
>   at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:61)
>   at 
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1521) Exception when running sql benchmark on AWS

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763814#comment-15763814
 ] 

Vladimir Ozerov commented on IGNITE-1521:
-

Ilya,
Is this problem still relevant?

> Exception when running sql benchmark on AWS
> ---
>
> Key: IGNITE-1521
> URL: https://issues.apache.org/jira/browse/IGNITE-1521
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Ilya Suntsov
>
> 1. I fork this repo: https://github.com/apacheignite/yardstick-ignite
> 2. Clone it
> 3. Used the following docs for start SQL benchmarks on AWS:
> https://github.com/yardstick-benchmarks/yardstick-docker
> And got the following exception:
> {noformat}
> ERROR: Shutting down benchmark driver to unexpected exception.
> Type '--help' for usage.
> java.lang.NoSuchMethodError: 
> org.apache.ignite.internal.processors.cache.query.GridCacheTwoStepQuery.(Ljava/util/Set;Ljava/lang/String;[Ljava/lang/Object;)V
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:216)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:859)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:807)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:662)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:660)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:660)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:618)
>   at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:85)
>   at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:61)
>   at 
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3365) .NET: User-defined affinity mapper

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3365:

Priority: Major  (was: Critical)

> .NET: User-defined affinity mapper
> --
>
> Key: IGNITE-3365
> URL: https://issues.apache.org/jira/browse/IGNITE-3365
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net, roadmap
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2703) .NET: Dynamically registered classes must use binary serialization if possible

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2703:

Priority: Major  (was: Critical)

> .NET: Dynamically registered classes must use binary serialization if possible
> --
>
> Key: IGNITE-2703
> URL: https://issues.apache.org/jira/browse/IGNITE-2703
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: .net, breaking-api, roadmap
> Fix For: 2.0
>
>
> At present we support dynamic class registration in .NET, but they are 
> written using deafult .NET mechanism. This is counterintuitive for users and 
> not consistent with Java, where such classes are written in binary form.
> Proposed implementation plan:
> 1) For each dynamically registered class we must understand whether it could 
> be serialized through binary or not. If not - print a warning and fallback to 
> .NET.
> 2) Before writing a class we must ensure that it's [typeId -> name] pair is 
> known to the cluster. If not - write full class name instead of type ID. Java 
> already do that.
> 3) Last, to support backward compatibility we must be able to fallback to 
> current mode with help of some boolean flag.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3734) .NET: Throw an exception when user tries to run SQL over [Serializable] types

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3734:

Priority: Minor  (was: Major)

> .NET: Throw an exception when user tries to run SQL over [Serializable] types
> -
>
> Key: IGNITE-3734
> URL: https://issues.apache.org/jira/browse/IGNITE-3734
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net
> Fix For: 2.0
>
>
> Unregistered [Serializable] types are written with BinaryFormatter and SQL 
> does not work on them. However, it just silently returns no results, which is 
> confusing to the users. We should clearly indicate the problem somehow.
> See 
> http://apache-ignite-users.70518.x6.nabble.com/No-cache-SQL-queries-possible-with-Default-Serializer-set-to-BinaryReflectiveSerializer-td7262.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3734) .NET: Throw an exception when user tries to run SQL over [Serializable] types

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3734:

Priority: Major  (was: Critical)

> .NET: Throw an exception when user tries to run SQL over [Serializable] types
> -
>
> Key: IGNITE-3734
> URL: https://issues.apache.org/jira/browse/IGNITE-3734
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Unregistered [Serializable] types are written with BinaryFormatter and SQL 
> does not work on them. However, it just silently returns no results, which is 
> confusing to the users. We should clearly indicate the problem somehow.
> See 
> http://apache-ignite-users.70518.x6.nabble.com/No-cache-SQL-queries-possible-with-Default-Serializer-set-to-BinaryReflectiveSerializer-td7262.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4317) Redesign Queries Screen

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov updated IGNITE-4317:
---
Assignee: Pavel Konstantinov  (was: Andrey Novikov)

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Attachments: chart settings.png, scan.png
>
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4317) Redesign Queries Screen

[Andrey Novikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763780#comment-15763780
 ] 

Andrey Novikov commented on IGNITE-4317:


Fixed UI.

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Attachments: chart settings.png, scan.png
>
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4391) Web Console: Implement grouping by company in Admin panel

[Vasiliy Sisko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763740#comment-15763740
 ] 

Vasiliy Sisko commented on IGNITE-4391:
---

# On click by user menu no action (Became, grant admin and remove).

> Web Console: Implement grouping by company in Admin panel
> -
>
> Key: IGNITE-4391
> URL: https://issues.apache.org/jira/browse/IGNITE-4391
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
>
> It will be useful to have different view on same data:
> # list by name (current)
> # group by company
> # group by country



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4372) Set up code coverage reports

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763675#comment-15763675
 ] 

ASF GitHub Bot commented on IGNITE-4372:


GitHub user ksuksu1601 opened a pull request:

https://github.com/apache/ignite/pull/1364

IGNITE-4372: Set up code coverage reports



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ksuksu1601/ignite ignite-4372

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1364.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 #1364


commit b23fd36e3e80e774abc2e556cee453181f3eabbf
Author: ksuksu1601 
Date:   2016-12-19T15:22:51Z

add profile for sonar coverage




> Set up code coverage reports
> 
>
> Key: IGNITE-4372
> URL: https://issues.apache.org/jira/browse/IGNITE-4372
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4424) REPLICATED cache isn't synced across nodes

[Anton Vinogradov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763635#comment-15763635
 ] 

Anton Vinogradov commented on IGNITE-4424:
--

Initially reproduced. Reproducer added to issue.

> REPLICATED cache isn't synced across nodes
> --
>
> Key: IGNITE-4424
> URL: https://issues.apache.org/jira/browse/IGNITE-4424
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.8
>Reporter: Andrew Mashenkov
>Assignee: Anton Vinogradov
>Priority: Blocker
> Fix For: 2.0
>
> Attachments: ReplicatedCacheRebalanceFails.java, 
> ReplicatedCacheRebalanceFails.java, ignite-d8e433e4.log
>
>
> Replicated cache sometimes won't sync across nodes properly.
> PFA a reproducer code.
> All nodes are started at the same time on different machines:
> * Ignition.start() // Blocks until node is up
> * Only one of the nodes performs next: getOrCreateCache() then putAll() 
> * All the other nodes block on this before proceeding. 
> * All of the nodes perform next:
> ** getOrCreateCache() // Again
> ** cache.localSize(CachePeekMode.ALL)
> All nodes should see filled cache, but sometimes some nodes see empty cache. 
> LocalSize call can be replaced by iterating over cache, but result will be 
> same.
> Much more rarely, cluster degradation is possible and one part of cluster see 
> empty cache while another see filled cache. Logs contain no errors at all. It 
> takes about two hours running test in infinite loop to catch this rare error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4391) Web Console: Implement grouping by company in Admin panel

[Dmitriy Shabalin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763632#comment-15763632
 ] 

Dmitriy Shabalin commented on IGNITE-4391:
--

1. fixed
2. fixed
3. fixed
4. need a separate task
5. fixed

Pls check it

> Web Console: Implement grouping by company in Admin panel
> -
>
> Key: IGNITE-4391
> URL: https://issues.apache.org/jira/browse/IGNITE-4391
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Alexey Kuznetsov
>Assignee: Dmitriy Shabalin
> Fix For: 2.0
>
>
> It will be useful to have different view on same data:
> # list by name (current)
> # group by company
> # group by country



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)