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

2016-08-03 Thread Vladimir Ozerov (JIRA) 
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
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Assignee: Taras Ledkov
 Fix For: 1.8


Currently IGFS is configured by passing names of two caches: meta and data. See 
{{FileSystemConfiguration.metaCacheName}} and 
{{FileSystemConfiguration.dataCacheName}}.

These two caches are considered internal then and are not accessible for the 
user.

We need to do the following during node startup:

1) If certain cache is configured as meta or data cache for multiple IGFS-es, 
or if it is configured as both meta and data cache for a single IGFS, then 
throw an exception.
Relevant code pieces:
{{IgfsProcessor.validateLocalIgfsConfigurations}}
{{IgfsProcessorSelfTest}}.

2) During node startup change the name of this cache to 
{{igfs-[IGFS_NAME]-meta}} or {{igfs-[IGFS_NAME]-data}}. Change must be 
performed both inside IGFS config and cache config.
Relevant code pieces:
{{CacheConfiguration.name}}
{{FileSystemConfiguration.metaCacheName}}
{{FileSystemConfiguration.dataCacheName}}
{{IgfsUtils.prepareCacheConfiguration}} - where change will be done.

3) If any of new names clashes with any other cache name, an exception should 
be thrown. The most simple way: throw an exception if user-configured cache 
name starts with "{{gfs-}} and ends with {{-meta}} or {{-data}}.
Relevant code pieces:
{{IgniteNamedInstance.initializeDefaultCacheConfiguration}}.



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

Re: [VOTE] Apache Ignite 1.7.0 RC1

2016-08-03 Thread Andrey Novikov 
+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 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  >
> > >> wrote:
> > >>
> > >>> +1 (binding)
> > >>>
> > >>> Looks good to me.
> > >>>
> > >>> On Wed, Aug 3, 2016 at 10:48 AM, Alexey Kuznetsov <
> > >> akuznet...@gridgain.com
> > 
> > >>> 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 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 <
> > >>> akuznet...@gridgain.com
> > >
> >  wrote:
> > 
> > > +1
> > >
> > > Downloaded
> > >
> > 
> > >>>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/apache-ignite-1.7.0-src.zip
> > > - OK
> > > mvn validate -DskipTests -Pcheck-licenses  - OK
> > > mvn clean package -DskipTests - OK
> > > Unpacked ..\src\target\bin\apache-ignite-fabric-1.7.0-bin.zip  - OK
> > > Started several niodes with ignite.bat - OK
> > > Started with ignite-schema-import.bat - OK
> > >
> > >
> > > On Tue, Aug 2, 2016 at 10:51 PM, Pavel Tupitsyn <
> > >> ptupit...@apache.org>
> > > wrote:
> > >
> > >> Hello,
> > >>
> > >> We have uploaded the 1.7.0 release candidate to
> > >> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/
> > >>
> > >> Tag name is
> > >> 1.7.0-rc1
> > >>
> > >> This release includes the following changes:
> > >>
> > >> Ignite:
> > >> * Added distributed SQL JOIN.
> > >> * Node can be assigned as primary only after preloading is
> finished.
> > >> * Fixed CountDownLatch re-create issue.
> > >> * ODBC: Added decimal type support.
> > >> * Visor: Fixed data nodes calculation when node filter is set for
> > >>> cache.
> > >> * Many stability and fault-tolerance fixes.
> > >>
> > >> Ignite.NET:
> > >> * Added ASP.NET Output Cache provider.
> > >> * Added ability to use .NET configuration in Apache.Ignite.exe.
> > >> * Added ability to implement custom affinity functions.
> > >> * Fixed a bug in IBinaryObjectBuilder causing type name to be
> lost.
> > >>
> > >> Ignite CPP:
> > >> * Marshalling performance improvements.
> > >>
> > >>
> > >> Complete list of closed issues:
> > >>
> > 
> > >>
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > >> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
> > >>
> > >> DEVNOTES
> > >>
> > >>
> > 
> > >>>
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/
> > >> 1.7.0-rc1
> > >>
> > >> RELEASENOTES
> > >>
> > >>
> > 
> > >>>
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/
> > >> 1.7.0-rc1
> > >>
> > >> Please start voting.
> > >>
> > >> +1 - to accept Apache Ignite 1.7.0-rc1
> > >> 0 - don't care either way
> > >> -1 - DO NOT accept Apache Ignite 1.7.0-rc1 (explain why)
> > >>
> > >> This vote will go for 72 hours.
> > >>
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> > 
> > 
> > 
> >  --
> >  Alexey Kuznetsov
> >  GridGain Systems
> >  www.gridgain.com
> > 
> > >>>
> > >>
> >
> >
>

Re: IGNITE-2294 implementation details

2016-08-03 Thread Alexey Kuznetsov 
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

2016-08-03 Thread Valentin Kulichenko 
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 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.
>

Agree that it looks like a bug, but I'm not sure how we can fix it. Do you
have any ideas?


>
> Second: in JdbcStatement.executeQuery we null 'rs' field, but don't
> set it with the new result set. It gets set only by 'execute' method,
> by result of 'executeQuery' call. However, in javadoc of Statement
> interface there's nothing regarding its 'getResultSet' returning last
> result only on 'execute' call. In other words, it seems to me that
> calling 'getResultSet' after 'executeQuery' will always return null,
> which I doubt is right. Moreover, we null 'rs' field prior to doing
> anything, and I question its correctness (or would like to understand
> reasons behind such design) as well. H2's JdbcStatement overwrites
> previous result only when new one is available - it directly sets new
> result without making field null prior to that. We probably should
> store last result until the new one is actually available, what do you
> think?
>

I don't think anyone will ever use getResultSet() method, because it's
mainly used for multiple results which we do not support. So I would just
do this in the same way as other major drivers do (unless this violates the
spec, of course).


>
> - Alex
>
> 2016-08-03 3:15 GMT+03:00 Dmitriy Setrakyan :
> > On Tue, Aug 2, 2016 at 2:21 PM, Alexander Paschenko <
> > alexander.a.pasche...@gmail.com> wrote:
> >
> >> Dmitriy,
> >>
> >> Sorry, link access fixed, please check now.
> >> Will sum up current status on issue page, meanwhile links to both docs
> are
> >> there.
> >>
> >
> > Thanks! I have comments, but I will wait till your list the proposed
> > changes in the Jira, so I can comment there.
> >
> >
> >>
> >> — Alex
> >> 2 авг. 2016 г. 10:51 PM пользователь "Dmitriy Setrakyan" <
> >> dsetrak...@apache.org> написал:
> >>
> >> > Alex,
> >> >
> >> > Can you please also make me happy and put all your design into the
> ticket
> >> > instead of sending it around in emails?
> >> >
> >> > On top of that, the link you provided is protected. I cannot access
> it.
> >> >
> >> > D.
> >> >
> >> > On Tue, Aug 2, 2016 at 8:24 AM, Alexander Paschenko <
> >> > alexander.a.pasche...@gmail.com> wrote:
> >> >
> >> > > I have pushed "zero" version of JDBC updates support, currently
> >> > > without batching (working on it).
> >> > > Sergi, also to make you happy here's another doc with changes to
> >> > > public API: http://goo.gl/FvGKUs
> >> > >
> >> > > - Alex
> >> > >
> >> > > 2016-08-01 20:06 GMT+03:00 Sergi Vladykin  >:
> >> > > > Ok, I think you don't really understand what public API really
> is, so
> >> > let
> >> > > > me clarify. What you have described are all internal classes,
> public
> >> > API
> >> > > is
> >> > > > what end user will see and work with, like Ignite, IgniteCache,
> >> > > > QueryCursor, etc... All the internal changes do not require any
> >> special
> >> > > > discussion, until they are really complex or big or important, so
> you
> >> > > think
> >> > > > it makes sense to notify everyone about them.
> >> > > >
> >> > > > Here we should not have any public API changes for now and I don't
> >> see
> >> > > any
> >> > > > in your doc, so it looks fine to me.
> >> > > >
> >> > > > The only possible issue I see is origKeyClass and origValueClass.
> >> These
> >> > > > classes can be unavailable on nodes and most of the time we will
> have
> >> > to
> >> > > > work with binary format. Please make sure that this case is
> correctly
> >> > > > handled.
> >> > > >
> >> > > > Sergi
> >> > > >
> >> > > > 2016-08-01 18:14 GMT+03:00 Alexander Paschenko <
> >> > > > alexander.a.pasche...@gmail.com>:
> >> > > >
> >> > > >> Guys,
> >> > > >>
> >> > > >> Here's documented version of current API changes - it's quite
> modest
> >> > > >> https://goo.gl/Y6Cv1b
> >> > > >>
> >> > > >> - Alex
> >> > > >>
> >> > > >> 2016-07-28 20:34 GMT+03:00 Alexander Paschenko
> >> > > >> :
> >> > > >> > Sergi,
> >> > > >> >
> >> > > >> > OK, I've done it as you said, thanks.
> >> > > >> > Now working on binary marshaller support.
> >> > > >> >
> >> > > >> > - Alex
> >> > > >> >
> >> > > >> > 2016-07-28 9:08 GMT+03:00 Sergi Vladykin <
> >> sergi.vlady...@gmail.com
> >> > >:
> >> > > >> >> I had a quick look at the PR.
> >> > > >> >>
> >> > > >> >> I don't like this @QueryCacheKey and setKeyProp method on
> public
> >> > API.
> >> > > >> They
> >> > > >> >> solve nothing but add complexity and make key to be stored
> twice
> >> in
> >> > > >> cache,
> >> > > >> >> which is wrong.

Re: Ignite 1.7 RELEASE_NOTES

2016-08-03 Thread Konstantin Boudnik 
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 notes.

Well, a lot of other projects do. And some others don't ;) I guess it depends
on what you want in the RN.

Cos

> On Tue, Aug 2, 2016 at 10:31 PM, Konstantin Boudnik  wrote:
> 
> > Tracking the "Fixed in release" on the JIRA tickets would take care about
> > any
> > gaps pretty much automatically. In general it's a good idea for an RM to
> > run a
> > spring-cleaning on the JIRA tickets to scope up the release. Then once all
> > tickets are fixed, you can simply _generate_ the release notes with a
> > single-button click.
> >
> > Cos
> >
> > On Mon, Aug 01, 2016 at 01:43PM, Pavel Tupitsyn wrote:
> > > Igniters,
> > >
> > > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me.
> > There
> > > are likely more noteworthy changes since 1.6.
> > >
> > > Let's discuss the changes to be included in release notes and fix them.
> > >
> > > Please reply to this email with your proposals.
> > >
> > > Pavel.
> >

Re: [VOTE] Apache Ignite 1.7.0 RC1

2016-08-03 Thread Valentin Kulichenko 
+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 :
> >
> >> +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 <
> >> akuznet...@gridgain.com
> 
> >>> 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 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 <
> >>> akuznet...@gridgain.com
> >
>  wrote:
> 
> > +1
> >
> > Downloaded
> >
> 
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/apache-ignite-1.7.0-src.zip
> > - OK
> > mvn validate -DskipTests -Pcheck-licenses  - OK
> > mvn clean package -DskipTests - OK
> > Unpacked ..\src\target\bin\apache-ignite-fabric-1.7.0-bin.zip  - OK
> > Started several niodes with ignite.bat - OK
> > Started with ignite-schema-import.bat - OK
> >
> >
> > On Tue, Aug 2, 2016 at 10:51 PM, Pavel Tupitsyn <
> >> ptupit...@apache.org>
> > wrote:
> >
> >> Hello,
> >>
> >> We have uploaded the 1.7.0 release candidate to
> >> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/
> >>
> >> Tag name is
> >> 1.7.0-rc1
> >>
> >> This release includes the following changes:
> >>
> >> Ignite:
> >> * Added distributed SQL JOIN.
> >> * Node can be assigned as primary only after preloading is finished.
> >> * Fixed CountDownLatch re-create issue.
> >> * ODBC: Added decimal type support.
> >> * Visor: Fixed data nodes calculation when node filter is set for
> >>> cache.
> >> * Many stability and fault-tolerance fixes.
> >>
> >> Ignite.NET:
> >> * Added ASP.NET Output Cache provider.
> >> * Added ability to use .NET configuration in Apache.Ignite.exe.
> >> * Added ability to implement custom affinity functions.
> >> * Fixed a bug in IBinaryObjectBuilder causing type name to be lost.
> >>
> >> Ignite CPP:
> >> * Marshalling performance improvements.
> >>
> >>
> >> Complete list of closed issues:
> >>
> 
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> >> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
> >>
> >> DEVNOTES
> >>
> >>
> 
> >>>
> >>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/
> >> 1.7.0-rc1
> >>
> >> RELEASENOTES
> >>
> >>
> 
> >>>
> >>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/
> >> 1.7.0-rc1
> >>
> >> Please start voting.
> >>
> >> +1 - to accept Apache Ignite 1.7.0-rc1
> >> 0 - don't care either way
> >> -1 - DO NOT accept Apache Ignite 1.7.0-rc1 (explain why)
> >>
> >> This vote will go for 72 hours.
> >>
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
> 
> 
> 
>  --
>  Alexey Kuznetsov
>  GridGain Systems
>  www.gridgain.com
> 
> >>>
> >>
>
>

Re: [VOTE] Apache Ignite 1.7.0 RC1

2016-08-03 Thread Denis Magda 
+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 
>> wrote:
>> 
>>> +1 (binding)
>>> 
>>> Looks good to me.
>>> 
>>> On Wed, Aug 3, 2016 at 10:48 AM, Alexey Kuznetsov <
>> akuznet...@gridgain.com
 
>>> 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 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 <
>>> akuznet...@gridgain.com
> 
 wrote:
 
> +1
> 
> Downloaded
> 
 
>>> 
>> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/apache-ignite-1.7.0-src.zip
> - OK
> mvn validate -DskipTests -Pcheck-licenses  - OK
> mvn clean package -DskipTests - OK
> Unpacked ..\src\target\bin\apache-ignite-fabric-1.7.0-bin.zip  - OK
> Started several niodes with ignite.bat - OK
> Started with ignite-schema-import.bat - OK
> 
> 
> On Tue, Aug 2, 2016 at 10:51 PM, Pavel Tupitsyn <
>> ptupit...@apache.org>
> wrote:
> 
>> Hello,
>> 
>> We have uploaded the 1.7.0 release candidate to
>> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/
>> 
>> Tag name is
>> 1.7.0-rc1
>> 
>> This release includes the following changes:
>> 
>> Ignite:
>> * Added distributed SQL JOIN.
>> * Node can be assigned as primary only after preloading is finished.
>> * Fixed CountDownLatch re-create issue.
>> * ODBC: Added decimal type support.
>> * Visor: Fixed data nodes calculation when node filter is set for
>>> cache.
>> * Many stability and fault-tolerance fixes.
>> 
>> Ignite.NET:
>> * Added ASP.NET Output Cache provider.
>> * Added ability to use .NET configuration in Apache.Ignite.exe.
>> * Added ability to implement custom affinity functions.
>> * Fixed a bug in IBinaryObjectBuilder causing type name to be lost.
>> 
>> Ignite CPP:
>> * Marshalling performance improvements.
>> 
>> 
>> Complete list of closed issues:
>> 
 
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
>> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
>> 
>> DEVNOTES
>> 
>> 
 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/
>> 1.7.0-rc1
>> 
>> RELEASENOTES
>> 
>> 
 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/
>> 1.7.0-rc1
>> 
>> Please start voting.
>> 
>> +1 - to accept Apache Ignite 1.7.0-rc1
>> 0 - don't care either way
>> -1 - DO NOT accept Apache Ignite 1.7.0-rc1 (explain why)
>> 
>> This vote will go for 72 hours.
>> 
> 
> 
> 
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
> 
 
 
 
 --
 Alexey Kuznetsov
 GridGain Systems
 www.gridgain.com
 
>>> 
>>

Re: [VOTE] Apache Ignite 1.7.0 RC1

2016-08-03 Thread Sergi Vladykin 
+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 <
> akuznet...@gridgain.com
> > >
> > 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 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 <
> > akuznet...@gridgain.com
> > > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Downloaded
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/apache-ignite-1.7.0-src.zip
> > > > - OK
> > > > mvn validate -DskipTests -Pcheck-licenses  - OK
> > > > mvn clean package -DskipTests - OK
> > > > Unpacked ..\src\target\bin\apache-ignite-fabric-1.7.0-bin.zip  - OK
> > > > Started several niodes with ignite.bat - OK
> > > > Started with ignite-schema-import.bat - OK
> > > >
> > > >
> > > > On Tue, Aug 2, 2016 at 10:51 PM, Pavel Tupitsyn <
> ptupit...@apache.org>
> > > > wrote:
> > > >
> > > >> Hello,
> > > >>
> > > >> We have uploaded the 1.7.0 release candidate to
> > > >> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/
> > > >>
> > > >> Tag name is
> > > >> 1.7.0-rc1
> > > >>
> > > >> This release includes the following changes:
> > > >>
> > > >> Ignite:
> > > >> * Added distributed SQL JOIN.
> > > >> * Node can be assigned as primary only after preloading is finished.
> > > >> * Fixed CountDownLatch re-create issue.
> > > >> * ODBC: Added decimal type support.
> > > >> * Visor: Fixed data nodes calculation when node filter is set for
> > cache.
> > > >> * Many stability and fault-tolerance fixes.
> > > >>
> > > >> Ignite.NET:
> > > >> * Added ASP.NET Output Cache provider.
> > > >> * Added ability to use .NET configuration in Apache.Ignite.exe.
> > > >> * Added ability to implement custom affinity functions.
> > > >> * Fixed a bug in IBinaryObjectBuilder causing type name to be lost.
> > > >>
> > > >> Ignite CPP:
> > > >> * Marshalling performance improvements.
> > > >>
> > > >>
> > > >> Complete list of closed issues:
> > > >>
> > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > > >> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
> > > >>
> > > >> DEVNOTES
> > > >>
> > > >>
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/
> > > >> 1.7.0-rc1
> > > >>
> > > >> RELEASENOTES
> > > >>
> > > >>
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/
> > > >> 1.7.0-rc1
> > > >>
> > > >> Please start voting.
> > > >>
> > > >> +1 - to accept Apache Ignite 1.7.0-rc1
> > > >> 0 - don't care either way
> > > >> -1 - DO NOT accept Apache Ignite 1.7.0-rc1 (explain why)
> > > >>
> > > >> This vote will go for 72 hours.
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>

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

2016-08-03 Thread Valentin Kulichenko (JIRA) 
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
  Issue Type: New Feature
  Components: cache
Affects Versions: 1.6
Reporter: Valentin Kulichenko


Sometimes it's useful to know how much memory cache objects consume. We can add 
{{memorySize()}} method to {{CacheMetrics}} and calculate the value  in the 
same way as we do in {{LruEvictionPolicy}}. This works only when cache 
statistics are enabled.



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

Re: IGNITE-2294 implementation details

2016-08-03 Thread Alexander Paschenko 
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 more than once. And after having had a look at
drivers of MySQL and Postgres I can tell that they don't null their
results explicitly and simply return the result they have. Frankly, as
a user, I'd be surprised by getting first a ResultSet and then null
after two consecutive calls of getResultSet. Still, this seems to be
one thing to decide by ourselves, so I'm asking your opinion about
this.

Another thing regarding JDBC driver behavior that I would like to
discuss is batch statements support, particularly behavior in case of
error - implementation of Statement.executeBatch().

JDBC javadocs don't specify what exactly we should do when an error
occurs during execution of some individual batch element - it says
that whether we fail fast or continue execution depends on us, and
this behavior just should be consistent with behavior of DBMS in
general. Here's how other engines handle this.

H2 attempts to run all elements of a batch, then, in case of one (or
more!) errors throws a BatchUpdateException that contains chain of all
exceptions as well as update counters for ALL batch elements - say, if
we have 3 elements batch and failed on first 2 and succeeded with the
3rd, then this exception will bear array of [-1, -1,
update_counter_for_3rd_stmt].

MySQL behaves depending on connection param set in connection string -
it can either fail fast or process all batch elements and then throw a
detailed exception, as H2 does.

Postgres, as I see it from the code, always fails fast.

Which behavior do you think it would be better to implement in Ignite?

- Alex

2016-08-03 15:47 GMT+03:00 Alexander Paschenko
:
> 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.
>
> Second: in JdbcStatement.executeQuery we null 'rs' field, but don't
> set it with the new result set. It gets set only by 'execute' method,
> by result of 'executeQuery' call. However, in javadoc of Statement
> interface there's nothing regarding its 'getResultSet' returning last
> result only on 'execute' call. In other words, it seems to me that
> calling 'getResultSet' after 'executeQuery' will always return null,
> which I doubt is right. Moreover, we null 'rs' field prior to doing
> anything, and I question its correctness (or would like to understand
> reasons behind such design) as well. H2's JdbcStatement overwrites
> previous result only when new one is available - it directly sets new
> result without making field null prior to that. We probably should
> store last result until the new one is actually available, what do you
> think?
>
> - Alex
>
> 2016-08-03 3:15 GMT+03:00 Dmitriy Setrakyan :
>> On Tue, Aug 2, 2016 at 2:21 PM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>>
>>> Dmitriy,
>>>
>>> Sorry, link access fixed, please check now.
>>> Will sum up current status on issue page, meanwhile links to both docs are
>>> there.
>>>
>>
>> Thanks! I have comments, but I will wait till your list the proposed
>> changes in the Jira, so I can comment there.
>>
>>
>>>
>>> — Alex
>>> 2 авг. 2016 г. 10:51 PM пользователь "Dmitriy Setrakyan" <
>>> dsetrak...@apache.org> написал:
>>>
>>> > Alex,
>>> >
>>> > Can you please also make me happy and put all your design into the ticket
>>> > instead of sending it around in emails?
>>> >
>>> > On top of that, the link you provided is protected. I cannot access it.
>>> >
>>> > D.
>>> >
>>> > On Tue, Aug 2, 2016 at 8:24 AM, Alexander Paschenko <
>>> > alexander.a.pasche...@gmail.com> wrote:
>>> >
>>> > > I have pushed "zero" version of JDBC updates support, currently
>>> > > without batching (working on it).
>>> > > Sergi, also to make you happy here's another doc with changes to
>>> > > public API: http://goo.gl/FvGKUs
>>> > >
>>> > > - Alex
>>> > >
>>> > > 2016-08-01 20:06 GMT+03:00 Sergi Vladykin :
>>> > > > Ok, I think you don't really understand what public API really is, so
>>> > let
>>> > > > me clarify. What you have described are all internal classes, public
>>> > API
>>> > > is
>>> > > > what end user will see and work with, like Ignite, IgniteCache,
>>> > > > QueryCursor, etc... All the internal changes do not require any
>>> special
>>> > > > discussion, until they are really complex or big or important, so you
>>> > > think
>>> > > > it makes sense to notify everyone about them.
>>> > > >
>>> > > > Here we should not have any public API changes for now and I

[GitHub] ignite pull request #922: Ignite 2649

2016-08-03 Thread dkarachentsev 
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 these changes as the patch at:

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


commit bfa7bf6c3d693406f1dd5121488796687aebbe7d
Author: vozerov-gridgain 
Date:   2016-03-18T14:45:48Z

IGNITE-2813: IGFS: Optimized metadata values splitting file and directory 
into separate classes.

commit 8de40f2f8649c9ffecf86202f9fd4efbc3827e83
Author: thatcoach 
Date:   2016-03-18T18:15:04Z

IGNITE-2860: IGFS: Fixed minor bug in append() operation.

commit 9a4b5bd720c5ed1f96b82a457fa3eaed1bdbb132
Author: thatcoach 
Date:   2016-03-19T18:13:35Z

IGNITE-2861: IGFS: Moved metadata processors into separate top-level 
classes to simplify code. Also cleaned up IgfsMetaManager from unused code.

commit 2cd0dcb37ce43a4cb07885ddfb2e72392fc814a7
Author: vozerov-gridgain 
Date:   2016-03-21T07:29:20Z

IGNITE-2836: IGFS: Ensured that metadata can be serialized through 
BinaryMarshaller in the most efficient way.

commit 76191ff39456a30246df3aca7c026773d00a8446
Author: vozerov-gridgain 
Date:   2016-03-21T07:36:26Z

IGNITE-2861: Added missing Apache headers.

commit ee5ea53bf9c4ad897459466e0b9b5447fc93ec2a
Author: vozerov-gridgain 
Date:   2016-03-22T06:20:32Z

IGNITE-2869: IGFS: Slightly improved serialization of IgfsListingEntry.

commit 218132dc0c3764966294a5f29ad480af4af7b0ff
Author: vozerov-gridgain 
Date:   2016-03-22T06:23:29Z

IGNITE-2868: IGFS: Increased trash concurrency from 16 to 64.

commit e886ad0aa800cddb3308fa5f8400902e5879ee3c
Author: vozerov-gridgain 
Date:   2016-03-22T07:28:13Z

IGNITE-2811: IGFS: Optimized properties handling.

commit 8d95ebacaa01f3f9271a1ce0d1b991dfead1d0c1
Author: vozerov-gridgain 
Date:   2016-03-22T09:06:51Z

IGNITE-2871: IGFS: Removed "path" from IgfsEntryInfo. Purge event is never 
fired now, it will be fixed as a part of IGNITE-1679.

commit b286facc4b8c44ab1628039dded6c7527760df73
Author: vozerov-gridgain 
Date:   2016-03-22T09:34:35Z

IGNITE-2806: IGFS: Implemented relaxed consistency model.

commit 26f115734e7262d4b4b60f1c6016783f67c66986
Author: vozerov-gridgain 
Date:   2016-03-22T09:46:23Z

IGFS: Added misssing "final" modifiers to FileSystemConfiguration defaults.

commit 00a0e4b51c299871ff690bbe6d462cf80dae045e
Author: vozerov-gridgain 
Date:   2016-03-24T07:35:43Z

IGNITE-2878: IGFS: Optimzied serialization of IgfsListingEntry and 
properties map.

commit 01a6e86ec4e19d372b8efbc5c497c84f4238a46c
Author: vozerov-gridgain 
Date:   2016-03-24T10:28:30Z

IGNITE-2876: Fixed possible starvation in system pool caused by 
IgfsBlockMessage. This closes #575.

commit 59705e008267b1d5926410f95c68bb8ffb8cd93c
Author: vozerov-gridgain 
Date:   2016-03-24T11:29:35Z

IGNITE-2883: IGFS: Now IPC messages are handled in a dedicated thread pool.

commit 0412c9bfd89b8d2a377588e908f1012c845ac5bc
Author: Alexey Kuznetsov 
Date:   2016-03-30T04:43:19Z

Added detail info about keys count in partitions for offheap and swap.

commit 28d2a7bf7f35ec4b51fba872ace47cdbc255ded8
Author: Alexey Kuznetsov 
Date:   2016-03-30T07:42:12Z

Minor change to Visor classes: added setters for name and queryMetrics 
properties.

commit a70d2dc48c42f23b1ea64c2a219560efa44fb99f
Author: Alexey Kuznetsov 
Date:   2016-04-04T07:14:42Z

Minor fix for Visor query metrics.

commit ec2ec9965ae03ef3666b2035a13f444cf2765aec
Author: dkarachentsev 
Date:   2016-03-30T10:29:36Z

Now cache plugins are able to unwrap entries passed to EntryProcessor.

commit e85a7170534cb66f40386cba689cfe632f4e66db
Author: ashutak 
Date:   2016-04-05T11:56:01Z

ignite-2835: Fixed BinaryObjectOffHeapImpl leakage to public code

commit d33b4340a68553e59e4adecf78fea79af55bf2ae
Author: sboikov 
Date:   2016-04-05T13:42:50Z

ignite-2835 Minor test changes.

commit 2397552daf6d8cff9b59515c1c8983abdc60f5f4
Author: vdpyatkov 
Date:   2016-04-05T15:03:55Z

IGNITE-2822
Continuous query local listener can be notified with empty list of events

commit 87f7522c56b5735442f8d52dbc63756de53f2464
Author: sboikov 
Date:   2016-04-06T06:46:47Z

gridgain-7.5.11

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

2016-08-03 Thread tledkov-gridgain 
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 https://github.com/gridgain/apache-ignite ignite-3331

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

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


commit be6ad25e2107267928122cda93dfa28a0da2166d
Author: tledkov-gridgain 
Date:   2016-08-03T13:47:06Z

IGNITE-3331 IGFS: Route client tasks to primary node when metadata 
co-location is enabled.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

2016-08-03 Thread AMashenkov 
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 IGNITE-3597

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

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


commit 5b9d549506710dcdd4699510d24963f8d695ea71
Author: Andrey V. Mashenkov 
Date:   2016-08-03T14:30:35Z

ignite-3597: Fixed.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

2016-08-03 Thread Ksenia Rybakova (JIRA) 
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: Bug
Affects Versions: 1.7
Reporter: Ksenia Rybakova


Drivers hang during streaming load test. Cpu dropps to 0% and test doesn't 
finish. Every time it happens almost at the end of the test. 

Config:
- benchmark: CacheRandomOperation
- 5 hosts
- Heap: 8Gb for servers, 1Gb for clients
- 20 clients, 40 servers
- Number of caches: 12
- Types of caches (atomicity mode): different (atomic, transactional)
- Types of caches (tiered storage mode): different (onheap without eviction, 
onheap with eviction, offheap_tired, offheap_values)
- Types of caches (indexing): different (with and without indexes)
- Types of caches (cache mode): partitioned
- Backups count: 1
- Number of entries: 8M

Benchmark property file and xml configs are attached. Thread dump of one of the 
drivers is attached.



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

Re: IGNITE-2294 implementation details

2016-08-03 Thread Alexander Paschenko 
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.

Second: in JdbcStatement.executeQuery we null 'rs' field, but don't
set it with the new result set. It gets set only by 'execute' method,
by result of 'executeQuery' call. However, in javadoc of Statement
interface there's nothing regarding its 'getResultSet' returning last
result only on 'execute' call. In other words, it seems to me that
calling 'getResultSet' after 'executeQuery' will always return null,
which I doubt is right. Moreover, we null 'rs' field prior to doing
anything, and I question its correctness (or would like to understand
reasons behind such design) as well. H2's JdbcStatement overwrites
previous result only when new one is available - it directly sets new
result without making field null prior to that. We probably should
store last result until the new one is actually available, what do you
think?

- Alex

2016-08-03 3:15 GMT+03:00 Dmitriy Setrakyan :
> On Tue, Aug 2, 2016 at 2:21 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
>> Dmitriy,
>>
>> Sorry, link access fixed, please check now.
>> Will sum up current status on issue page, meanwhile links to both docs are
>> there.
>>
>
> Thanks! I have comments, but I will wait till your list the proposed
> changes in the Jira, so I can comment there.
>
>
>>
>> — Alex
>> 2 авг. 2016 г. 10:51 PM пользователь "Dmitriy Setrakyan" <
>> dsetrak...@apache.org> написал:
>>
>> > Alex,
>> >
>> > Can you please also make me happy and put all your design into the ticket
>> > instead of sending it around in emails?
>> >
>> > On top of that, the link you provided is protected. I cannot access it.
>> >
>> > D.
>> >
>> > On Tue, Aug 2, 2016 at 8:24 AM, Alexander Paschenko <
>> > alexander.a.pasche...@gmail.com> wrote:
>> >
>> > > I have pushed "zero" version of JDBC updates support, currently
>> > > without batching (working on it).
>> > > Sergi, also to make you happy here's another doc with changes to
>> > > public API: http://goo.gl/FvGKUs
>> > >
>> > > - Alex
>> > >
>> > > 2016-08-01 20:06 GMT+03:00 Sergi Vladykin :
>> > > > Ok, I think you don't really understand what public API really is, so
>> > let
>> > > > me clarify. What you have described are all internal classes, public
>> > API
>> > > is
>> > > > what end user will see and work with, like Ignite, IgniteCache,
>> > > > QueryCursor, etc... All the internal changes do not require any
>> special
>> > > > discussion, until they are really complex or big or important, so you
>> > > think
>> > > > it makes sense to notify everyone about them.
>> > > >
>> > > > Here we should not have any public API changes for now and I don't
>> see
>> > > any
>> > > > in your doc, so it looks fine to me.
>> > > >
>> > > > The only possible issue I see is origKeyClass and origValueClass.
>> These
>> > > > classes can be unavailable on nodes and most of the time we will have
>> > to
>> > > > work with binary format. Please make sure that this case is correctly
>> > > > handled.
>> > > >
>> > > > Sergi
>> > > >
>> > > > 2016-08-01 18:14 GMT+03:00 Alexander Paschenko <
>> > > > alexander.a.pasche...@gmail.com>:
>> > > >
>> > > >> Guys,
>> > > >>
>> > > >> Here's documented version of current API changes - it's quite modest
>> > > >> https://goo.gl/Y6Cv1b
>> > > >>
>> > > >> - Alex
>> > > >>
>> > > >> 2016-07-28 20:34 GMT+03:00 Alexander Paschenko
>> > > >> :
>> > > >> > Sergi,
>> > > >> >
>> > > >> > OK, I've done it as you said, thanks.
>> > > >> > Now working on binary marshaller support.
>> > > >> >
>> > > >> > - Alex
>> > > >> >
>> > > >> > 2016-07-28 9:08 GMT+03:00 Sergi Vladykin <
>> sergi.vlady...@gmail.com
>> > >:
>> > > >> >> I had a quick look at the PR.
>> > > >> >>
>> > > >> >> I don't like this @QueryCacheKey and setKeyProp method on public
>> > API.
>> > > >> They
>> > > >> >> solve nothing but add complexity and make key to be stored twice
>> in
>> > > >> cache,
>> > > >> >> which is wrong. Please remove this.
>> > > >> >>
>> > > >> >> If you want to do some public API changes you have to discuss
>> them
>> > > >> publicly
>> > > >> >> before implementing them, ok?
>> > > >> >>
>> > > >> >> I did not look deeper yet, lets fix the obvious issue first.
>> > > >> >>
>> > > >> >> Sergi
>> > > >> >>
>> > > >> >> 2016-07-27 21:44 GMT+03:00 Alexander Paschenko <
>> > > >> >> alexander.a.pasche...@gmail.com>:
>> > > >> >>
>> > > >> >>> Sergi,
>> > > >> >>>
>> > > >> >>> I've made changes to the API according to your valuable
>> > > >> >>> recommendations, thank you very much for giving them. Please
>> refer
>> > > to
>> > > >> >>> PR to see current state of the work.
>> > > >> >>> Will surely look into ODBC, .NET and

Re: [VOTE] Apache Ignite 1.7.0 RC1

2016-08-03 Thread 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  >
> 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 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 <
> akuznet...@gridgain.com
> > >
> > wrote:
> >
> > > +1
> > >
> > > Downloaded
> > >
> >
> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/apache-ignite-1.7.0-src.zip
> > > - OK
> > > mvn validate -DskipTests -Pcheck-licenses  - OK
> > > mvn clean package -DskipTests - OK
> > > Unpacked ..\src\target\bin\apache-ignite-fabric-1.7.0-bin.zip  - OK
> > > Started several niodes with ignite.bat - OK
> > > Started with ignite-schema-import.bat - OK
> > >
> > >
> > > On Tue, Aug 2, 2016 at 10:51 PM, Pavel Tupitsyn 
> > > wrote:
> > >
> > >> Hello,
> > >>
> > >> We have uploaded the 1.7.0 release candidate to
> > >> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/
> > >>
> > >> Tag name is
> > >> 1.7.0-rc1
> > >>
> > >> This release includes the following changes:
> > >>
> > >> Ignite:
> > >> * Added distributed SQL JOIN.
> > >> * Node can be assigned as primary only after preloading is finished.
> > >> * Fixed CountDownLatch re-create issue.
> > >> * ODBC: Added decimal type support.
> > >> * Visor: Fixed data nodes calculation when node filter is set for
> cache.
> > >> * Many stability and fault-tolerance fixes.
> > >>
> > >> Ignite.NET:
> > >> * Added ASP.NET Output Cache provider.
> > >> * Added ability to use .NET configuration in Apache.Ignite.exe.
> > >> * Added ability to implement custom affinity functions.
> > >> * Fixed a bug in IBinaryObjectBuilder causing type name to be lost.
> > >>
> > >> Ignite CPP:
> > >> * Marshalling performance improvements.
> > >>
> > >>
> > >> Complete list of closed issues:
> > >>
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > >> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
> > >>
> > >> DEVNOTES
> > >>
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/
> > >> 1.7.0-rc1
> > >>
> > >> RELEASENOTES
> > >>
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/
> > >> 1.7.0-rc1
> > >>
> > >> Please start voting.
> > >>
> > >> +1 - to accept Apache Ignite 1.7.0-rc1
> > >> 0 - don't care either way
> > >> -1 - DO NOT accept Apache Ignite 1.7.0-rc1 (explain why)
> > >>
> > >> This vote will go for 72 hours.
> > >>
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

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

2016-08-03 Thread tledkov-gridgain 
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 https://github.com/gridgain/apache-ignite ignite-2310-new

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

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


commit 485f4bf6cd9289d8a5364fbe0e93e8204d6311fe
Author: tledkov-gridgain 
Date:   2016-05-27T12:16:27Z

IGNITE-2310 Lock cache partition for affinityRun/affinityCall execution




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: IGNITE-3621 Implementation details

2016-08-03 Thread Vladimir Ozerov 
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
constantly switch back and forth. This is how Ignite works for years and I
doubt we currently consider this as a performance issue. So I doubt we have
any problem with TTL context switches for now.

As per entering critical section inside TTL manager, again - it should be
benchmarked first. E.g. cache with expiry policy vs cache w/o expiry
policy. Even in contented case JVM allows for millions enter-leave cycles
per second for "synchronized" block. So I doubt it is a problem either.

On Wed, Aug 3, 2016 at 1:46 PM, Eduard Shangareev <
eduard.shangar...@gmail.com> wrote:

> 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 notify worker. Obviously, it is not good
> from performance point of view.
>
> So, my proposal is next:
> 1. Expiration should be done on every cache action (on exit thread which
> updates cache should invoke expire).
> 2. TtlManager will exist only in one instance.
> 3. CleanupWorker will be the only backup if there is no cache activity. It
> will wake up with some period to check for work (500 ms, for example).
>
> Moreover, now we keep on-heap pending entries even if a cache is kept
> off-head. At least, this issue needs discussion.
>

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

2016-08-03 Thread Alexey Kuznetsov (JIRA) 
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
  Issue Type: Task
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
Priority: Minor
 Fix For: 1.8


Current implementation of BinaryObject.toString() method print idHash for 
internal objects, for example, for AffinityKey.

This lead to "unstable" result of toString() method, you will get 2 different 
strings on each toString() invocation.

Possible fix: introduce

private static final boolean debug = false;

And check this flag in toString().

If some one will need idHash for debug reasons he could change this flag in its 
private build and debug.



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

IGNITE-3621 Implementation details

2016-08-03 Thread Eduard Shangareev 
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 notify worker. Obviously, it is not good
from performance point of view.

So, my proposal is next:
1. Expiration should be done on every cache action (on exit thread which
updates cache should invoke expire).
2. TtlManager will exist only in one instance.
3. CleanupWorker will be the only backup if there is no cache activity. It
will wake up with some period to check for work (500 ms, for example).

Moreover, now we keep on-heap pending entries even if a cache is kept
off-head. At least, this issue needs discussion.

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

2016-08-03 Thread Eduard Shangareev (JIRA) 
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
  Components: cache
Affects Versions: 1.6
Reporter: Eduard Shangareev


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 notify worker. 
Obviously, it is not good from performance point of view.

So, my proposal is next:
1. Expiration should be done on every cache action (on exit thread which 
updates cache should invoke {{expire}}).
2. TtlManager will exist only in one instance.
3. CleanupWorker will be the only backup if there is no cache activity. It will 
wake up with some period to check for work (500 ms, for example).

Moreover, now we keep on-heap pending entries even if a cache is kept off-head. 
At least, this issue needs discussion.



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

Re: [VOTE] Apache Ignite 1.7.0 RC1

2016-08-03 Thread Vladimir Ozerov 
+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 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  >
> wrote:
>
> > +1
> >
> > Downloaded
> >
> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/apache-ignite-1.7.0-src.zip
> > - OK
> > mvn validate -DskipTests -Pcheck-licenses  - OK
> > mvn clean package -DskipTests - OK
> > Unpacked ..\src\target\bin\apache-ignite-fabric-1.7.0-bin.zip  - OK
> > Started several niodes with ignite.bat - OK
> > Started with ignite-schema-import.bat - OK
> >
> >
> > On Tue, Aug 2, 2016 at 10:51 PM, Pavel Tupitsyn 
> > wrote:
> >
> >> Hello,
> >>
> >> We have uploaded the 1.7.0 release candidate to
> >> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/
> >>
> >> Tag name is
> >> 1.7.0-rc1
> >>
> >> This release includes the following changes:
> >>
> >> Ignite:
> >> * Added distributed SQL JOIN.
> >> * Node can be assigned as primary only after preloading is finished.
> >> * Fixed CountDownLatch re-create issue.
> >> * ODBC: Added decimal type support.
> >> * Visor: Fixed data nodes calculation when node filter is set for cache.
> >> * Many stability and fault-tolerance fixes.
> >>
> >> Ignite.NET:
> >> * Added ASP.NET Output Cache provider.
> >> * Added ability to use .NET configuration in Apache.Ignite.exe.
> >> * Added ability to implement custom affinity functions.
> >> * Fixed a bug in IBinaryObjectBuilder causing type name to be lost.
> >>
> >> Ignite CPP:
> >> * Marshalling performance improvements.
> >>
> >>
> >> Complete list of closed issues:
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> >> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
> >>
> >> DEVNOTES
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/
> >> 1.7.0-rc1
> >>
> >> RELEASENOTES
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/
> >> 1.7.0-rc1
> >>
> >> Please start voting.
> >>
> >> +1 - to accept Apache Ignite 1.7.0-rc1
> >> 0 - don't care either way
> >> -1 - DO NOT accept Apache Ignite 1.7.0-rc1 (explain why)
> >>
> >> This vote will go for 72 hours.
> >>
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

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

2016-08-03 Thread Vasiliy Sisko (JIRA) 
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: Sub-task
Reporter: Vasiliy Sisko






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

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

2016-08-03 Thread ptupitsyn 
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

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

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


commit 7927ab813c75368f6664394c91d21cc61491d675
Author: Pavel Tupitsyn 
Date:   2016-08-03T08:53:23Z

IGNITE-3359 .NET: IgniteConfiguration.ToXml

commit 63aa0bb71bc6341bb9f00c832c8115873cbe8f41
Author: Pavel Tupitsyn 
Date:   2016-08-03T08:54:50Z

wip tests

commit ad4368ab634f816e04d15f665b429d9e4d461116
Author: Pavel Tupitsyn 
Date:   2016-08-03T09:02:44Z

wip

commit c55a4f84123032640fe0a02f54c65891dd90ad12
Author: Pavel Tupitsyn 
Date:   2016-08-03T09:08:52Z

wip

commit 958f34cefb1e4d16a18f6016a256d4c8ba786cb2
Author: Pavel Tupitsyn 
Date:   2016-08-03T09:11:28Z

wip

commit 206f0a1ecae7534a6a7c83e3b9098dea8897dbe3
Author: Pavel Tupitsyn 
Date:   2016-08-03T09:28:27Z

ToXml test done

commit c8448e8f8ba00355e839a7d8b6ea96f3807b82aa
Author: Pavel Tupitsyn 
Date:   2016-08-03T10:03:19Z

wip FromXml

commit 5d862d59a5c4e80b0ba31a00f70c84cc8cd346c1
Author: Pavel Tupitsyn 
Date:   2016-08-03T10:06:36Z

wip tests

commit 60f40a389cfab8ba68c3cd59d8b200bceb4c85ad
Author: Pavel Tupitsyn 
Date:   2016-08-03T10:11:07Z

Tests done

commit ec36f01c30f4811442f34cbfc56933604b737525
Author: Pavel Tupitsyn 
Date:   2016-08-03T10:15:03Z

all done




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #910: Ignite 2310

2016-08-03 Thread tledkov-gridgain 
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #912: Ignite 1.7.1

2016-08-03 Thread asfgit 
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #914: ignite-1.6.4

2016-08-03 Thread asfgit 
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #896: Ignite 1.6.3 3343

2016-08-03 Thread asfgit 
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Apache Ignite 1.7.0 RC1

2016-08-03 Thread Alexey Kuznetsov 
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 
wrote:

> +1
>
> Downloaded
> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/apache-ignite-1.7.0-src.zip
> - OK
> mvn validate -DskipTests -Pcheck-licenses  - OK
> mvn clean package -DskipTests - OK
> Unpacked ..\src\target\bin\apache-ignite-fabric-1.7.0-bin.zip  - OK
> Started several niodes with ignite.bat - OK
> Started with ignite-schema-import.bat - OK
>
>
> On Tue, Aug 2, 2016 at 10:51 PM, Pavel Tupitsyn 
> wrote:
>
>> Hello,
>>
>> We have uploaded the 1.7.0 release candidate to
>> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/
>>
>> Tag name is
>> 1.7.0-rc1
>>
>> This release includes the following changes:
>>
>> Ignite:
>> * Added distributed SQL JOIN.
>> * Node can be assigned as primary only after preloading is finished.
>> * Fixed CountDownLatch re-create issue.
>> * ODBC: Added decimal type support.
>> * Visor: Fixed data nodes calculation when node filter is set for cache.
>> * Many stability and fault-tolerance fixes.
>>
>> Ignite.NET:
>> * Added ASP.NET Output Cache provider.
>> * Added ability to use .NET configuration in Apache.Ignite.exe.
>> * Added ability to implement custom affinity functions.
>> * Fixed a bug in IBinaryObjectBuilder causing type name to be lost.
>>
>> Ignite CPP:
>> * Marshalling performance improvements.
>>
>>
>> Complete list of closed issues:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
>> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
>>
>> DEVNOTES
>>
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/
>> 1.7.0-rc1
>>
>> RELEASENOTES
>>
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/
>> 1.7.0-rc1
>>
>> Please start voting.
>>
>> +1 - to accept Apache Ignite 1.7.0-rc1
>> 0 - don't care either way
>> -1 - DO NOT accept Apache Ignite 1.7.0-rc1 (explain why)
>>
>> This vote will go for 72 hours.
>>
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

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

2016-08-03 Thread vldpyatkov 
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #798: Ignite 3226

2016-08-03 Thread vldpyatkov 
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #825: Gridgain 7.5.27 yardstick

2016-08-03 Thread vldpyatkov 
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---