[jira] [Created] (IGNITE-3625) IGFS: Use common naming for IGFS meta and data caches.

Vladimir Ozerov created IGNITE-3625: --- Summary: IGFS: Use common naming for IGFS meta and data caches. Key: IGNITE-3625 URL: https://issues.apache.org/jira/browse/IGNITE-3625 Project: Ignite

Re: [VOTE] Apache Ignite 1.7.0 RC1

+1 -- Andrey On Thu, Aug 4, 2016 at 2:38 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > +1 (binding) > > -Val > > On Wed, Aug 3, 2016 at 12:32 PM, Denis Magda wrote: > > > +1 (binding) > > > > -- > > Denis > > > > > On Aug 3, 2016, at 11:52 AM, Sergi

Re: IGNITE-2294 implementation details

About arguments number. I see following options here: 1. Somehow use H2 engine to parse SQL string and check results. 2. Use some other parsing library instead of H2 but this will bring one more dependency to Ignite. 3. Write some simple parser by ourselves .

Re: IGNITE-2294 implementation details

Alex, See my comments below. -Val On Wed, Aug 3, 2016 at 5:47 AM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Guys, > > I have few questions about current state of the art regarding JDBC driver. > > First: in JdbcPreparedStatement, we determine number of arguments > simply

Re: Ignite 1.7 RELEASE_NOTES

On Wed, Aug 03, 2016 at 10:47AM, Pavel Tupitsyn wrote: > Cos, we track versions in JIRA. There are 230 closed issues for 1.7: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed > We can't just dump all of them to release

Re: [VOTE] Apache Ignite 1.7.0 RC1

+1 (binding) -Val On Wed, Aug 3, 2016 at 12:32 PM, Denis Magda wrote: > +1 (binding) > > -- > Denis > > > On Aug 3, 2016, at 11:52 AM, Sergi Vladykin > wrote: > > > > +1 binding > > > > Sergi > > > > 2016-08-03 15:04 GMT+03:00 Nikolai Tikhonov

Re: [VOTE] Apache Ignite 1.7.0 RC1

+1 (binding) -- Denis > On Aug 3, 2016, at 11:52 AM, Sergi Vladykin wrote: > > +1 binding > > Sergi > > 2016-08-03 15:04 GMT+03:00 Nikolai Tikhonov : > >> +1 (binding) >> >> On Wed, Aug 3, 2016 at 1:25 PM, Vladimir Ozerov

Re: [VOTE] Apache Ignite 1.7.0 RC1

+1 binding Sergi 2016-08-03 15:04 GMT+03:00 Nikolai Tikhonov : > +1 (binding) > > On Wed, Aug 3, 2016 at 1:25 PM, Vladimir Ozerov > wrote: > > > +1 (binding) > > > > Looks good to me. > > > > On Wed, Aug 3, 2016 at 10:48 AM, Alexey Kuznetsov < >

[jira] [Created] (IGNITE-3624) Provide API to get the size of the cache in bytes

Valentin Kulichenko created IGNITE-3624: --- Summary: Provide API to get the size of the cache in bytes Key: IGNITE-3624 URL: https://issues.apache.org/jira/browse/IGNITE-3624 Project: Ignite

Re: IGNITE-2294 implementation details

Folks, OK, I have one thing to clarify about Statement.getResultSet: its javadoc says that it "should be called only once per result", so setting field to null every one and then is starting to make sense. However, this "should" word does not tell us what we have to do if the method gets called

[GitHub] ignite pull request #922: Ignite 2649

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

[GitHub] ignite pull request #921: IGNITE-3331 IGFS: Route client tasks to primary no...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/921 IGNITE-3331 IGFS: Route client tasks to primary node when metadata co… …-location is enabled. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #920: ignite-3597: Fixed.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/920 ignite-3597: Fixed. U.setWorkDirectory method rewrites old work dir value. You can merge this pull request into a Git repository by running: $ git pull https://github.com/AMashenkov/ignite

[jira] [Created] (IGNITE-3623) Drivers hung during streaming load test

Ksenia Rybakova created IGNITE-3623: --- Summary: Drivers hung during streaming load test Key: IGNITE-3623 URL: https://issues.apache.org/jira/browse/IGNITE-3623 Project: Ignite Issue Type:

Re: IGNITE-2294 implementation details

Guys, I have few questions about current state of the art regarding JDBC driver. First: in JdbcPreparedStatement, we determine number of arguments simply by counting question mark symbols. What if query string contains a string literal with question mark in it? It seems like a bug to me.

Re: [VOTE] Apache Ignite 1.7.0 RC1

+1 (binding) On Wed, Aug 3, 2016 at 1:25 PM, Vladimir Ozerov wrote: > +1 (binding) > > Looks good to me. > > On Wed, Aug 3, 2016 at 10:48 AM, Alexey Kuznetsov > > wrote: > > > I managed to check sha1 and md5 checksums under Windows. > > > >

[GitHub] ignite pull request #919: IGNITE-2310 Lock cache partition for affinityRun/a...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/919 IGNITE-2310 Lock cache partition for affinityRun/affinityCall execution You can merge this pull request into a Git repository by running: $ git pull

Re: IGNITE-3621 Implementation details

I hardly can imagine use case hundreds of caches with expiry policies. Even if someone really need it, what is the real performance impact? Considering some mid-level server with 64 cores we already have ~4 nio threads and ~64 system pool threads processing cache operations. All these threads

[jira] [Created] (IGNITE-3622) BinaryObject: print idHash in toString() method only in debug mode

Alexey Kuznetsov created IGNITE-3622: Summary: BinaryObject: print idHash in toString() method only in debug mode Key: IGNITE-3622 URL: https://issues.apache.org/jira/browse/IGNITE-3622 Project:

IGNITE-3621 Implementation details

Now every cache has own TTL manager, which creates CleanupWorker = new extra thread. This can cause to extra hundreds of threads (redundant context switches = performance penalty). Also, under IGNITE-3513 every put can enter critical section to

[jira] [Created] (IGNITE-3621) Make GridCacheTtlManager singleto

Eduard Shangareev created IGNITE-3621: - Summary: Make GridCacheTtlManager singleto Key: IGNITE-3621 URL: https://issues.apache.org/jira/browse/IGNITE-3621 Project: Ignite Issue Type: Bug

Re: [VOTE] Apache Ignite 1.7.0 RC1

+1 (binding) Looks good to me. On Wed, Aug 3, 2016 at 10:48 AM, Alexey Kuznetsov wrote: > I managed to check sha1 and md5 checksums under Windows. > > C:\Program Files\Git\usr\bin>sha1sum -c *.sha1 > apache-ignite-1.7.0-src.zip: OK > > C:\Program

[jira] [Created] (IGNITE-3620) Hide error popover on section collapse.

Vasiliy Sisko created IGNITE-3620: - Summary: Hide error popover on section collapse. Key: IGNITE-3620 URL: https://issues.apache.org/jira/browse/IGNITE-3620 Project: Ignite Issue Type:

[GitHub] ignite pull request #918: IGNITE-3359 .NET: Implement IgniteConfiguration.To...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/918 IGNITE-3359 .NET: Implement IgniteConfiguration.ToXml/FromXml You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3359

[GitHub] ignite pull request #910: Ignite 2310

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/912 --- 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 #914: ignite-1.6.4

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/914 --- 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 #896: Ignite 1.6.3 3343

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/896 --- 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: [VOTE] Apache Ignite 1.7.0 RC1

I managed to check sha1 and md5 checksums under Windows. C:\Program Files\Git\usr\bin>sha1sum -c *.sha1 apache-ignite-1.7.0-src.zip: OK C:\Program Files\Git\usr\bin>md5sum -c *.md5 apache-ignite-1.7.0-src.zip: OK On Wed, Aug 3, 2016 at 10:39 AM, Alexey Kuznetsov

[GitHub] ignite pull request #849: IGNITE-1802

Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/849 --- 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 #798: Ignite 3226

Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/798 --- 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 #825: Gridgain 7.5.27 yardstick

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