[GitHub] ignite pull request #2494: ignite-5714-2

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2494 ignite-5714-2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5714-2 Alternatively you can review and apply these changes

Re: SQL Getting Started Guide

Prachi, is there an example for a template file? Is there an example of how a template should be registered? Is there an example of how other extended parameters should be configured, i.e. a sample CREATE TABLE command? On Mon, Aug 21, 2017 at 5:15 PM, Prachi Garg wrote: >

[GitHub] ignite pull request #2493: ignite-5714-1

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2493 ignite-5714-1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5714-1 Alternatively you can review and apply these changes

Re: Ignite: configuration changes at runtime

On Mon, Aug 21, 2017 at 7:28 AM, Alexey Dmitriev wrote: > I believe it should be persistent. > We can have a parameter about "reset configuration on restart", which can > be also OLCC-compatible > Alexey, the problem with persisting at all times is that some properties

Re: Scan Queries: rows, updates and binary builders

On Mon, Aug 21, 2017 at 9:01 AM, Yakov Zhdanov wrote: > Guys, > > I was asked how effectively change many rows in cache many times. > Currently, this can done via ScanQuery - we send affinityCall(), inside > callable we iterate over local primary cache partitions, filter

[jira] [Created] (IGNITE-6135) java.sql.Date is serialized using OptimizedMarshaller

Valentin Kulichenko created IGNITE-6135: --- Summary: java.sql.Date is serialized using OptimizedMarshaller Key: IGNITE-6135 URL: https://issues.apache.org/jira/browse/IGNITE-6135 Project: Ignite

[GitHub] ignite pull request #2495: ignite-5714-3

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2495 ignite-5714-3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5714-3 Alternatively you can review and apply these changes

Re: Shell script to stop Ignite node

Denis, I generally agree that Visor CLI should be more lightweight (connect using thin client instead of starting client node) and have all this functionality as well. However, having a simple way to stop the node is very natural. It's a bit confusing to our users that there is a script to start

Re: SQL Getting Started Guide

Nikita, Thanks for checking. No, this is not on purpose. Denis, do we have the template syntax documented anywhere? D. On Mon, Aug 21, 2017 at 9:42 AM, Nikita Ivanov wrote: > I looked briefly and I couldn't find any explanation on "template" at all - > the only unique

Re: SQL Getting Started Guide

Thanks, Prachi! Looks complete, not sure how I missed it the first time. On Mon, Aug 21, 2017 at 5:52 PM, Prachi Garg wrote: > https://apacheignite.readme.io/docs/distributed-ddl#section-create-table > has examples for template and other extended parameters. The Extended >

Expanding Apache Ignite Use Case

Igniters, I’ve been working on this ticket that aims to add more use cases we have: https://issues.apache.org/jira/browse/IGNITE-6036 Presently these pages are ready: SQL database page: http://localhost/use-cases/database/sql-database.html

Re: SQL Getting Started Guide

https://apacheignite.readme.io/docs/distributed-ddl#section-create-table has examples for template and other extended parameters. The Extended Parameters section explains how to register a template. On Mon, Aug 21, 2017 at 5:19 PM, Dmitriy Setrakyan wrote: > Prachi, is there

Re: Ignite: configuration changes at runtime

Guys, Why not to let user to decide whether to persist changed properties or not? We could have a Boolean flag on API "persist=true|false". Make sense? On Tue, Aug 22, 2017 at 6:52 AM, Dmitriy Setrakyan wrote: > On Mon, Aug 21, 2017 at 7:28 AM, Alexey Dmitriev

[jira] [Created] (IGNITE-6136) Web Console: implement version check

Alexey Kuznetsov created IGNITE-6136: Summary: Web Console: implement version check Key: IGNITE-6136 URL: https://issues.apache.org/jira/browse/IGNITE-6136 Project: Ignite Issue Type:

Re: Ignite: configuration changes at runtime

On Mon, Aug 21, 2017 at 6:20 PM, Alexey Kuznetsov wrote: > Guys, > > Why not to let user to decide whether to persist changed properties or not? > We could have a Boolean flag on API "persist=true|false". > > Make sense? > Not really. What if the user configured Ignite

Re: Expanding Apache Ignite Use Case

Denis, great progress. At a first glance, I would suggest to move the page "What is Collocated Processing" to Features and add some coding examples there. Also, I am not sure if I agree with "Featured Solutions" page. D. P.S. don't forget to update sitemap.xml file. On Mon, Aug 21, 2017 at

IGNITE-4172 - ready for review

Hi, I've prepared a PR for https://issues.apache.org/jira/browse/IGNITE-4172 Looks like CI doesn't have problems related to the change. Please take a look at https://reviews.ignite.apache.org/ignite/review/IGNT-CR-286 Kind regards, Alex.

Re: IGNITE-4172 - ready for review

CI build https://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_RunAll=776189_Ignite20Tests_RunAll=pull/2438/head Kind regards, Alex. On Mon, Aug 21, 2017 at 2:24 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Hi, > > I've prepared a PR for

Re: SQL usability issues

Hi, Denis, please rename '|IgniteThinJdbcDriver| ' -> 'IgniteJdbcThinDriver' an the Installation and Configuration section (see [1]). [1] https://apacheignite.readme.io/docs/sql-tooling#installation-and-configuration On 18.08.2017 0:22, Denis Magda wrote: No I see what you tried to

[jira] [Created] (IGNITE-6128) Binary: offsets might be skipped for constant-length fields

Vladimir Ozerov created IGNITE-6128: --- Summary: Binary: offsets might be skipped for constant-length fields Key: IGNITE-6128 URL: https://issues.apache.org/jira/browse/IGNITE-6128 Project: Ignite

Yardstick framework for Ignite 2.1

I am handling with yardstick benchmark framework for Ignite[1], but the latest version available for 1.9. In versions 2.0-2.1 were made many back incompatible changes. Is there any newer version that is working with Ignite 2.1 not to do a double job? [1]

[jira] [Created] (IGNITE-6129) Implement date types comparison without deserialization

Vladimir Ozerov created IGNITE-6129: --- Summary: Implement date types comparison without deserialization Key: IGNITE-6129 URL: https://issues.apache.org/jira/browse/IGNITE-6129 Project: Ignite

[jira] [Created] (IGNITE-6119) ODBC: Propagate "lazy" flag

Vladimir Ozerov created IGNITE-6119: --- Summary: ODBC: Propagate "lazy" flag Key: IGNITE-6119 URL: https://issues.apache.org/jira/browse/IGNITE-6119 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2490: IGNITE-1094 Ignite.createCache(CacheConfiguration...

GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/2490 IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization The following algorithm was implemented in order to fix hangs during dynamic start of

[jira] [Created] (IGNITE-6120) Web Console: Propagate "lazy" flag on Query screen

Alexey Kuznetsov created IGNITE-6120: Summary: Web Console: Propagate "lazy" flag on Query screen Key: IGNITE-6120 URL: https://issues.apache.org/jira/browse/IGNITE-6120 Project: Ignite

[jira] [Created] (IGNITE-6124) Try merge multiple exchanges into one

Semen Boikov created IGNITE-6124: Summary: Try merge multiple exchanges into one Key: IGNITE-6124 URL: https://issues.apache.org/jira/browse/IGNITE-6124 Project: Ignite Issue Type:

Re: Yardstick framework for Ignite 2.1

Hello, Yes, this repository contains benchmarks for old Apache Ignite and yardstick version. The last versions Apache Ignite distributed with benchmarks. You can download there https://ignite.apache.org/download.cgi#binaries and found them and instruction in /benchmarks folder. On Mon, Aug 21,

[GitHub] ignite pull request #149: ignite-1666 Fallback for full scan query does not ...

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

[GitHub] ignite pull request #2473: ignite-5714-1

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

[jira] [Created] (IGNITE-6123) First performance measurement of implemented ml algorithms

Yury Babak created IGNITE-6123: -- Summary: First performance measurement of implemented ml algorithms Key: IGNITE-6123 URL: https://issues.apache.org/jira/browse/IGNITE-6123 Project: Ignite

[GitHub] ignite pull request #2474: ignite-5714-2

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

[GitHub] ignite pull request #1971: Ignite 5203

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

[GitHub] ignite pull request #1960: Ignite 4763 review

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

[GitHub] ignite pull request #1984: ignite-5203 Simple BLOB support added

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

[GitHub] ignite pull request #2449: fair-aff-fix

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

[GitHub] ignite pull request #2461: gg-12637 Fixed unevenly partitions distribution i...

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

[jira] [Created] (IGNITE-6125) A range of improvements for JDBC driver metadata queries

Ilya Kasnacheev created IGNITE-6125: --- Summary: A range of improvements for JDBC driver metadata queries Key: IGNITE-6125 URL: https://issues.apache.org/jira/browse/IGNITE-6125 Project: Ignite

Re: SQL Getting Started Guide

Prachi, Yeah, looks good. I've added creation of "Person" table to documentation, so take a look please. Best Regards, Igor On Fri, Aug 18, 2017 at 10:29 PM, Prachi Garg wrote: > Hi Igor, > > The getting started guide is missing an example oh how to create a Person > table

[GitHub] ignite pull request #2001: ignite-5283 Transaction recovery works incorrectl...

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

[GitHub] ignite pull request #2176: ignite-5574 For offheap_tiered cache first try re...

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

[jira] [Created] (IGNITE-6117) JDBC2: Propagate "lazy" flag

Vladimir Ozerov created IGNITE-6117: --- Summary: JDBC2: Propagate "lazy" flag Key: IGNITE-6117 URL: https://issues.apache.org/jira/browse/IGNITE-6117 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6118) JDBC Thin: Propagate "lazy" flag

Vladimir Ozerov created IGNITE-6118: --- Summary: JDBC Thin: Propagate "lazy" flag Key: IGNITE-6118 URL: https://issues.apache.org/jira/browse/IGNITE-6118 Project: Ignite Issue Type: Task

Re: Multi-Version Concurrency Control

There are some updates and clarifications for the approach. About Multi/Single Node Operations To improve performance for single-partition operations it's possible to separate single-partitions and multi-partitions transactions. A single-partition operation sends a put/get directly to the

[jira] [Created] (IGNITE-6126) Compilation error (yardstick repo)

Ilya Suntsov created IGNITE-6126: Summary: Compilation error (yardstick repo) Key: IGNITE-6126 URL: https://issues.apache.org/jira/browse/IGNITE-6126 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #2492: Ignite 1.7.4 p4

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

[jira] [Created] (IGNITE-6134) Need to check node local map on class loader undeploy

Yakov Zhdanov created IGNITE-6134: - Summary: Need to check node local map on class loader undeploy Key: IGNITE-6134 URL: https://issues.apache.org/jira/browse/IGNITE-6134 Project: Ignite

Scan Queries: rows, updates and binary builders

Guys, I was asked how effectively change many rows in cache many times. Currently, this can done via ScanQuery - we send affinityCall(), inside callable we iterate over local primary cache partitions, filter entries by predicate and then do cache puts for rows that are wanted to change. I want

[jira] [Created] (IGNITE-6122) CPP: Propagate SqlFieldsQuery.lazy property

Vladimir Ozerov created IGNITE-6122: --- Summary: CPP: Propagate SqlFieldsQuery.lazy property Key: IGNITE-6122 URL: https://issues.apache.org/jira/browse/IGNITE-6122 Project: Ignite Issue

[jira] [Created] (IGNITE-6121) .NET: Propagate SqlFieldsQuery.lazy property

Vladimir Ozerov created IGNITE-6121: --- Summary: .NET: Propagate SqlFieldsQuery.lazy property Key: IGNITE-6121 URL: https://issues.apache.org/jira/browse/IGNITE-6121 Project: Ignite Issue

[GitHub] ignite pull request #2491: IGNITE-6118 JDBC Thin: Propagate "lazy" flag

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2491 IGNITE-6118 JDBC Thin: Propagate "lazy" flag You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6118

[jira] [Created] (IGNITE-6132) Need to add criteria query to web console

Yakov Zhdanov created IGNITE-6132: - Summary: Need to add criteria query to web console Key: IGNITE-6132 URL: https://issues.apache.org/jira/browse/IGNITE-6132 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-6133) Add clearNodeLocalMap() to IgniteMXBean

Yakov Zhdanov created IGNITE-6133: - Summary: Add clearNodeLocalMap() to IgniteMXBean Key: IGNITE-6133 URL: https://issues.apache.org/jira/browse/IGNITE-6133 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-6130) JDBC Thin: getTypes returns invalid result set

Taras Ledkov created IGNITE-6130: Summary: JDBC Thin: getTypes returns invalid result set Key: IGNITE-6130 URL: https://issues.apache.org/jira/browse/IGNITE-6130 Project: Ignite Issue Type:

Re: Ignite: configuration changes at runtime

I think the main question I have is whether this configuration change will survive restarts. Part of me says it should, and the other part says it shouldn't. Does anyone have a strong opinion about this? D. On Mon, Aug 21, 2017 at 7:07 AM, Alexey Dmitriev wrote: > It

Re: Yardstick framework for Ignite 2.1

Igniters, We should either update this repository or delete it. Why have a repository with outdated benchmarks. Thoughts? D. On Mon, Aug 21, 2017 at 7:14 AM, Aleksei Zaitsev wrote: > Thanks, looks like that's what I need. > > 21.08.2017, 12:17, "Nikolai Tikhonov"

Re: Ignite: configuration changes at runtime

On Mon, Aug 21, 2017 at 7:15 AM, Alexey Dmitriev wrote: > I would say it should as soon as we moving to "persistence". > It will require to look at the things a bit different than before, but I > would say that's an evolution for the product. > We probably also should

Re: Ignite: configuration changes at runtime

I would vote for not automatically persisting runtime configuration changes. Still it makes sense to expose a "save(fileName)" method to allow explicitly saving changes to a different or same config file. On Mon, Aug 21, 2017 at 5:22 PM, Dmitriy Setrakyan wrote: > On Mon,

Re: Ignite: configuration changes at runtime

On Mon, Aug 21, 2017 at 7:25 AM, Alexey Kukushkin wrote: > I would vote for not automatically persisting runtime configuration > changes. Still it makes sense to expose a "save(fileName)" method to allow > explicitly saving changes to a different or same config file.

Re: Ignite: configuration changes at runtime

It looks like very useful and natural thing having the parameters change on the fly. Maybe we should design something like OLCC (on-line configuration change) module, which will request different procedures for different bunch of parameters. All the parameters, this way, will be splitted into

Re: Ignite: configuration changes at runtime

>I see your point. In this case, we should have a special package containing >all the runtime config properties. Dmitry, I think this will be a mess. Igniters, any more opinions? --Yakov

Re: Yardstick framework for Ignite 2.1

Thanks, looks like that's what I need. 21.08.2017, 12:17, "Nikolai Tikhonov" : > Hello, > > Yes, this repository contains benchmarks for old Apache Ignite and > yardstick version. The last versions Apache Ignite distributed with > benchmarks. You can download there >

Re: Ignite: configuration changes at runtime

I would say it should as soon as we moving to "persistence". It will require to look at the things a bit different than before, but I would say that's an evolution for the product. We probably also should think how our configuration system should be changed to make it more obvious. On Mon, Aug

Re: Ignite: configuration changes at runtime

I believe it should be persistent. We can have a parameter about "reset configuration on restart", which can be also OLCC-compatible On Mon, Aug 21, 2017 at 5:22 PM, Dmitriy Setrakyan wrote: > On Mon, Aug 21, 2017 at 7:15 AM, Alexey Dmitriev >

[jira] [Created] (IGNITE-6131) In Visor "cache on nodes" statistics doubles off-heap entries

Ilya Kasnacheev created IGNITE-6131: --- Summary: In Visor "cache on nodes" statistics doubles off-heap entries Key: IGNITE-6131 URL: https://issues.apache.org/jira/browse/IGNITE-6131 Project: Ignite

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

Hello, Igniters. I am developing Externalizable interface support by BinaryMarshaller through new type constant. BinaryMarshaller allows using BinarySerializer to manage serialization. I need to define BinaryWriteMode in the BinaryClassDescriptor constructor. In case of the Binarylizable

Shell script to stop Ignite node

Guys, Currently to stop node on a particular server (not using visor or web console) I need to run "jps" and then "kill" with a pid. What if we create ignite-stop.sh which will display the list of started nodes on local host and allow user to choose one to stop. Also it should support --all

Re: SQL Getting Started Guide

Igor, Pavel On the website[1], I have added SQL, JDBC, ODBC, and Java API examples for DDL, DML and queries . I could not find DDL examples for .NET and C++ in the documentation. Please add the missing code snippets for .NET and C++ APIs taking SQL syntax from the Java API example. [1]

Re: SQL Getting Started Guide

I looked briefly and I couldn't find any explanation on "template" at all - the only unique caveat apart from standard SQL. Is this on purpose? -- Nikita Ivanov On Mon, Aug 21, 2017 at 9:36 AM, Prachi Garg wrote: > Igor, Pavel > > On the website[1], I have added SQL, JDBC,

Re: SQL usability issues

Thanks Taras, fixed the doc. Not sure how it worked before with the wrong name. — Denis > On Aug 21, 2017, at 5:05 AM, Taras Ledkov wrote: > > Hi, > > Denis, please rename '|IgniteThinJdbcDriver| ' -> 'IgniteJdbcThinDriver' an > the Installation and Configuration

Re: Shell script to stop Ignite node

+1 On Mon, Aug 21, 2017 at 11:44 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > +1 > > -Val > > On Mon, Aug 21, 2017 at 9:06 AM, Yakov Zhdanov > wrote: > > > Guys, > > > > Currently to stop node on a particular server (not using visor or web > > console)

Re: Shell script to stop Ignite node

Igniters, I would propose to make this a feature of Visor CLI. Recently we’ve added the script to control a cluster activation [1] explaining that Visor CLI is not flexible for that. If we keep moving this way at some point there will be the whole zoo of scripts. Why don’t we improve Visor

Re: Policy for update third-party dependencies

Hi Nick, Do you suggest to build and deploy uber-jars that has no external dependencies? -Val On Sun, Aug 20, 2017 at 1:02 PM, Nick Pordash wrote: > If the dependency is not exposed by the public API then another alternative > is to simply shade the artifact and then

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

Nikita, I think anything binary related should have higher priority than Externalizable. I.e. if user explicitly implemented Binarylizable or provided a BinarySerializer, then BinaryMarshaller should of course use that and ignore Externalizable. -Val On Mon, Aug 21, 2017 at 9:29 AM, Nikita

Re: Shell script to stop Ignite node

+1 -Val On Mon, Aug 21, 2017 at 9:06 AM, Yakov Zhdanov wrote: > Guys, > > Currently to stop node on a particular server (not using visor or web > console) I need to run "jps" and then "kill" with a pid. > > What if we create ignite-stop.sh which will display the list of