[GitHub] ignite pull request #2073: IGNITE-5355 Create task with release tools

GitHub user achetaev opened a pull request: https://github.com/apache/ignite/pull/2073 IGNITE-5355 Create task with release tools You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5355 Alternatively

Re: [DISCUSS] Ignite memory -> virtual memory

Agreed then. Let's update the javadoc and documentation. On Thu, Jun 1, 2017 at 1:33 AM, Alexey Goncharuk wrote: > I am fine with this javadoc change as long as there is no confusion between > Ignite page memory buffers and the OS Virtual Memory concept. > >

Re: Libs with BSD license in dependencies

Dmitriy, Denis, thanks a lot for your answers! 2017-06-02 19:36 GMT+03:00 Denis Magda : > List of all the compatible licenses: > https://www.apache.org/legal/resolved.html#category-a < > https://www.apache.org/legal/resolved.html#category-a> > > > On Jun 2, 2017, at 9:35 AM,

Re: Libs with BSD license in dependencies

List of all the compatible licenses: https://www.apache.org/legal/resolved.html#category-a > On Jun 2, 2017, at 9:35 AM, Dmitriy Setrakyan wrote: > > BSD is an official ASF-friendly license. It is OK to have it in >

Re: Libs with BSD license in dependencies

BSD is an official ASF-friendly license. It is OK to have it in dependencies. https://www.apache.org/legal/resolved.html#criteria D. On Fri, Jun 2, 2017 at 12:12 AM, Vyacheslav Daradur wrote: > And where I can read about this agrement is relative to the Ignite project. >

Re: Persistent Store Stabilization for release

On Fri, Jun 2, 2017 at 6:46 AM, Alexey Goncharuk wrote: > Dmitriy, > > The original idea behind moving persistence to a separate module was > easiness of review and the fact that it is likely that in the future it > will have some external dependencies. I guess we

Re: Summary of SQL changes in 2.1

Sounds good. Can you specify the defaults for the Create Table command? On Fri, Jun 2, 2017 at 6:55 AM, Vladimir Ozerov wrote: > Regarding other comments: > 1) Config - agree, let's have a single flat class "SqlServerConfiguration" > to store listener config. It will be a

Re: contention on DataStructure creation/removing

https://github.com/apache/ignite/pull/2053/files I'm checking TC, now, I'll send it for review as soon as pull request passes TC. On Fri, Jun 2, 2017 at 6:41 PM, Dmitriy Setrakyan wrote: > Wow, what was patched? Can you provide the code sample being benchmarked? > > On

Re: contention on DataStructure creation/removing

Wow, what was patched? Can you provide the code sample being benchmarked? On Fri, Jun 2, 2017 at 8:00 AM, Mikhail Cherkasov wrote: > Looks like dev list doesn't allow to include pictures in emails, so there > are links to plots: > > Throughput plot without any changes:

Re: Expose SqlQueryFields flags as SQL hints

Vova, what custom params are you suggestion? Can you be more specific? How should they look in SQL? On Fri, Jun 2, 2017 at 8:06 AM, Sergi Vladykin wrote: > To be clear I mean not to add some creative stuff under Ignite mode, but > instead add generic hints in H2

[GitHub] ignite pull request #2072: ignite-5097-dotnet-integration

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2072 ignite-5097-dotnet-integration You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5097-dotnet Alternatively you can

[GitHub] ignite pull request #2071: IGNITE-5263: Replaced ODBC connection param "Cach...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2071 IGNITE-5263: Replaced ODBC connection param "Cache" with "Schema" You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2070: Replicated optimizations

GitHub user yzhdanov opened a pull request: https://github.com/apache/ignite/pull/2070 Replicated optimizations https://issues.apache.org/jira/browse/IGNITE-5293 You can merge this pull request into a Git repository by running: $ git pull https://github.com/yzhdanov/ignite

[GitHub] ignite pull request #2068: IGNITE-5255: implement update methods for jdbc st...

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

Re: Expose SqlQueryFields flags as SQL hints

To be clear I mean not to add some creative stuff under Ignite mode, but instead add generic hints in H2 (without Ignite) first, then plug Ignite stuff there so that it will work and look consistently with H2 hints. I'm just trying to avoid situation when we add some our hints under Ignite mode,

Re: contention on DataStructure creation/removing

Looks like dev list doesn't allow to include pictures in emails, so there are links to plots: Throughput plot without any changes: https://www.dropbox.com/s/mc3v5m49u4i2be3/no-changes.png?dl=0 the same plot with patched ignite: https://www.dropbox.com/s/cyojw9nz4smew87/with-chages.png?dl=0

[jira] [Created] (IGNITE-5400) Migrate new SQL configuration to .NET

Vladimir Ozerov created IGNITE-5400: --- Summary: Migrate new SQL configuration to .NET Key: IGNITE-5400 URL: https://issues.apache.org/jira/browse/IGNITE-5400 Project: Ignite Issue Type:

Re: Expose SqlQueryFields flags as SQL hints

This was exactly what I meant. We need native H2 support here. On Fri, Jun 2, 2017 at 5:46 PM, Sergi Vladykin wrote: > IMO the correct way is to implement generic hints for H2 first and plug > Ignite hints there. > > Sergi > > 2017-06-02 17:31 GMT+03:00 Alexey

Re: Expose SqlQueryFields flags as SQL hints

IMO the correct way is to implement generic hints for H2 first and plug Ignite hints there. Sergi 2017-06-02 17:31 GMT+03:00 Alexey Kuznetsov : > Hints discussion on H2 user group: > https://groups.google.com/d/topic/h2-database/dHwbBitzXlY/discussion > > On Fri, Jun 2,

[GitHub] ignite pull request #2069: IGNITE-5393 .NET: Fix NuGet suite build

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2069 --- 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 #2056: IGNITE-5327 PARTITIONED and REPLICATED cache temp...

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

Re: Expose SqlQueryFields flags as SQL hints

Hints discussion on H2 user group: https://groups.google.com/d/topic/h2-database/dHwbBitzXlY/discussion On Fri, Jun 2, 2017 at 9:23 PM, Vladimir Ozerov wrote: > Well, looks like H2 doesn't support hints at the moment, and there is no > way to add some custom params to

Re: Expose SqlQueryFields flags as SQL hints

I'd prefer to avoid inventing any brand new SQL syntax. Sergi 2017-06-02 17:23 GMT+03:00 Vladimir Ozerov : > Well, looks like H2 doesn't support hints at the moment, and there is no > way to add some custom params to SELECT (it is possible for CREATE TABLE > and CREATE

[jira] [Created] (IGNITE-5399) Manual cache rebalancing feature is broken

Andrew Mashenkov created IGNITE-5399: Summary: Manual cache rebalancing feature is broken Key: IGNITE-5399 URL: https://issues.apache.org/jira/browse/IGNITE-5399 Project: Ignite Issue

Re: Expose SqlQueryFields flags as SQL hints

Well, looks like H2 doesn't support hints at the moment, and there is no way to add some custom params to SELECT (it is possible for CREATE TABLE and CREATE SCHEMA) only. Anyway, this could be nice usability improvement for us. On Fri, Jun 2, 2017 at 5:13 PM, Alexey Kuznetsov

[jira] [Created] (IGNITE-5398) Optimize allocations in RendezvousAffinityFunction

Alexey Goncharuk created IGNITE-5398: Summary: Optimize allocations in RendezvousAffinityFunction Key: IGNITE-5398 URL: https://issues.apache.org/jira/browse/IGNITE-5398 Project: Ignite

Re: Expose SqlQueryFields flags as SQL hints

I like this, but could you show some examples? On Fri, Jun 2, 2017 at 9:08 PM, Vladimir Ozerov wrote: > Folks, > > We have quite a few flags on SqlFields and SqlQueryFields classes which are > used for fine tuning. Probably even more flags will appear soon. AFAIK > special

Expose SqlQueryFields flags as SQL hints

Folks, We have quite a few flags on SqlFields and SqlQueryFields classes which are used for fine tuning. Probably even more flags will appear soon. AFAIK special compatibility mode for Apache Ignite was added to H2 parser recently. I think we can expose all these flags as SQL hints in the query

Re: contention on DataStructure creation/removing

Hi all, I prepared a benchmark for ignite reentrant lock, the benchmark updates cache values under the reentrant lock. The benchmark is based on s real case, when user can't use regular cache locks, because they prevent partition map exchange and as result don't allow new nodes join cluster.

Re: Summary of SQL changes in 2.1

Regarding other comments: 1) Config - agree, let's have a single flat class "SqlServerConfiguration" to store listener config. It will be a replacement for OdbcConfiguration. 2) Ok, let's allow users to create indexes on non-SQL caches. This may be convenient in some cases. On Thu, Jun 1, 2017 at

[jira] [Created] (IGNITE-5397) JDBC thin driver: clear server cursor automatically when last result piece is transmitted

Vladimir Ozerov created IGNITE-5397: --- Summary: JDBC thin driver: clear server cursor automatically when last result piece is transmitted Key: IGNITE-5397 URL: https://issues.apache.org/jira/browse/IGNITE-5397

[jira] [Created] (IGNITE-5396) ODBC: Clear server cursor automatically when last result piece is transmitted

Vladimir Ozerov created IGNITE-5396: --- Summary: ODBC: Clear server cursor automatically when last result piece is transmitted Key: IGNITE-5396 URL: https://issues.apache.org/jira/browse/IGNITE-5396

Re: Persistent Store Stabilization for release

Dmitriy, The original idea behind moving persistence to a separate module was easiness of review and the fact that it is likely that in the future it will have some external dependencies. I guess we can have those dependencies as a separate module and move persistence to the core module.

[jira] [Created] (IGNITE-5395) Move ignite-ps module to ignite-core

Alexey Goncharuk created IGNITE-5395: Summary: Move ignite-ps module to ignite-core Key: IGNITE-5395 URL: https://issues.apache.org/jira/browse/IGNITE-5395 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5394) Cache-independent SQL query fails if no tables are present in it

Vladimir Ozerov created IGNITE-5394: --- Summary: Cache-independent SQL query fails if no tables are present in it Key: IGNITE-5394 URL: https://issues.apache.org/jira/browse/IGNITE-5394 Project:

[GitHub] ignite pull request #2064: IGNITE-5355 Create task with release tools

Github user achetaev closed the pull request at: https://github.com/apache/ignite/pull/2064 --- 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 #2069: IGNITE-5393 .NET: Fix NuGet suite build

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2069 IGNITE-5393 .NET: Fix NuGet suite build You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-5393 Alternatively you can

Optimize transaction prepare step when store is enabled IGNITE-1553

Will start working on ticket https://issues.apache.org/jira/browse/IGNITE-1553 if nobody mind -- *Best Regards,* *Kuznetsov Aleksey*

[GitHub] ignite pull request #2068: IGNITE-5255: implement update methods for jdbc st...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2068 IGNITE-5255: implement update methods for jdbc statements You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2054: IGNITE-5328 Added CREATE TABLE params

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2054 --- 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-5393) .NET: NuGet suite fails on TC

Pavel Tupitsyn created IGNITE-5393: -- Summary: .NET: NuGet suite fails on TC Key: IGNITE-5393 URL: https://issues.apache.org/jira/browse/IGNITE-5393 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #2050: IGNITE-5255 JDBC Driver: support DML

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/2050 --- 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

[GitHub] ignite pull request #2055: IGNITE-5305 Correct schema in GridQueryProcessor....

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2055 --- 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 #2067: Ignite 3562 lucene 5.5.2 new

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2067 Ignite 3562 lucene 5.5.2 new latest master You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2066: Ignite 3562 lucene 5.5.2

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2066 Ignite 3562 lucene 5.5.2 old master You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3562-lucene-5.5.2

[GitHub] ignite pull request #2040: IGNITE-5176 JDBC Driver: implement query executio...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2040 --- 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 #2034: IGNITE-5335: Fixed reading decimal binary field

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2034 --- 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 #1916: IGNITE-4509: send unicast sql request when partit...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1916 --- 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 #2065: ignite-5390: Add test for write behind coalescing...

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/2065 ignite-5390: Add test for write behind coalescing=false parameter subj You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1814: IGNITE-4939 Receive event before cache initialize...

Github user ezhuravl closed the pull request at: https://github.com/apache/ignite/pull/1814 --- 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 #2063: IGNITE-5356 .NET: Fix runtime dependency loading ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2063 --- 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 #2048: IGNITE-5358 .NET: Fix nullable enum field handlin...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2048 --- 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-5391) CREATE INDEX and DROP INDEX operations should be allowed back on non-sql caches

Vladimir Ozerov created IGNITE-5391: --- Summary: CREATE INDEX and DROP INDEX operations should be allowed back on non-sql caches Key: IGNITE-5391 URL: https://issues.apache.org/jira/browse/IGNITE-5391

[jira] [Created] (IGNITE-5390) But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest

Alexander Belyak created IGNITE-5390: Summary: But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest Key: IGNITE-5390 URL: https://issues.apache.org/jira/browse/IGNITE-5390 Project: Ignite

Re: Persistent Store Stabilization for release

Also in persistence code I see some TODOs (//TODO GG-), all TODOs should reference some ingite JIRA issue, Thanks! On Fri, Jun 2, 2017 at 11:29 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Semyon, thanks for spotting this. I've removed the fails as tests should be > passing now.

Re: Persistent Store Stabilization for release

Semyon, thanks for spotting this. I've removed the fails as tests should be passing now. 2017-06-02 10:20 GMT+03:00 Semyon Boikov : > Guys, > > I see some tests in PDS suite fail with message > "junit.framework.AssertionFailedError: only for one run, must be removed >

[jira] [Created] (IGNITE-5389) Allow to start sequences in batches.

Alexei Scherbakov created IGNITE-5389: - Summary: Allow to start sequences in batches. Key: IGNITE-5389 URL: https://issues.apache.org/jira/browse/IGNITE-5389 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5388) Web Console: Support to configuration for Ignite 2.x and Ignite 1.x

Andrey Novikov created IGNITE-5388: -- Summary: Web Console: Support to configuration for Ignite 2.x and Ignite 1.x Key: IGNITE-5388 URL: https://issues.apache.org/jira/browse/IGNITE-5388 Project:

Re: Persistent Store Stabilization for release

Guys, I see some tests in PDS suite fail with message "junit.framework.AssertionFailedError: only for one run, must be removed soon". We never add suche messages without reference to JIRA issue, please fix. Thanks! On Thu, Jun 1, 2017 at 7:22 PM, Alexey Goncharuk

Re: Libs with BSD license in dependencies

And where I can read about this agrement is relative to the Ignite project. 2017-06-02 10:10 GMT+03:00 Vyacheslav Daradur : > Hi Igniters! > > I want to know: Is it legal to use libs in dependincies of the project > with license BSD-2-Clause and BSD-3-Clause? > > For

Libs with BSD license in dependencies

Hi Igniters! I want to know: Is it legal to use libs in dependincies of the project with license BSD-2-Clause and BSD-3-Clause? For examples: https://github.com/facebook/zstd/blob/dev/LICENSE https://github.com/luben/zstd-jni/blob/master/LICENSE -- Best Regards, Vyacheslav