Re: Enums and SQL queries

[Sergi Vladykin]

I'm not sure what exactly you are going to patch in SQL engine. We could
and some SQL function like enum('MY_ENUM_NAME') but probably it will not
work if we will not pass enum type there as well, so it have look like
enum('com.mycompany.MyEnum', 'MY_ENUM_NAME') which is ugly.

Sergi

On 23 июля 2016 г., 0:43, Valentin Kulichenko  wrote:

> Folks,
>
> I noticed that we currently have a very weird limitation for enum fields
> when running SQL queries. Basically, you can't use enum value names as many
> users would expect.
>
> Technically this happens because binary format stores only ordinal and the
> only way to run such query is to do something like this:
>
> SqlFieldsQuery qry = new SqlFieldsQuery("select * from Table where
> enumField = ?");
> qry.setArgs(MyEnum.ENUM_VALUE);
> cache.query(qry);
>
> This means that this query can be executed only if:
> - IgniteCache API is used. So it doesn't work in JDBC driver, Zeppelin,
> etc.
> - The client that executes the query has the enum class on classpath.
>
> My first thought about fixing this is to somehow store value names in
> binary metadata and patch the SQL engine so that it understands how to use
> this information.
>
> Thoughts?
>
> -Val
>

[GitHub] ignite pull request #887: IGNITE-2344 WebSessionFilter doesn't support sessi...

[samaitra]

GitHub user samaitra opened a pull request:

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

IGNITE-2344 WebSessionFilter doesn't support session ID renewal



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

$ git pull https://github.com/samaitra/ignite IGNITE-2344

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

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


commit c2e9af35635bd92b07ed992a8b0faaeafbedbf41
Author: samaitra 
Date:   2016-06-04T20:39:20Z

IGNITE-2344 WebSessionFilter doesn't support session ID renewal

commit a966f49fb3e7d3f6f22324095b1a10dfb31a261b
Author: samaitra 
Date:   2016-06-04T21:01:13Z

IGNITE-2344 WebSessionFilter doesn't support session ID renewal

commit 7d005184837b93d8edf55b0fef977efc51b94354
Author: samaitra 
Date:   2016-07-22T18:52:32Z

Merge remote-tracking branch 'upstream/master' into IGNITE-2344

# Conflicts:
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteTxExceptionAbstractSelfTest.java
#   
modules/web/src/main/java/org/apache/ignite/cache/websession/WebSessionFilter.java

commit a6e0d56ee78537d5b1964b86d1ea5242e0708b4a
Author: samaitra 
Date:   2016-07-23T03:32:14Z

IGNITE-2344 WebSessionFilter doesn't support session ID renewal

commit 1eaf006987b4b8140fd68faceb3772fb85b1
Author: samaitra 
Date:   2016-07-23T03:33:44Z

IGNITE-2344 WebSessionFilter doesn't support session ID renewal




---
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 #886: Ignite 2294 SQL DML

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

Ignite 2294 SQL DML



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

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

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

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


commit 297ffedb0a1acabf63489ad854af4ed89f014582
Author: Alexander Paschenko 
Date:   2016-07-14T11:33:39Z

GridSqlFunction - don't quote identifier on SQL generation

commit dcaa313c7583745999dc26003d05a04cf4b13ea8
Author: Alexander Paschenko 
Date:   2016-07-14T11:59:30Z

IGNITE-2294 INSERT parsing

commit c2d5082e6f9849d45ad9196d390503f0ff6d49e9
Author: Alexander Paschenko 
Date:   2016-07-15T10:51:00Z

IGNITE-2294 DELETE parsing

commit b538fc9b1519ecdfd9ec330c22030c21261f53f5
Author: Alexander Paschenko 
Date:   2016-07-15T17:28:33Z

IGNITE-2294 UPDATE parsing

commit ec2f3688c110ceeda8cf9ff8ce45feebe8c22469
Author: Alexander Paschenko 
Date:   2016-07-20T11:14:16Z

IGNITE-2294 MERGE parsing

commit cce306e0e72d1ef555e51a361615b79423e288ae
Author: Alexander Paschenko 
Date:   2016-07-22T12:49:28Z

IGNITE-2294 IgniteCache.update() operation and some API placeholders

commit e8c0b6e868233bb48a15ad556808f497017dbab7
Author: Alexander Paschenko 
Date:   2016-07-22T12:50:29Z

IGNITE-2294 Introduced GridSqlStatement to distinguish between queries and 
update operations

commit fa6c6a6fea69b1ad80d6bc3a92d5ade94098e0c4
Author: Alexander Paschenko 
Date:   2016-07-22T12:52:19Z

Javadoc updated.

commit 947c8e61c505c792b2d4ca8c006d9818b42d0d13
Author: Alexander Paschenko 
Date:   2016-07-22T13:10:38Z

IGNITE-2294 Introduced GridQueryIndexing.update() operation.

commit d2ea44f0802a893aa1c4639a4354806a0429505b
Author: Alexander Paschenko 
Date:   2016-07-22T23:23:06Z

IGNITE-2294 First (naive) SQL merge implementation (YAY!)

commit 0d6ae9554b0d59c0027b669c9d4608d79330f93e
Author: Alexander Paschenko 
Date:   2016-07-23T00:28:54Z

Merge branch 'master' into ignite-2294

# Conflicts:
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/opt/GridH2Utils.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/sql/GridSqlQueryParser.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/sql/GridSqlQuerySplitter.java

commit 0d36971e83642ee9735c20038c116c6f592d0304
Author: Alexander Paschenko 
Date:   2016-07-23T00:55:15Z

Post merge fixes

commit 04503c19186e8a2a0fd6cc81b04829b6fcf85a1e
Author: Alexander Paschenko 
Date:   2016-07-23T00:58:53Z

IGNITE-2294 Explicit key merge test

commit 649c63cd7cc153c6cdfc8268aa4c43f1ecbf1d2d
Author: Alexander Paschenko 
Date:   2016-07-23T01:00:11Z

IGNITE-2294 IgniteH2Indexing - fixed returned values




---
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.
---

Enums and SQL queries

[Valentin Kulichenko]

Folks,

I noticed that we currently have a very weird limitation for enum fields
when running SQL queries. Basically, you can't use enum value names as many
users would expect.

Technically this happens because binary format stores only ordinal and the
only way to run such query is to do something like this:

SqlFieldsQuery qry = new SqlFieldsQuery("select * from Table where
enumField = ?");
qry.setArgs(MyEnum.ENUM_VALUE);
cache.query(qry);

This means that this query can be executed only if:
- IgniteCache API is used. So it doesn't work in JDBC driver, Zeppelin, etc.
- The client that executes the query has the enum class on classpath.

My first thought about fixing this is to somehow store value names in
binary metadata and patch the SQL engine so that it understands how to use
this information.

Thoughts?

-Val

Re: Breaking improvements for the Ignite C++.

[Igor Sapego]

Dmitriy,

I've checked Java implementation of the BinaryType and it seems
to be something a bit different than in C++.

Current role of the BinaryType in C++ is to provide Ignite with
the information about its template type, to be used during serialization
and deserialization. Unlike Java version, C++ BinaryType also used
for user to provide implementation of Read and Write methods, i.e.
methods that used to serialize and deserialize objects.

We can not have non-template interface for this class as Write and
Read methods have templated type in theirs signatures:

void Write(BinaryWriter& writer, const T& obj);
T Read(BinaryReader& reader);

We can not change template type T with non-template type as we
don't have single root class in C++ like Object class in Java and
we also don't have any type information at runtime.

Thus we always need to know template type for the BinaryType
when we are instantiating it, thus we can not have any fabrics or any
polymorphism for this class in C++ and internally we always use
default constructor to get new instance of such a class.

So, currently I can not see how having non static methods could be
useful for this class.


Best Regards,
Igor

On Fri, Jul 22, 2016 at 7:12 PM, Dmitriy Setrakyan 
wrote:

> I am not a C++ expert, but can you please explain why you would like to
> change all methods on the BinaryType to static? Is it the same way in Java?
>
> On Fri, Jul 22, 2016 at 9:00 AM, Igor Sapego  wrote:
>
> > Hello Igniters and Ignite users,
> >
> > As there is going to be Ignite 2.0 release soon, It is a good opportunity
> > for us to improve Ignite C++ API without the need to maintain backward
> > compatibility. Let's collect and discuss all the proposal for the changes
> > in API here.
> >
> > If you've had any proposal on how to improve C++ API but that could break
> > backward compatibility, now you can propose that for us to discuss and
> > probably include it in Ignite 2.0. So, go ahead and post your proposals
> > here.
> >
> > Let's create tasks for accepted proposals as subtasks for the task [1] so
> > they all could be easy to track.
> >
> > [1] - https://issues.apache.org/jira/browse/IGNITE-3559
> >
> > Best Regards,
> > Igor
> >
>

Re: Breaking improvements for the Ignite C++.

[Dmitriy Setrakyan]

I am not a C++ expert, but can you please explain why you would like to
change all methods on the BinaryType to static? Is it the same way in Java?

On Fri, Jul 22, 2016 at 9:00 AM, Igor Sapego  wrote:

> Hello Igniters and Ignite users,
>
> As there is going to be Ignite 2.0 release soon, It is a good opportunity
> for us to improve Ignite C++ API without the need to maintain backward
> compatibility. Let's collect and discuss all the proposal for the changes
> in API here.
>
> If you've had any proposal on how to improve C++ API but that could break
> backward compatibility, now you can propose that for us to discuss and
> probably include it in Ignite 2.0. So, go ahead and post your proposals
> here.
>
> Let's create tasks for accepted proposals as subtasks for the task [1] so
> they all could be easy to track.
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-3559
>
> Best Regards,
> Igor
>

[GitHub] ignite pull request #879: IGNITE-3512 .NET: IBinaryObject.ToBuilder loses ty...

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

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


---
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.
---

Breaking improvements for the Ignite C++.

[Igor Sapego]

Hello Igniters and Ignite users,

As there is going to be Ignite 2.0 release soon, It is a good opportunity
for us to improve Ignite C++ API without the need to maintain backward
compatibility. Let's collect and discuss all the proposal for the changes
in API here.

If you've had any proposal on how to improve C++ API but that could break
backward compatibility, now you can propose that for us to discuss and
probably include it in Ignite 2.0. So, go ahead and post your proposals
here.

Let's create tasks for accepted proposals as subtasks for the task [1] so
they all could be easy to track.

[1] - https://issues.apache.org/jira/browse/IGNITE-3559

Best Regards,
Igor

[jira] [Created] (IGNITE-3559) CPP: Review Ignite C++ API and provide list of breaking improvements that can be included in Ignite 2.0

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-3559:
---

 Summary: CPP: Review Ignite C++ API and provide list of breaking 
improvements that can be included in Ignite 2.0
 Key: IGNITE-3559
 URL: https://issues.apache.org/jira/browse/IGNITE-3559
 Project: Ignite
  Issue Type: Task
  Components: odbc
Affects Versions: 1.6
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.0


As there is going to be Ignite 2.0 release soon, It is a good opportunity to 
improve Ignite C++ API without the need to maintain backward compatibility. 
Let's collect and discuss all the proposal for the changes in this task and 
then create matching subtasks for all the accepted proposals.



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

Re: Apache Ignite - New Release

[Dmitriy Setrakyan]

On Fri, Jul 22, 2016 at 7:10 AM, Semyon Boikov  wrote:

> Hi,
>
> Today I merged into master 'distributed join' implementation -
> https://issues.apache.org/jira/browse/IGNITE-1232 (thanks to Sergi, he
> implemented this feature). I think this together with recent bugfixes worth
> 1.7 release. Do you think we can cut off 1.7 release branch from master?
>

Great news. Can you describe that amount of testing we did for this feature?


>
> Thanks
>
>
> On Thu, Jul 21, 2016 at 7:47 PM, Alexandre Boudnik <
> alexander.boud...@gmail.com> wrote:
>
> > Sorry, I missed the typo:
> > To support the point, I would add that PosgreSQL has demonstrated the
> > similar behavior (inspired by unix .dot files and ls):
> > - they have "hidden" column: xmin and xmax in any table
> > - they do not appear in select * list unless they are specified
> explicitly
> > Take care,
> > Alexandre "Sasha" Boudnik
> >
> > call me via Google Voice:
> > 1(405) BUDNIKA
> > 1(405) 283-6452
> >
> >
> >
> > On Thu, Jul 21, 2016 at 12:46 PM, Alexandre Boudnik
> >  wrote:
> > > To support the point, I would add that PosgreSQL has demonstrated the
> > > similar behavior (inspired by unix .dot files and ls):
> > > - they have "hidden" column: xmin and xmax in any table
> > > - they appear in select * list unless they are specified explicitly
> > >
> > > I'll add some notices to the ticket
> > > Take care,
> > > Alexandre "Sasha" Boudnik
> > >
> > > call me via Google Voice:
> > > 1(405) BUDNIKA
> > > 1(405) 283-6452
> > >
> > >
> > >
> > > On Fri, Jul 15, 2016 at 6:37 PM, Valentin Kulichenko
> > >  wrote:
> > >> Agree.
> > >>
> > >> On Fri, Jul 15, 2016 at 12:59 PM, Alexey Goncharuk <
> > >> alexey.goncha...@gmail.com> wrote:
> > >>
> > >>> Looks like the ticket for removing _key and _value from selct * is a
> > good
> > >>> candidate for 2.0.
> > >>>
> > >>> 2016-07-15 5:12 GMT-07:00 Sergi Vladykin :
> > >>>
> > >>> > We will not be able to just change this, because it will brake
> > >>> > compatibility. Still I believe that an option to define our SQL
> > tables
> > >>> > without _key and _value fields. But this is another story you can
> > file a
> > >>> > ticket for it, can we fix somehow our JDBC for now? Like returning
> > >>> > BinaryObject instance or something?
> > >>> >
> > >>> > Sergi
> > >>> >
> > >>> >
> > >>> >
> > >>> > On Fri, Jul 15, 2016 at 2:48 AM, Valentin Kulichenko <
> > >>> > valentin.kuliche...@gmail.com> wrote:
> > >>> >
> > >>> > > IGNITE-3466 is not a JDBC-only issue. This happens because
> 'select
> > *'
> > >>> > query
> > >>> > > returns all the fields including _kay and _val which are created
> by
> > >>> > Ignite,
> > >>> > > not by user. This is actually a usability issue that pops up
> every
> > now
> > >>> > and
> > >>> > > then. This is very counterintuitive that we return the fields
> that
> > user
> > >>> > > never defined (unless he explicitly asks for them, of course) and
> > that
> > >>> > > 'select *' requires class definitions on the client.
> > >>> > >
> > >>> > > Is it possible to fix this on SQL engine level instead of fixing
> > only
> > >>> for
> > >>> > > JDBC? Sergi, what do you think?
> > >>> > >
> > >>> > > -Val
> > >>> > >
> > >>> > > On Thu, Jul 14, 2016 at 3:28 AM, Sergi Vladykin <
> > >>> > sergi.vlady...@gmail.com>
> > >>> > > wrote:
> > >>> > >
> > >>> > > > All these issues seem to be related to Jdbc driver rather than
> > to SQL
> > >>> > > > engine. I think Andrey Gura was the last who worked on it. IMO
> > they
> > >>> > must
> > >>> > > be
> > >>> > > > easy to fix.
> > >>> > > >
> > >>> > > > Sergi
> > >>> > > >
> > >>> > > > On Thu, Jul 14, 2016 at 9:06 AM, Denis Magda <
> > dma...@gridgain.com>
> > >>> > > wrote:
> > >>> > > >
> > >>> > > > > Yakov,
> > >>> > > > >
> > >>> > > > > I'm not the one who is eligible for review of IGNITE-3389.
> > Assigned
> > >>> > it
> > >>> > > on
> > >>> > > > > Andrey Gura. Andrey please find time for review.
> > >>> > > > > Alexander B. when you need a review please send an email to
> > the dev
> > >>> > > list
> > >>> > > > > and someone will assist you.
> > >>> > > > >
> > >>> > > > > As for IGNITE-3466, IGNITE-3467 and 3468 Sergi's opinion is
> > needed.
> > >>> > > Sergi
> > >>> > > > > please have a look.
> > >>> > > > >
> > >>> > > > > --
> > >>> > > > > Denis
> > >>> > > > >
> > >>> > > > >
> > >>> > > > > On Wed, Jul 13, 2016 at 12:13 PM, Yakov Zhdanov <
> > >>> yzhda...@apache.org
> > >>> > >
> > >>> > > > > wrote:
> > >>> > > > >
> > >>> > > > > > Sasha, ignite-3389 is in resolved state and I suppose is
> > ready to
> > >>> > be
> > >>> > > > > > reviewed and merged. Denis, can you please do it? Make sure
> > to
> > >>> > check
> > >>> > > TC
> > >>> > > > > :)
> > >>> > > > > >
> > >>> > > > > > As far as Ignite-3466..3468, Igor, can you please provide
> > >>> feedback
> > >>> > to
> > >>> > > > the
> > >>> > > > > > issues and 

Re: Apache Ignite - New Release

[Semyon Boikov]

Hi,

Today I merged into master 'distributed join' implementation -
https://issues.apache.org/jira/browse/IGNITE-1232 (thanks to Sergi, he
implemented this feature). I think this together with recent bugfixes worth
1.7 release. Do you think we can cut off 1.7 release branch from master?

Thanks


On Thu, Jul 21, 2016 at 7:47 PM, Alexandre Boudnik <
alexander.boud...@gmail.com> wrote:

> Sorry, I missed the typo:
> To support the point, I would add that PosgreSQL has demonstrated the
> similar behavior (inspired by unix .dot files and ls):
> - they have "hidden" column: xmin and xmax in any table
> - they do not appear in select * list unless they are specified explicitly
> Take care,
> Alexandre "Sasha" Boudnik
>
> call me via Google Voice:
> 1(405) BUDNIKA
> 1(405) 283-6452
>
>
>
> On Thu, Jul 21, 2016 at 12:46 PM, Alexandre Boudnik
>  wrote:
> > To support the point, I would add that PosgreSQL has demonstrated the
> > similar behavior (inspired by unix .dot files and ls):
> > - they have "hidden" column: xmin and xmax in any table
> > - they appear in select * list unless they are specified explicitly
> >
> > I'll add some notices to the ticket
> > Take care,
> > Alexandre "Sasha" Boudnik
> >
> > call me via Google Voice:
> > 1(405) BUDNIKA
> > 1(405) 283-6452
> >
> >
> >
> > On Fri, Jul 15, 2016 at 6:37 PM, Valentin Kulichenko
> >  wrote:
> >> Agree.
> >>
> >> On Fri, Jul 15, 2016 at 12:59 PM, Alexey Goncharuk <
> >> alexey.goncha...@gmail.com> wrote:
> >>
> >>> Looks like the ticket for removing _key and _value from selct * is a
> good
> >>> candidate for 2.0.
> >>>
> >>> 2016-07-15 5:12 GMT-07:00 Sergi Vladykin :
> >>>
> >>> > We will not be able to just change this, because it will brake
> >>> > compatibility. Still I believe that an option to define our SQL
> tables
> >>> > without _key and _value fields. But this is another story you can
> file a
> >>> > ticket for it, can we fix somehow our JDBC for now? Like returning
> >>> > BinaryObject instance or something?
> >>> >
> >>> > Sergi
> >>> >
> >>> >
> >>> >
> >>> > On Fri, Jul 15, 2016 at 2:48 AM, Valentin Kulichenko <
> >>> > valentin.kuliche...@gmail.com> wrote:
> >>> >
> >>> > > IGNITE-3466 is not a JDBC-only issue. This happens because 'select
> *'
> >>> > query
> >>> > > returns all the fields including _kay and _val which are created by
> >>> > Ignite,
> >>> > > not by user. This is actually a usability issue that pops up every
> now
> >>> > and
> >>> > > then. This is very counterintuitive that we return the fields that
> user
> >>> > > never defined (unless he explicitly asks for them, of course) and
> that
> >>> > > 'select *' requires class definitions on the client.
> >>> > >
> >>> > > Is it possible to fix this on SQL engine level instead of fixing
> only
> >>> for
> >>> > > JDBC? Sergi, what do you think?
> >>> > >
> >>> > > -Val
> >>> > >
> >>> > > On Thu, Jul 14, 2016 at 3:28 AM, Sergi Vladykin <
> >>> > sergi.vlady...@gmail.com>
> >>> > > wrote:
> >>> > >
> >>> > > > All these issues seem to be related to Jdbc driver rather than
> to SQL
> >>> > > > engine. I think Andrey Gura was the last who worked on it. IMO
> they
> >>> > must
> >>> > > be
> >>> > > > easy to fix.
> >>> > > >
> >>> > > > Sergi
> >>> > > >
> >>> > > > On Thu, Jul 14, 2016 at 9:06 AM, Denis Magda <
> dma...@gridgain.com>
> >>> > > wrote:
> >>> > > >
> >>> > > > > Yakov,
> >>> > > > >
> >>> > > > > I'm not the one who is eligible for review of IGNITE-3389.
> Assigned
> >>> > it
> >>> > > on
> >>> > > > > Andrey Gura. Andrey please find time for review.
> >>> > > > > Alexander B. when you need a review please send an email to
> the dev
> >>> > > list
> >>> > > > > and someone will assist you.
> >>> > > > >
> >>> > > > > As for IGNITE-3466, IGNITE-3467 and 3468 Sergi's opinion is
> needed.
> >>> > > Sergi
> >>> > > > > please have a look.
> >>> > > > >
> >>> > > > > --
> >>> > > > > Denis
> >>> > > > >
> >>> > > > >
> >>> > > > > On Wed, Jul 13, 2016 at 12:13 PM, Yakov Zhdanov <
> >>> yzhda...@apache.org
> >>> > >
> >>> > > > > wrote:
> >>> > > > >
> >>> > > > > > Sasha, ignite-3389 is in resolved state and I suppose is
> ready to
> >>> > be
> >>> > > > > > reviewed and merged. Denis, can you please do it? Make sure
> to
> >>> > check
> >>> > > TC
> >>> > > > > :)
> >>> > > > > >
> >>> > > > > > As far as Ignite-3466..3468, Igor, can you please provide
> >>> feedback
> >>> > to
> >>> > > > the
> >>> > > > > > issues and tell us if we can fit them as well.
> >>> > > > > >
> >>> > > > > > --Yakov
> >>> > > > > >
> >>> > > > > > 2016-07-12 23:33 GMT+03:00 Alexandre Boudnik <
> >>> > > > > alexander.boud...@gmail.com
> >>> > > > > > >:
> >>> > > > > >
> >>> > > > > > > Yakov,
> >>> > > > > > >
> >>> > > > > > > Is it possible to include several probably easy-to-fix
> bugs and
> >>> > > > > > > improvements; they are very annoying and they decrease the
> >>> value
> >>> > of
> >>> > > 

[GitHub] ignite pull request #885: ignite-3476

[EdShangGG]

GitHub user EdShangGG opened a pull request:

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

ignite-3476



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

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

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

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


commit 3e59321ef0ae1d936d94f8f804db45ceeff55844
Author: vozerov-gridgain 
Date:   2016-03-16T09:31:37Z

IGNITE-2842: IGFS: Optimized create/mkdirs operations with help of entry 
processors.

commit f57f3657b1da33abf28f885cd405780dabfd57e3
Author: vozerov-gridgain 
Date:   2016-03-16T10:22:07Z

IGNITE-2846: IGFS: Reworked IgfsMetaManager.updateInfo() operation to use 
"invoke" instead of "put".

commit 8a93c3bf1687e6f2de1a4391d95366d733a44a7d
Author: vozerov-gridgain 
Date:   2016-03-18T13:38:45Z

IGNITE-2860: IGFS: Reworked base meta operations.

commit 8e9e790e482b8911142bf8b21fa3ad7267a62db6
Author: vozerov-gridgain 
Date:   2016-03-18T14:07:58Z

IGNITE-2834: IGFS: Implemented optional metadata co-location.

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 

[jira] [Created] (IGNITE-3558) Affinity task hangs when Collision SPI produces a lot of job rejections & Failover SPI produces many attempts

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-3558:


 Summary: Affinity task hangs when Collision SPI produces a lot of 
job rejections & Failover SPI produces many attempts
 Key: IGNITE-3558
 URL: https://issues.apache.org/jira/browse/IGNITE-3558
 Project: Ignite
  Issue Type: Bug
  Components: compute
Reporter: Taras Ledkov
Assignee: Taras Ledkov


The test to reproduce:
IgniteCacheLockPartitionOnAffinityRunWithCollisionSpiTest#testJobFinishing

*Root cause*
GridJobExecuteResponse isn't set from target node because there is a confusion 
with GridJobWorker instances in the CollisionContext.

*Suggestion*
The method GridJobProcessor.CollisionJobContext.cancel()
use passiveJobs.remove(jobWorker.getJobId(), jobWorker). 
*passiveJobs* is a ConcurrentHashMap and GridJobWorker.equals() implements as a 
equation of jobId.

So, when two thread try to cancel the two workers with *the same jobIds* we 
have the case:
- thread0 remove jobWorker0 & cancel jobWorker0.
- thread0 put jobWorker1 (because jobWorker0 already removed);
- thread1: (has a copy of jobWorker0) and try to cancel it.
- thread1: remove jobWorker1 instead of jobWorker0 (because jobId is used to 
identify);
- thread1: doesn't send ExecuteResponse because jobWorker0 has been canceled.

*Proposal*
Try to use system default equals for the GridJobWorker



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

[GitHub] ignite pull request #884: Ignite 3476

[EdShangGG]

Github user EdShangGG closed the pull request at:

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


---
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 #884: Ignite 3476

[EdShangGG]

GitHub user EdShangGG opened a pull request:

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

Ignite 3476



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

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

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

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


commit 3e59321ef0ae1d936d94f8f804db45ceeff55844
Author: vozerov-gridgain 
Date:   2016-03-16T09:31:37Z

IGNITE-2842: IGFS: Optimized create/mkdirs operations with help of entry 
processors.

commit f57f3657b1da33abf28f885cd405780dabfd57e3
Author: vozerov-gridgain 
Date:   2016-03-16T10:22:07Z

IGNITE-2846: IGFS: Reworked IgfsMetaManager.updateInfo() operation to use 
"invoke" instead of "put".

commit 8a93c3bf1687e6f2de1a4391d95366d733a44a7d
Author: vozerov-gridgain 
Date:   2016-03-18T13:38:45Z

IGNITE-2860: IGFS: Reworked base meta operations.

commit 8e9e790e482b8911142bf8b21fa3ad7267a62db6
Author: vozerov-gridgain 
Date:   2016-03-18T14:07:58Z

IGNITE-2834: IGFS: Implemented optional metadata co-location.

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 

[jira] [Created] (IGNITE-3557) Hadoop: integrate with Ambary management console.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3557:
---

 Summary: Hadoop: integrate with Ambary management console.
 Key: IGNITE-3557
 URL: https://issues.apache.org/jira/browse/IGNITE-3557
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 2.0


This will greatly simplify IGFS cluster management.



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

[jira] [Created] (IGNITE-3556) IGFS: Support external changes to the secondary file system.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3556:
---

 Summary: IGFS: Support external changes to the secondary file 
system.
 Key: IGNITE-3556
 URL: https://issues.apache.org/jira/browse/IGNITE-3556
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 2.0


Currently if secondary file system is changed from the outside, IGFS will stop 
working. We need to support ability to survive external change. It means that 
we must very carefully review every single file system operation and see how it 
should behave in this scenario.



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

[jira] [Created] (IGNITE-3555) IGFS: Expose IGFS as POSIX file system to OS.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3555:
---

 Summary: IGFS: Expose IGFS as POSIX file system to OS.
 Key: IGNITE-3555
 URL: https://issues.apache.org/jira/browse/IGNITE-3555
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 2.0


This way users will be able to mount IGFS and work with it as with any other 
file system.



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

[jira] [Created] (IGNITE-3554) IGFS: Support cross-mode operations.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3554:
---

 Summary: IGFS: Support cross-mode operations.
 Key: IGNITE-3554
 URL: https://issues.apache.org/jira/browse/IGNITE-3554
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 2.0


We need to support operations when certain files/diretories are moved between 
modes. This affects operations where two directories are involved, or several 
paths are affected:
1) create/append
2) mkdirs
3) rename
4) delete




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

[jira] [Created] (IGNITE-3553) Implement internal light-weight closure execution.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3553:
---

 Summary: Implement internal light-weight closure execution.
 Key: IGNITE-3553
 URL: https://issues.apache.org/jira/browse/IGNITE-3553
 Project: Ignite
  Issue Type: Sub-task
  Components: compute, IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.7


The main goal is speed. No failover. No sessions. No injections. Just extremely 
compact message and execution.



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

[jira] [Created] (IGNITE-3552) IGFS: Performance improvements.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3552:
---

 Summary: IGFS: Performance improvements.
 Key: IGNITE-3552
 URL: https://issues.apache.org/jira/browse/IGNITE-3552
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 1.7


This is an umbrella ticket for all recent performance improvements planned for 
IGFS.



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

[jira] [Created] (IGNITE-3551) Hadoop: Improve usability for Apache Ignite 2.0

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3551:
---

 Summary: Hadoop: Improve usability for Apache Ignite 2.0
 Key: IGNITE-3551
 URL: https://issues.apache.org/jira/browse/IGNITE-3551
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 2.0


This is an umbrella ticket to host all IGFS usability improvements targeted for 
Apache Ignite 2.0.



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

[GitHub] ignite pull request #875: IGNITE-3515

[kromulan]

Github user kromulan closed the pull request at:

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


---
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-3549) IGFS: Switch his

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3549:
---

 Summary: IGFS: Switch his
 Key: IGNITE-3549
 URL: https://issues.apache.org/jira/browse/IGNITE-3549
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 2.0


This way we will be more similar to Hadoop {{FileSystem}} API where 
modification time comes first.



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

[jira] [Created] (IGNITE-3548) .NET: Rename ILifecycleBean

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3548:
--

 Summary: .NET: Rename ILifecycleBean
 Key: IGNITE-3548
 URL: https://issues.apache.org/jira/browse/IGNITE-3548
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Bean is a Java term. 

Either rename this interface to something like ILifecycle, or rework the 
lifecycle notifications to C# event handlers.



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

[GitHub] ignite pull request #883: Ignite 1.6.3

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3547) Invalid message send retry with GridTcpNioCommunicationClient

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3547:


 Summary: Invalid message send retry with 
GridTcpNioCommunicationClient
 Key: IGNITE-3547
 URL: https://issues.apache.org/jira/browse/IGNITE-3547
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Blocker
 Fix For: 1.7


GridTcpNioCommunicationClient.sendMessage returns 'retry = true' if message 
send failed with IOException, after this the same client is used to retry send. 
But this client will contain already closed sessio, so sendMessage will always 
fail. Need remove old client and try create new one before retrying send.



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

[GitHub] ignite pull request #883: Ignite 1.6.3

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

Ignite 1.6.3



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

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

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

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


commit 11c7e8fe53461f84924e5c29893865191f236c8c
Author: Anton Vinogradov 
Date:   2016-07-20T08:31:14Z

Documentation fix

commit 9b55658749d0e2a869bbb3614034d8aa1f0e95c1
Author: vozerov-gridgain 
Date:   2016-07-20T11:14:50Z

IGNITE-3405: IGFS: Restricted path modes interleaving, so that now only 
DUAL -> PRIMARY and DUAL -> PROXY paths are possible.

commit 6c5218f4d67c8e247f59dbe8deb58b51db2954a2
Author: vozerov-gridgain 
Date:   2016-07-20T11:15:11Z

Merge remote-tracking branch 'upstream/gridgain-7.6.2' into gridgain-7.6.2




---
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 #882: Ignite 7.6.3

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

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


---
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-3546) IGFS: Review events subsystem.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3546:
---

 Summary: IGFS: Review events subsystem.
 Key: IGNITE-3546
 URL: https://issues.apache.org/jira/browse/IGNITE-3546
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 2.0


Currently we have different event types for various file system operations. But 
we do not fire them always. E.g. if the path {{/a}} is removed, then we will 
fire only one event. We will not fire events for {{/a/b}}.

Is it fine or not? Do we need these events at all or not? May be we want to 
configure event handling somehow? May be users would like to listen such 
events? Need to think about it.



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

[jira] [Created] (IGNITE-3545) IGFS: Review exceptions in secondary file system interface.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3545:
---

 Summary: IGFS: Review exceptions in secondary file system 
interface.
 Key: IGNITE-3545
 URL: https://issues.apache.org/jira/browse/IGNITE-3545
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 2.0


Possible solutions:
1) Throw {{IgniteException}} - looks to broad, but who cares?
2) Throw {{IOException}} - better fits into general understanding of what file 
system is. Having it in the interface will reduce try-catch boilerplate in 
concrete implementations.

Any other ideas?



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

[jira] [Created] (IGNITE-3544) IGFS: Review info() semantics - should it return null or throw exception if file doesn't exist?

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3544:
---

 Summary: IGFS: Review info() semantics - should it return null or 
throw exception if file doesn't exist?
 Key: IGNITE-3544
 URL: https://issues.apache.org/jira/browse/IGNITE-3544
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 2.0


1) Throw exception: clean and simple semantics, but if Hadoop/Spark/etc. 
products return null in this case, we could end up with hot path where 
exception is thrown. This would render bad performance.
2) Return null: always good perf, but additional null-checks will be required.

Alternatively:
- Have a method with exception semantics on public API, but use method with 
null semantics for {{IgniteHadoopFileSystem}}.



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

[jira] [Created] (IGNITE-3543) IGFS: Merge isRetryForSecondary() and verifyIntegrity() methods.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3543:
---

 Summary: IGFS: Merge isRetryForSecondary() and verifyIntegrity() 
methods.
 Key: IGNITE-3543
 URL: https://issues.apache.org/jira/browse/IGNITE-3543
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 1.7


There are two methods with very similar semantics:
1) {{IgfsPathIds.verifyIntegrity}}
2) {{IgfsMetaManager.isRetryForSecondary}}

The latter method ensures that if path is incomplete, then the last existing 
item do not have reference to child with expected name, but unexpected ID. 
Semantically this situation means that concurrent update occurred. 

Instead of heaving two identical methods, we should merge these checks in a 
single method {{IgfsPathIds.verifyIntegrity}}.



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

[jira] [Created] (IGNITE-3542) IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3542:
---

 Summary: IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to 
re-try.
 Key: IGNITE-3542
 URL: https://issues.apache.org/jira/browse/IGNITE-3542
 Project: Ignite
  Issue Type: Bug
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
 Fix For: 1.7


If integrity check failed, it means that some concurrent file system update 
occurred. We should always perform re-try in this case.



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

[jira] [Created] (IGNITE-3541) Visrocmd returns emty list of caches

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-3541:
-

 Summary: Visrocmd returns emty list of caches
 Key: IGNITE-3541
 URL: https://issues.apache.org/jira/browse/IGNITE-3541
 Project: Ignite
  Issue Type: Bug
  Components: visor
Affects Versions: 1.6
Reporter: Sergey Kozlov


1. Start 3 nodes grid with attached config (copy in root fabric directory)
{{bin/ignite.sh visor.xml}}
2. Execute visorcmd with attached batch file
{{bin/ignitevisorcmd.sh visor.bat}}





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

[GitHub] ignite pull request #882: Ignite 7.6.3

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

Ignite 7.6.3



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

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

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

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


commit 11c7e8fe53461f84924e5c29893865191f236c8c
Author: Anton Vinogradov 
Date:   2016-07-20T08:31:14Z

Documentation fix

commit 9b55658749d0e2a869bbb3614034d8aa1f0e95c1
Author: vozerov-gridgain 
Date:   2016-07-20T11:14:50Z

IGNITE-3405: IGFS: Restricted path modes interleaving, so that now only 
DUAL -> PRIMARY and DUAL -> PROXY paths are possible.

commit 6c5218f4d67c8e247f59dbe8deb58b51db2954a2
Author: vozerov-gridgain 
Date:   2016-07-20T11:15:11Z

Merge remote-tracking branch 'upstream/gridgain-7.6.2' into gridgain-7.6.2




---
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-3540) .NET: Review access modifiers

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3540:
--

 Summary: .NET: Review access modifiers
 Key: IGNITE-3540
 URL: https://issues.apache.org/jira/browse/IGNITE-3540
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Currently some classes in internal namespaces are public. This can be fixed in 
2.0.



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

[jira] [Created] (IGNITE-3539) .NET: Remove deprecated code

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3539:
--

 Summary: .NET: Remove deprecated code
 Key: IGNITE-3539
 URL: https://issues.apache.org/jira/browse/IGNITE-3539
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.0






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

[jira] [Created] (IGNITE-3538) Implement remove failover for cache collections

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3538:


 Summary: Implement remove failover for cache collections
 Key: IGNITE-3538
 URL: https://issues.apache.org/jira/browse/IGNITE-3538
 Project: Ignite
  Issue Type: Bug
  Components: data structures
Reporter: Semen Boikov


Now it is possible that node initiated collection remove was able to remove 
collection header, but after that failed, so there could left orphaned 
collection items.



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

[jira] [Created] (IGNITE-3537) Add tests checking that data structures work inside user transactions

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3537:


 Summary: Add tests checking that data structures work inside user 
transactions
 Key: IGNITE-3537
 URL: https://issues.apache.org/jira/browse/IGNITE-3537
 Project: Ignite
  Issue Type: Task
  Components: data structures
Reporter: Semen Boikov
Priority: Minor


Need create tests to check that Ignite data structures work inside user 
transaction. Now data structures should use independent transactions, test 
should jus check that there are no exceptions.



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