Re: How to turn our Nabble list into forums-based community with roles & ranks (gamification) + social media options

[Dmitriy Setrakyan]

Hi Tim,

I have tried the Board application type, but it will not work for us. We
really need to continue using the Forum application type, in which case
your proposed macro does not make sense.

I did add the social medial buttons though.

D.

On Fri, Oct 20, 2017 at 11:00 AM, Tom Diederich 
wrote:

> Igniters! I have an idea for you to vote on.
>
> Here's how to turn our Nabble list into forums-based community with roles &
> ranks (gamification) + social media options (Facebook, Twitter, LinkedIn,
> etc). This would have zero effect on those who prefer email only. But it
> would enable us to have an actual forums page on
> https://ignite.apache.org/community/resources.html that is searchable and
> has some structure.
>
> I was experimenting with Nabble on an account of my own and discovered that
> there are some pretty cool options to turn the list into a forums page with
> some structure to it. Best of all, you can embed the forums onto any
> webpage
> with a snippet of code.
>
> I created a sample page here:
> http://apache-ignite-users-community-forums-dev-version.
> 23092.n8.nabble.com/
>
> *Here’s how I did it to test it out* /(I do not have admin to the actual
> Ignite lists)/
>
> 1)  Go to Nabble.com http://www.nabble.com
> 2)  Click “Create Free Forum.” You can always change it to the other
> options
> listed on this page at any time (archive mailing list, photo gallery, news
> site, blog, resume builder, knowledge base).
> 3)  Follow the simple directions (create user name, forum name, etc.)
> 4)  To embed the dynamic forums into a page on your website (I first
> created
> a blank page for this on my website), click: Options > Embedding options"
> and you will see a text area with a code snippet. Copy and paste that
> snippet into your HTML web page. Now open the page and you will see that
> your forum loads up seamlessly. No installation, no HTML hassle, just copy
> and paste.
>
> *Ranks and roles*
> Ranks are a great way of adding gamification to your community…. That
> addictive element that encourages members to participate. Roles, on the
> other hand, are great way of clearly showing your place in the community,
> such as “Admin” and “Moderator.”
>
> The Nabble team has yet call out ranks as an option but there is a simple
> hack that will give our community this awesome gamification feature with a
> simple copy and paste of some code. This will let you create ranks of your
> choosing based on post count. Ideally this would be accomplished via a
> formula such as post count, Likes, shares, etc. But we’ll take what we can
> get – this is after all, free.
>
> In the code below, starting from the bottom, you’ll see the ranks used in
> this example (Newbie, Helper, Master, Guru). You can change those by
> swapping out the names with whatever you come up with.
>
> *To create ranks (and by default, enable roles)*
>
> 1.  Look at the bottom right-hand corner of your forums page. Click
> “Edit
> this page.”
> 2.  Click the green gear to the left of “view_board.”
> 3.  Next, “Search macros.”
> 4.  In the search field, type “post_count”
> 5.  Click the hyper-link “post_count”
> 6.  Click “Override this macro”
> 7.  Paste in the following then hit “Save changes”
>
> 
> 
> 
> 
> var $div = $('div.post-count');
> $div.html(' n="[n.page_user.post_count_value/]" one_text="[t]post[/t]"
> many_text="[t]posts[/t]"/>');
>
> $div.append("");
> var postCount = ;
> if (postCount > 300)
> $div.append("Elite Member");
> else if (postCount > 200)
> $div.append("Guru");
> else if (postCount > 100)
> $div.append("Master");
> else if (postCount > 50)
> $div.append("Helper");
> else
> $div.append("Newbie");
> 
> 
> 
> 
>
> *Social engagement buttons*
> Adding social buttons for users to share specific posts can help drive more
> people to our community and also serve as a pat-on-the-back to authors.
> Nabble has a button to "tweet" posts, along with a Facebook Like button and
> a Google+ share button.
>
> *To add those to this community:*
> 1)  Click “Options”
> 2)  Click “Application”
> 3)  Click “Extras and add-ons”
> 4)  Check the four boxes
> 5)  Click “Save Changes”
>
> In addition to those three buttons, from each post community members can
> click “More” /(next to the “Reply” button)/ to post to Twitter, Facebook,
> Delicious, Stumble Upon, LinkedIn, Google Bookmarks and Digg.
>
> Also, going back a little to “Applications,” you’ll also see some other
> cool
> features you can add, including adding Google Analytics account ID.
>
> I'm more than happy to help if you all decide you'd like to give this a
> try.
> You can always turn it 

Re: Fix IgniteSpringBean in 2.x

[Valentin Kulichenko]

Alex,

I tried to investigate this scenario and it looks it is reproduced only if:
- Injected bean is a singleton
- Injected bean is created *after* IgniteSpringBean

Do you know if there is a way to verify that required singleton is already
created before injecting it, without acquiring the same global lock? If
yes, then I would do this and just throw an exception if bean is not ready,
explaining how to fix it (e.g. using 'depends-on' attribute). This way we
will not change current semantics and will avoid deadlocks.

What do you think?

-Val

On Wed, Oct 18, 2017 at 12:57 PM, Alexander Fedotov <
alexander.fedot...@gmail.com> wrote:

> Hi Val,
>
> SmartInitializingSingleton#afterSingletonsInstantiated is invoked right at
> the end of the singleton pre-instantiation phase, *with a guarantee that
> all regular singleton beans have been created already*.
> This behavior allows avoiding the deadlock case described in the first
> message.
> InitializingBean#afterPropertiesSet method is called when a lock on the
> Spring's internal collection of singleton beans is being held (due to a
> singleton bean instantiation)
> and not all singleton beans have been initialized.
>
> With SmartInitializingSingleton approach it won't be possible to call
> Ignite instance methods inside any kind of init methods of other beans.
> For example, it won't be possible to call any operation on the Ignite
> instance inside @PostConstruct annotated methods because the Ignite
> instance won't be started by that time.
>
> Kind regards,
> Alex.
>
> On Wed, Oct 18, 2017 at 8:50 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Hi Alex,
> >
> > This indeed has to be fixed, I've seen this issue multiple times.
> >
> > Can you please clarify the difference between SmartInitializingSingleton
> > and InitializingBean? And what exactly will not work if we switch? Can
> you
> > give an example?
> >
> > -Val
> >
> > On Wed, Oct 18, 2017 at 8:56 AM, Alexander Fedotov <
> > alexander.fedot...@gmail.com> wrote:
> >
> > > Hi Igniters,
> > >
> > > There is an issue that IgniteSpringBean deadlocks when there is
> > CacheStore,
> > > Service, you name it with @SpringResource annotated fields
> > > https://issues.apache.org/jira/browse/IGNITE-6555. The issue appeared
> > > after
> > > moving the logic for starting statically configured caches to operate
> in
> > > the same way as for dynamic ones: from GridDhtPartitionsExchangeFutur
> e.
> > > Deadlock occurs because IgniteSpringBean having acquired internal
> Spring
> > > lock waits for a GridDhtPartitionsExchangeFuture which is executed in
> a
> > > separate thread and which in turn tries to inject @SpringResource
> > annotated
> > > fields using the passed Spring application context what leads to an
> > attempt
> > > to acquire the same internal Spring lock that is already being held by
> > the
> > > main thread.
> > >
> > > A possible solution is to remove IgniteSpringBean#afterPropertiesSet,
> > make
> > > IgniteSpringBean implement SmartInitializingSingleton and start Ignite
> > > instance inside afterSingletonsInstantiated.
> > > The only possible problem here is that an Ignite bean cannot be
> > > referenced from init-like methods: afterPropertiesSet, @PostConstruct
> > etc.
> > >
> > > Any thoughts? Suggestions?
> > >
> > > Kind regards,
> > > Alex.
> > >
> >
>

Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

[Denis Magda]

Folks,

After we added CACHE_NAME, KEY_TYPE and VALUE_TYPE parameters [1] to CREATE 
TABLE syntax for 2.3, I’ve returned to a simple demo application [2] that aims 
to show how to use key-value, compute, service grid APIs in the cluster fully 
configured with DDL.

So, what was done and works:
* started the cluster with this config [3] (built binary from 2.3 branch).
* configured the cluster and preloaded data using this SQL script [4] fed to 
SQLLine tool.
* double checked that Java SQL APIs are workable.[5]
* could get a value with the key of BinaryObject type! [6] Something we didn’t 
support in 2.2.

But then got stuck with the following:
* failed to deserialize BinaryObject value to City type [7]. Just classical 
"class org.apache.ignite.binary.BinaryInvalidTypeException: City" caused by 
"Caused by: java.lang.ClassNotFoundException: City”.
* failed to implement hashCode for CityKey for non binary key-val access. 
Thought I could setup BinaryArrayIdentityResolver for CityKey type to address 
the issue but we removed resolvers from the public configuration.
*  as a Java developer I was forced to name at least CityKey’s affinity field 
[9] in the way it's named in CREATE TABLE command [2]. Not a blocker but a big 
usability issue. Can we have case insensitive policy for fields names? 

Vladimir, Alex P., will highly appreciate if you look at this before the 
release and help to overcome the issues I’m facing.

[1] https://apacheignite-sql.readme.io/docs/create-table#section-parameters
[2] https://github.com/dmagda/ignite_world_demo
[3] 
https://github.com/dmagda/ignite_world_demo/blob/master/config/ignite-config.xml
[4] https://github.com/dmagda/ignite_world_demo/blob/master/ignite_world.sql
[5] 
https://github.com/dmagda/ignite_world_demo/tree/master/src/main/java/demo/sql
[6] 
https://github.com/dmagda/ignite_world_demo/blob/master/src/main/java/demo/keyvalue/KeyValueDataProcessing.java#L83
[7] 
https://github.com/dmagda/ignite_world_demo/blob/master/src/main/java/demo/keyvalue/KeyValueDataProcessing.java#L86
[8] 
https://github.com/dmagda/ignite_world_demo/blob/master/src/main/java/demo/model/CityKey.java#L44
[9] 
https://github.com/dmagda/ignite_world_demo/blob/master/src/main/java/demo/model/CityKey.java#L14


—
Denis

Re: CacheConfiguration reusage issues with EvictionPolicy enabled.

[Valentin Kulichenko]

I don't think it's a big problem. But it would be great if someone better
experienced in Hadoop stuff chimes in.

-Val

On Fri, Oct 20, 2017 at 8:50 AM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Val,
>
> It doesn't look possible to do without refactoring.
> I've make a PR#2896 [1] with a fix and want to someone look at it
> as I'm not familiar with Hadoop module.
>
> Will it be ok to left it "as is" for now and create a ticket for
> refactoring?
>
>
> On Fri, Oct 20, 2017 at 3:15 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Andrey,
> >
> > Using factory instead of policy instance in configuration makes sense to
> > me, I think we should do this change.
> >
> > As for Hadoop module issue, is it possible to do the mentioned validation
> > after creating the policy? I think that should fix the problem.
> >
> > -Val
> >
> > On Thu, Oct 19, 2017 at 7:50 AM Andrey Mashenkov <
> > andrey.mashen...@gmail.com>
> > wrote:
> >
> > > Hi Igniters,
> > >
> > > I'm working on a ticket IGNITE-6649 [1] and got stuck.
> > > Currently, we allow user to set EvictionPolicy instance into
> > configuration
> > > instead of factory.
> > > The leads to some isses when user tries to reuse EvictionPolicy
> instance,
> > > e.g. it doesn't clean its queue on cache stop.
> > >
> > > Seems, we should replace EvictionPolicy with its factory as policy
> objec
> > is
> > > a statefull object and current approach is error prone.
> > >
> > > The issue I faced is that we make checks for EvicitonPolicy derives
> some
> > > known class in several code places.
> > > E.g. in HadoopModule you can find IgfsPerBlockLruEvictionPolicy usages.
> > > What will be correct way to overwork this with using facrories?
> > >
> > >
> > > Also, I've noticed that we check EvictionPolicy instances if they
> > implement
> > > LifecycleAware interface and no one policy available out-of-box really
> > > implements it.
> > > The second way here is to make these EvictionPolicies implements
> > > LifecycleAware interface and gracefully clean their queues.
> > > This will resolve the issue for case when user recreate cache with same
> > > configuration instance,
> > > but seem will not help in case when user share EvictionPolicy instance
> > for
> > > several caches.
> > >
> > >
> > > Also`EvictionPolicies has non-transient "queue" field, so queue may
> leak
> > to
> > > another node.
> > > I'm not sure it can happens, I'll check.
> > >
> > > Thoughts?
> > >
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-6649
> > >
> > > --
> > > Best regards,
> > > Andrey V. Mashenkov
> > >
> >
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

Re: Adding sqlline tool to Apache Ignite project

[Denis Magda]

Has the tool been renamed? Give us an intermediate build. We need to finalize 
the doc and screencast.

—
Denis

> On Oct 19, 2017, at 10:26 AM, Denis Magda  wrote:
> 
>>> How about renaming it to "sqlline”?
> 
> No objections from my side. Who will do the renaming? Please send a note once 
> it happens so that Prachi can update the doc and screencast.
> 
> 
> Prachi, 
> 
> The doc looks good, thanks! Please keep an eye on the discussion and rename 
> the script both in the docs and screencasts once the change is applied.
> 
> 
> Anton,
> 
> All the cosmetic changes (2.1 to 2.3) will be done before the doc release. 
> Presently it’s not exposed anywhere and invisible for Google crawlers.
> 
> —
> Denis
> 
>> On Oct 19, 2017, at 2:27 AM, Anton Vinogradov  
>> wrote:
>> 
>> Prachi,
>> Seems, documentation should point to 2.3 instead of 2.1?
>> 
>> On Thu, Oct 19, 2017 at 9:30 AM, Vladimir Ozerov 
>> wrote:
>> 
>>> Igniters,
>>> 
>>> We named the script "Ignitesql.sh" because initially we thought that it
>>> would have additional logic. But now it is merely a thin wrapper around
>>> sqlline which only contains classpath creation logic and some convenient
>>> defaults. How about renaming it to "sqlline"?
>>> 
>>> чт, 19 окт. 2017 г. в 2:27, Prachi Garg :
>>> 
 Here is the link for SQLLine documentation -
 https://apacheignite-sql.readme.io/v2.1/docs/sqlline
 
 -P
 
 On Tue, Oct 17, 2017 at 11:54 AM, Denis Magda  wrote:
 
> Looks good to me. Prachi will help us documenting the tool usage:
> https://issues.apache.org/jira/browse/IGNITE-6656 <
> https://issues.apache.org/jira/browse/IGNITE-6656>
> 
> However, I can’t conceive how to see a table structure (columns and
>>> their
> types, indexes with names and types) using SQLLine. I’ve tried
>>> !metadata
> with a variety of parameters but no luck. As for !indexes and !tables
> commands they just print out table names and secondary indexes omitting
> columns, indexes types and *primary indexes*. Considering that Ignite
> doesn’t support standard *describe* command I assumed SQLLine would
>>> help
 us
> out. But how do I do this with SQLLine?
> 
> —
> Denis
> 
>> On Oct 17, 2017, at 4:33 AM, Oleg Ostanin 
 wrote:
>> 
>> New example build with sqlline:
>> 
>> https://ci.ignite.apache.org/viewLog.html?buildId=894407;
> tab=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> pareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp
>> 
>> 
>> On Wed, Oct 11, 2017 at 1:00 AM, Denis Magda 
 wrote:
>> 
>>> Oleg,
>>> 
>>> Looks good to me. Please consider the notes left in the ticket. I
>>> want
> us
>>> to prepare a script for Windows, review the language for help notice
 and
>>> errors, put together documentation. Prachi will be able to help with
 the
>>> editing and documentation.
>>> 
>>> —
>>> Denis
>>> 
 On Oct 9, 2017, at 10:13 AM, Oleg Ostanin 
> wrote:
 
 New build with fixed argument parsing:
 https://ci.ignite.apache.org/viewLog.html?buildId=882282;
>>> tab=artifacts=IgniteRelease_
>>> XxxFromMirrorIgniteRelease3Pre
>>> pareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp
 
 On Mon, Oct 9, 2017 at 5:38 PM, Denis Magda 
> wrote:
 
> I think it’s a must have for the ticket resolution.
> 
> Denis
> 
> On Monday, October 9, 2017, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
> 
>> Any plans to have ignitesql.bat?
>> 
>> On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin <
 oosta...@gridgain.com
>> > wrote:
>> 
>>> Another build with sqlline included:
>>> https://ci.ignite.apache.org/viewLog.html?buildId=881120;
>>> tab=artifacts=IgniteRelease_
>>> XxxFromMirrorIgniteRelease3Pre
>>> pareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp
>>> 
>>> On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda <
>>> dma...@gridgain.com
>> > wrote:
>>> 
 No more doubts on my side. +1 for Vladimir’s suggestion.
 
 Denis
 
 On Saturday, October 7, 2017, Dmitriy Setrakyan <
> dsetrak...@apache.org
>> >
 wrote:
 
> I now tend to agree with Vladimir. We should always require
>>> that
> some
> address is specified. The help menu should clearly state how
>>> to
>> connect
 to
> a localhost.
> 
> D.
> 
> On Sat, Oct 7, 2017 at 12:44 AM, 

How to turn our Nabble list into forums-based community with roles & ranks (gamification) + social media options

[Tom Diederich]

Igniters! I have an idea for you to vote on. 

Here's how to turn our Nabble list into forums-based community with roles &
ranks (gamification) + social media options (Facebook, Twitter, LinkedIn,
etc). This would have zero effect on those who prefer email only. But it
would enable us to have an actual forums page on
https://ignite.apache.org/community/resources.html that is searchable and
has some structure.

I was experimenting with Nabble on an account of my own and discovered that
there are some pretty cool options to turn the list into a forums page with
some structure to it. Best of all, you can embed the forums onto any webpage
with a snippet of code.

I created a sample page here:
http://apache-ignite-users-community-forums-dev-version.23092.n8.nabble.com/ 

*Here’s how I did it to test it out* /(I do not have admin to the actual
Ignite lists)/

1)  Go to Nabble.com http://www.nabble.com 
2)  Click “Create Free Forum.” You can always change it to the other options
listed on this page at any time (archive mailing list, photo gallery, news
site, blog, resume builder, knowledge base).
3)  Follow the simple directions (create user name, forum name, etc.)
4)  To embed the dynamic forums into a page on your website (I first created
a blank page for this on my website), click: Options > Embedding options"
and you will see a text area with a code snippet. Copy and paste that
snippet into your HTML web page. Now open the page and you will see that
your forum loads up seamlessly. No installation, no HTML hassle, just copy
and paste.

*Ranks and roles*
Ranks are a great way of adding gamification to your community…. That
addictive element that encourages members to participate. Roles, on the
other hand, are great way of clearly showing your place in the community,
such as “Admin” and “Moderator.”

The Nabble team has yet call out ranks as an option but there is a simple
hack that will give our community this awesome gamification feature with a
simple copy and paste of some code. This will let you create ranks of your
choosing based on post count. Ideally this would be accomplished via a
formula such as post count, Likes, shares, etc. But we’ll take what we can
get – this is after all, free. 

In the code below, starting from the bottom, you’ll see the ranks used in
this example (Newbie, Helper, Master, Guru). You can change those by
swapping out the names with whatever you come up with.

*To create ranks (and by default, enable roles)*
 
1.  Look at the bottom right-hand corner of your forums page. Click “Edit
this page.”
2.  Click the green gear to the left of “view_board.”
3.  Next, “Search macros.”
4.  In the search field, type “post_count”
5.  Click the hyper-link “post_count”
6.  Click “Override this macro”
7.  Paste in the following then hit “Save changes”

  
  
  
  
var $div = $('div.post-count');  
$div.html('');  
  
$div.append("");  
var postCount = ;  
if (postCount > 300)  
$div.append("Elite Member");  
else if (postCount > 200)  
$div.append("Guru");  
else if (postCount > 100)  
$div.append("Master");  
else if (postCount > 50)  
$div.append("Helper");  
else  
$div.append("Newbie");  
  
  
  


*Social engagement buttons*
Adding social buttons for users to share specific posts can help drive more
people to our community and also serve as a pat-on-the-back to authors.
Nabble has a button to "tweet" posts, along with a Facebook Like button and
a Google+ share button. 

*To add those to this community:*
1)  Click “Options”
2)  Click “Application”
3)  Click “Extras and add-ons”
4)  Check the four boxes
5)  Click “Save Changes”

In addition to those three buttons, from each post community members can
click “More” /(next to the “Reply” button)/ to post to Twitter, Facebook,
Delicious, Stumble Upon, LinkedIn, Google Bookmarks and Digg.  

Also, going back a little to “Applications,” you’ll also see some other cool
features you can add, including adding Google Analytics account ID. 

I'm more than happy to help if you all decide you'd like to give this a try.
You can always turn it off if it doesn't work out. 
Tom



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #2899: ignite 12992

[ntikhonov]

GitHub user ntikhonov opened a pull request:

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

ignite  12992



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

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

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

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


commit 0c5bf92a56eb4df089291bafe4a2cf76bf14982c
Author: Andrey V. Mashenkov 
Date:   2017-06-05T09:48:44Z

Merge branch 'ignite-1.8.7' into ignite-1.9.4

# Conflicts:
#   
modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/datasource/DataSource.java
#   
modules/cassandra/store/src/test/java/org/apache/ignite/tests/IgnitePersistentStoreTest.java
#   
modules/clients/src/test/java/org/apache/ignite/internal/jdbc2/JdbcAbstractDmlStatementSelfTest.java
#   
modules/clients/src/test/java/org/apache/ignite/jdbc/suite/IgniteJdbcDriverTestSuite.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePreloaderAdapter.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPartitionDemander.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPreloader.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/CacheRebalancingSelfTest.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/service/GridServiceProcessorMultiNodeConfigSelfTest.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/service/GridServiceProcessorMultiNodeSelfTest.java

commit 374cba8a2b0d4438b46258a4ea89e43ab1e7989c
Author: dkarachentsev 
Date:   2017-06-06T13:17:01Z

IGNITE-5259 Minor serialization fix

commit 5cb580ad7043f27e4a0396aea1f877c21d49078e
Author: dkarachentsev 
Date:   2017-06-06T13:17:01Z

IGNITE-5259 Minor serialization fix

(cherry picked from commit 374cba8)

commit f03252f9b2c6f0e777f307fd85cc8bd20ab21423
Author: dkarachentsev 
Date:   2017-06-06T13:17:01Z

IGNITE-5259 Minor serialization fix

(cherry picked from commit 374cba8)

commit d2bf9619aaf867f251bc193d913dd4cc174a33a3
Author: Ivan Veselovskiy 
Date:   2017-06-06T13:56:09Z

IGNITE-5410: Fixed assertion in HadoopDataOutStream. This closes #2084.

commit 77ff30cc08dae653c0b914167088e9e90cdadd32
Author: dkarachentsev 
Date:   2017-06-06T14:12:27Z

IGNITE-5259 Minor serialization fix

commit be2bf6509816d2dc25fe9798b746a0f5c9014124
Author: dkarachentsev 
Date:   2017-06-06T14:12:42Z

Merge remote-tracking branch 'origin/ignite-1.9.3' into ignite-1.9.3

commit 3a1d560cd8741de9e7a6dd1110b42814d0ccff6b
Author: dkarachentsev 
Date:   2017-06-06T14:13:52Z

IGNITE-5259 Minor serialization fix

commit 56d4ce8a042238654ab96235d1a2969107b8881c
Author: devozerov 
Date:   2017-06-06T14:39:33Z

GG-12244: Fixed a bug in GridH2IndexRangeRequest serialization mechanics.

commit f1b8a7d8407fbc990e7027b17e366d30f05c1ab6
Author: devozerov 
Date:   2017-06-06T14:40:01Z

Merge remote-tracking branch 'upstream/ignite-1.9.3' into ignite-1.9.3

commit cfbe8da934741e76c8964af87671a38ec7b6c9a3
Author: dkarachentsev 
Date:   2017-06-06T16:15:59Z

IGNITE-5103 Rolled back due to test failings.

commit 83307da08289c873c5c2eb02d5eb314018bc5c13
Author: Ivan Veselovskiy 
Date:   2017-06-06T13:56:09Z

IGNITE-5410: Fixed assertion in HadoopDataOutStream. This closes #2084.

(cherry picked from commit d2bf961)

commit e95626d609ee225918b49653b7981b180e5d4e49
Author: Evgenii Zhuravlev 
Date:   2017-06-01T16:56:34Z

SSL fix

(cherry picked from commit 95d5595)

commit 340204637a03e5533685f1b11ca65c9121f6e193
Author: Alexei Kaigorodov 
Date:   2017-06-08T16:37:40Z

IGNITE-5103 Rolled back due to test failings. (#69)

commit f3f726e9059e492573dc5125fd5edb5d2f71e9d3
Author: Andrey V. Mashenkov 
Date:   2017-06-13T11:11:17Z

IGNITE-4196: Added means to specify port for H2 debug console. This closes 
#1486.

(cherry picked from commit b246260)

commit c2c237d1222557d3e6b35d9a51a61a4c78e56782
Author: Sergey Kalashnikov 
Date:   2017-02-03T08:41:14Z

IGNITE-4196: Added means to specify port for H2 debug console. This closes 
#1486.

(cherry picked from commit 

Re: CacheConfiguration reusage issues with EvictionPolicy enabled.

[Andrey Mashenkov]

Val,

It doesn't look possible to do without refactoring.
I've make a PR#2896 [1] with a fix and want to someone look at it
as I'm not familiar with Hadoop module.

Will it be ok to left it "as is" for now and create a ticket for
refactoring?


On Fri, Oct 20, 2017 at 3:15 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Andrey,
>
> Using factory instead of policy instance in configuration makes sense to
> me, I think we should do this change.
>
> As for Hadoop module issue, is it possible to do the mentioned validation
> after creating the policy? I think that should fix the problem.
>
> -Val
>
> On Thu, Oct 19, 2017 at 7:50 AM Andrey Mashenkov <
> andrey.mashen...@gmail.com>
> wrote:
>
> > Hi Igniters,
> >
> > I'm working on a ticket IGNITE-6649 [1] and got stuck.
> > Currently, we allow user to set EvictionPolicy instance into
> configuration
> > instead of factory.
> > The leads to some isses when user tries to reuse EvictionPolicy instance,
> > e.g. it doesn't clean its queue on cache stop.
> >
> > Seems, we should replace EvictionPolicy with its factory as policy objec
> is
> > a statefull object and current approach is error prone.
> >
> > The issue I faced is that we make checks for EvicitonPolicy derives some
> > known class in several code places.
> > E.g. in HadoopModule you can find IgfsPerBlockLruEvictionPolicy usages.
> > What will be correct way to overwork this with using facrories?
> >
> >
> > Also, I've noticed that we check EvictionPolicy instances if they
> implement
> > LifecycleAware interface and no one policy available out-of-box really
> > implements it.
> > The second way here is to make these EvictionPolicies implements
> > LifecycleAware interface and gracefully clean their queues.
> > This will resolve the issue for case when user recreate cache with same
> > configuration instance,
> > but seem will not help in case when user share EvictionPolicy instance
> for
> > several caches.
> >
> >
> > Also`EvictionPolicies has non-transient "queue" field, so queue may leak
> to
> > another node.
> > I'm not sure it can happens, I'll check.
> >
> > Thoughts?
> >
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-6649
> >
> > --
> > Best regards,
> > Andrey V. Mashenkov
> >
>



-- 
Best regards,
Andrey V. Mashenkov

[jira] [Created] (IGNITE-6695) Validation of joining node data consistency WRT the same data in grid

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-6695:
---

 Summary: Validation of joining node data consistency WRT the same 
data in grid
 Key: IGNITE-6695
 URL: https://issues.apache.org/jira/browse/IGNITE-6695
 Project: Ignite
  Issue Type: New Feature
  Security Level: Public (Viewable by anyone)
  Components: persistence
Reporter: Sergey Chugunov


h2. Scenario
Consider the following simple scenario (persistence is active):
# Start nodes A and B, activate, add (K1, V1) to cache.
# Stop A; update K1 to (K1, V2) (only B is aware of update). Stop B.
# Start A, activate, update K1 to (K1, V3).
After that B joining the cluster will lead to ambiguity of K1 value.

Also even having BaselineTopology tracking history of cluster nodes activations 
won't help here as after #3 node B's history is compatible with node A's 
history.

h2. Description
When there is load of data updates and user turns off nodes one by one, it is 
important to start nodes back in the opposite order. Node turned off the last 
must be started first and so one.
If it is not the case, situations like described above may happen.

A mechanism to detect this scenarios and refuse to join nodes with potentially 
conflicting data is needed.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: sql documentation

[Denis Magda]

Pavel,

There will be a single SQL related page in Java, .NET and C++ docs that will 
refer to these new docs. Plus SQL will appear in the header of every readme.io 
domain.

I’ll take care of this when we will be releasing all 2.3 docs. Here is a ticket 
to track all the things to be done with SQL:
https://issues.apache.org/jira/browse/IGNITE-6685

—
Denis

> On Oct 20, 2017, at 1:51 AM, Pavel Tupitsyn  wrote:
> 
>> that all the SQL related pages will be hidden
> 
> Denis, please make sure to update all references to these pages.
> It should be obvious from Java/.NET/C++ docs that SQL features are present
> and did not disappear from the docs.
> 
> Consider scenario:
> As a user, I go to apacheignite-net.readme.io 
>  and search for SQL and LINQ
> (in the search bar). Do I find anything?
> 
> Thanks,
> Pavel
> 
> On Fri, Oct 20, 2017 at 8:09 AM, Denis Magda  > wrote:
> 
>> On Thursday, October 19, 2017, Dmitriy Setrakyan 
>> wrote:
>> 
>>> Denis,
>>> 
>>> Awesome work and great contribution!
>>> 
>>> A minor comment. Does SELECT belong under DML?
>> 
>> 
>> Thanks for feedback!
>> 
>> It turned out that yes, SELECT belongs to DML. Personally, I deciphered ‘M’
>> as ‘modification’ before while in fact it stands for ‘manipulation’.
>> 
>> Some proof links:
>> https://en.m.wikipedia.org/wiki/Data_manipulation_language
>> http://www.h2database.com/html/grammar.html
>> 
>> Denis
>> 
>>> 
>>> D.
>>> 
>>> 
>>> On Thu, Oct 19, 2017 at 6:36 PM, Denis Magda >> > wrote:
>>> 
 Igniters,
 
 I’m glad to share that the new SQL doc is ready for proof read:
 https://apacheignite-sql.readme.io/docs 
 
 
 Main sections:
 - Overview - SQL capabilities outline and getting started guide.
 - SQL Reference - SQL itself with all the commands and operations.
 - Architecture - insights on how SQL engine works and some of its
>>> features.
 - JDBC
 - ODBC
 - Tools and Analytics - tools to work with Ignite as with SQL database.
 -  Java Dev Guide - Java specific features
 - .NET Dev Guide - .NET specific features
 - C++ Dev Guide - C++ specific features
 
 Note, that all the SQL related pages will be hidden (consider removed)
>> on
 Java, .NET and C++ readme.io  sites in 2.3. All the SQL 
 related
 capabilities have to be documented on this new specific doc.
 
 Here is we’re tracking minor documentation tasks to close before the
 release:
 https://issues.apache.org/jira/browse/IGNITE-6685 
 
 
 Many thanks to Sergey Puchnin for the help with SQL reference
 documentation!
 
 —
 Denis
 
 
> On Sep 14, 2017, at 5:00 AM, Serge Puchnin  
>>> >
 wrote:
> 
> Denis,
> Thanks a lot for the link.
> It's very helpful to split "function part" to more specific like
 'string',
> 'numeric', etc.
> 
> the main reason to separate "Java Developer" as an independent part
 because
> it's about a mix between Java and SQL code.
> It's about classes, methods, annotation, GC, etc.
> It doesn't fully belong to the SQL specification but IMHO should be
>> in
 SQL
> category.
> 
> BR,
> Serge
> 
> On Wed, 13 Sep 2017 at 22:39, Denis Magda  
>>> > wrote:
> 
>> Serge,
>> 
>> I like the proposed format. It reminds me the one chosen by MemSQL
>>> which
>> is crystal clear:
>> https://docs.memsql.com/sql-reference/v5.8/sql-reference-overview/ 
>> 
>> 
>> Not 100% sure about “Java Developer Guides” section. Let me
>>> contemplate
 a
>> bit and propose other solutions.
>> 
>> —
>> Denis
>> 
>> On Sep 13, 2017, at 3:41 AM, Serge Puchnin <
>> sergey.puch...@gmail.com 
>>> >
>> wrote:
>> 
>> I have done some reorganizing for the SQL documentation.
>> Thanks a lot for the review and proof read.
>> 
>> 
>> 
>> On Wed, 13 Sep 2017 at 01:22, Dmitriy Setrakyan <
>>> dsetrak...@apache.org  >
>> wrote:
>> 
>>> Thanks Sergey, I think we should add SQL Syntax section on the
>> left.
 Also,
>>> please let us know when we can proof read it. I would like to fix
>>> some
>>> phrasing on the page.
>>> 
>>> On Tue, Sep 12, 2017 at 8:26 AM, Serge Puchnin <
 sergey.puch...@gmail.com  >
>>> wrote:
>>> 
 I've 

[jira] [Created] (IGNITE-6694) Ability to turn BaselineTopology handling off

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-6694:
---

 Summary: Ability to turn BaselineTopology handling off
 Key: IGNITE-6694
 URL: https://issues.apache.org/jira/browse/IGNITE-6694
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Sergey Chugunov
 Fix For: 2.4


To support cluster upgrade/downgrade scenarios when only part of nodes supports 
BaselineTopology special setting to turn BLT handling off is needed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: IGNITE-6692 Select query on a client with unused field throws an exception.

[Nikita Amelchev]

I've attached reproducer to the issue [1].

1. https://issues.apache.org/jira/browse/IGNITE-6692

2017-10-20 16:05 GMT+03:00 Vladimir Ozerov :

> Hi Nikita,
>
> Appears to be a bug. Could you please file a ticket with reproducer?
>
> On Fri, Oct 20, 2017 at 3:56 PM, Nikita Amelchev 
> wrote:
>
> > Hello, Igniters.
> >
> > I found a bug when I execute next queries on the client:
> >
> > CREATE TABLE t1 (name VARCHAR(1), unused LONG, PRIMARY KEY(name));
> > INSERT INTO t1 (name) values ('A');
> > SELECT name FROM t1 ORDER BY name, unused;
> >
> > The latest query throws exception like "BinaryObjectException: Cannot
> find
> > schema for object with compact footer [typeId=-1289534525, schemaId=0]"
> >
> > Is it a bug? Does anybody fix it right now?
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >
>



-- 
Best wishes,
Amelchev Nikita

[jira] [Created] (IGNITE-6693) private method initBlockFor in BlockMatrixStorage works incorrect for small matricies

[Aleksey Zinoviev (JIRA)]

Aleksey Zinoviev created IGNITE-6693:


 Summary: private method initBlockFor in BlockMatrixStorage works 
incorrect for small matricies
 Key: IGNITE-6693
 URL: https://issues.apache.org/jira/browse/IGNITE-6693
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: ml
Reporter: Aleksey Zinoviev






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2898: Ignite 1.8.13.b1

[apopovgg]

GitHub user apopovgg opened a pull request:

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

Ignite 1.8.13.b1



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

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

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

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


commit 925ee11c2002729b1264148ee5db5700ded5a7b7
Author: Alexey Kuznetsov 
Date:   2017-04-04T09:06:01Z

Fixed typo.
(cherry picked from commit 3b84f34)

commit ce4b078c1c97cae4136c318ae38b27a50fe383cc
Author: Alexey Kuznetsov 
Date:   2017-04-04T09:14:56Z

master Updated version.
(cherry picked from commit 5469626)

commit ae435fb5474429e7ac76faadd680c19a4c657371
Author: Sergi Vladykin 
Date:   2017-04-02T12:35:04Z

ignite-2913 - SQL: EXISTS support added

commit b7ab27301b59bf93fc73b52fdf8e0bcf124fec1d
Author: Andrey V. Mashenkov 
Date:   2017-04-06T11:43:50Z

IGNITE-4832: Prevent service deployment on client by default when 
configuration is provided on startup. This closes #1748.

commit b214211eb3461746b6931c0623e086bb208e5dda
Author: Anton Vinogradov 
Date:   2017-04-06T12:00:12Z

IGNITE-4644 Value from IgniteQueue in atomic mode could be lost

commit 014161427fb603b6df7c8ecc3c0904f5df47a21d
Author: Denis Magda 
Date:   2017-02-14T01:33:32Z

IGNITE-4159: Kubernetes IP finder.
(cherry picked from commit 37c0a22)

commit 1db238402f11c67d2b28bfb7ff47955415f00c25
Author: Denis Magda 
Date:   2017-02-16T04:37:26Z

IGNITE-4159: fixing logging
(cherry picked from commit 06908d2)
(cherry picked from commit fa27ee3)

commit 5dfe16f7e91374008b9f6dfbb899364f5b2e1164
Author: Denis Magda 
Date:   2017-02-14T06:03:30Z

IGNITE-4159: using logger instead of system.out.println
(cherry picked from commit b9bf77c)

commit 6e596d1ef426b66abd866d011a8f5cf5c5c25124
Author: Andrey V. Mashenkov 
Date:   2017-04-06T11:43:50Z

IGNITE-4832: Prevent service deployment on client by default when 
configuration is provided on startup. This closes #1748.

(cherry picked from commit b7ab273)

commit 443ac9a7aa82af1359a03bcfc8f9212b108300e4
Author: Andrey V. Mashenkov 
Date:   2017-04-05T12:01:02Z

IGNITE-4917: Fixed failure when accessing BinaryObjectBuilder field value 
serialized with OptimizedMarshaller . This closes #1736.

commit 05f3c747921aed6838804d2f5f2c8d2bd7985337
Author: Andrey V. Mashenkov 
Date:   2017-04-05T12:01:02Z

IGNITE-4917: Fixed failure when accessing BinaryObjectBuilder field value 
serialized with OptimizedMarshaller . This closes #1736.

(cherry picked from commit 443ac9a)

commit 3be4e00373ec5a2b49788d70eb0aebccc3cb6ccf
Author: Alexander Fedotov 
Date:   2017-04-07T11:59:00Z

Merge branch ignite-1.6.5 into ignite-1.8.5-p1

commit d81548d3a4e384e1a9b4adacf1fb487444bbfd33
Author: Alexander Fedotov 
Date:   2017-04-07T12:33:08Z

Merge branch ignite-1.6.6-p1 into ignite-1.8.5-p1

commit 6954ff0c85f2f75507ee0bd306c879f490b4201a
Author: Alexander Fedotov 
Date:   2017-04-07T12:44:48Z

Merge branch ignite-1.6.12 into ignite-1.8.5-p1

commit 62dbba81c009170ff6243a28d3ef12fa75b96225
Author: Alexander Fedotov 
Date:   2017-04-07T12:46:11Z

Merge branch ignite-1.7.4-p1 into ignite-1.8.5-p1

commit 4fce28054bc325741f65035ae384f9b4b9c3fee8
Author: Alexander Fedotov 
Date:   2017-04-07T13:06:34Z

Merge branch ignite-1.8.4-p1 into ignite-1.8.5-p1

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java

commit 3d616799efb472227b3b313516e6b40729654631
Author: dkarachentsev 
Date:   2017-04-10T07:36:11Z

IGNITE-2466 - Use current NIO back pressure mechanism to limit received 
messages. Mark them process only when backups acknowledged.

(backport from 1.9.2)

(cherry picked from commit 220db882b466c03eadd148b3a19a0bf70d82d4a6)

commit 2a88a7a7581465ff0a6f8733550e6d42d7f71a6c
Author: dkarachentsev 
Date:   2017-04-10T07:54:37Z

IGNITE-4667 - Throw exception on starting client cache when indexed types 
cannot be loaded

commit ba6227be49c8a395a5632e9841a6acb65ae340b6
Author: dkarachentsev 
Date:   2017-04-10T08:40:17Z

IGNITE-2466 - Disable back-pressure for sender data nodes to avoid deadlock.

commit 

[GitHub] ignite pull request #2897: Ignite-1.8.13-b1

[apopovgg]

Github user apopovgg closed the pull request at:

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


---

[GitHub] ignite pull request #2897: Ignite-1.8.13-b1

[apopovgg]

GitHub user apopovgg opened a pull request:

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

Ignite-1.8.13-b1



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

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

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

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


commit 925ee11c2002729b1264148ee5db5700ded5a7b7
Author: Alexey Kuznetsov 
Date:   2017-04-04T09:06:01Z

Fixed typo.
(cherry picked from commit 3b84f34)

commit ce4b078c1c97cae4136c318ae38b27a50fe383cc
Author: Alexey Kuznetsov 
Date:   2017-04-04T09:14:56Z

master Updated version.
(cherry picked from commit 5469626)

commit ae435fb5474429e7ac76faadd680c19a4c657371
Author: Sergi Vladykin 
Date:   2017-04-02T12:35:04Z

ignite-2913 - SQL: EXISTS support added

commit b7ab27301b59bf93fc73b52fdf8e0bcf124fec1d
Author: Andrey V. Mashenkov 
Date:   2017-04-06T11:43:50Z

IGNITE-4832: Prevent service deployment on client by default when 
configuration is provided on startup. This closes #1748.

commit b214211eb3461746b6931c0623e086bb208e5dda
Author: Anton Vinogradov 
Date:   2017-04-06T12:00:12Z

IGNITE-4644 Value from IgniteQueue in atomic mode could be lost

commit 014161427fb603b6df7c8ecc3c0904f5df47a21d
Author: Denis Magda 
Date:   2017-02-14T01:33:32Z

IGNITE-4159: Kubernetes IP finder.
(cherry picked from commit 37c0a22)

commit 1db238402f11c67d2b28bfb7ff47955415f00c25
Author: Denis Magda 
Date:   2017-02-16T04:37:26Z

IGNITE-4159: fixing logging
(cherry picked from commit 06908d2)
(cherry picked from commit fa27ee3)

commit 5dfe16f7e91374008b9f6dfbb899364f5b2e1164
Author: Denis Magda 
Date:   2017-02-14T06:03:30Z

IGNITE-4159: using logger instead of system.out.println
(cherry picked from commit b9bf77c)

commit 6e596d1ef426b66abd866d011a8f5cf5c5c25124
Author: Andrey V. Mashenkov 
Date:   2017-04-06T11:43:50Z

IGNITE-4832: Prevent service deployment on client by default when 
configuration is provided on startup. This closes #1748.

(cherry picked from commit b7ab273)

commit 443ac9a7aa82af1359a03bcfc8f9212b108300e4
Author: Andrey V. Mashenkov 
Date:   2017-04-05T12:01:02Z

IGNITE-4917: Fixed failure when accessing BinaryObjectBuilder field value 
serialized with OptimizedMarshaller . This closes #1736.

commit 05f3c747921aed6838804d2f5f2c8d2bd7985337
Author: Andrey V. Mashenkov 
Date:   2017-04-05T12:01:02Z

IGNITE-4917: Fixed failure when accessing BinaryObjectBuilder field value 
serialized with OptimizedMarshaller . This closes #1736.

(cherry picked from commit 443ac9a)

commit 3be4e00373ec5a2b49788d70eb0aebccc3cb6ccf
Author: Alexander Fedotov 
Date:   2017-04-07T11:59:00Z

Merge branch ignite-1.6.5 into ignite-1.8.5-p1

commit d81548d3a4e384e1a9b4adacf1fb487444bbfd33
Author: Alexander Fedotov 
Date:   2017-04-07T12:33:08Z

Merge branch ignite-1.6.6-p1 into ignite-1.8.5-p1

commit 6954ff0c85f2f75507ee0bd306c879f490b4201a
Author: Alexander Fedotov 
Date:   2017-04-07T12:44:48Z

Merge branch ignite-1.6.12 into ignite-1.8.5-p1

commit 62dbba81c009170ff6243a28d3ef12fa75b96225
Author: Alexander Fedotov 
Date:   2017-04-07T12:46:11Z

Merge branch ignite-1.7.4-p1 into ignite-1.8.5-p1

commit 4fce28054bc325741f65035ae384f9b4b9c3fee8
Author: Alexander Fedotov 
Date:   2017-04-07T13:06:34Z

Merge branch ignite-1.8.4-p1 into ignite-1.8.5-p1

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java

commit 3d616799efb472227b3b313516e6b40729654631
Author: dkarachentsev 
Date:   2017-04-10T07:36:11Z

IGNITE-2466 - Use current NIO back pressure mechanism to limit received 
messages. Mark them process only when backups acknowledged.

(backport from 1.9.2)

(cherry picked from commit 220db882b466c03eadd148b3a19a0bf70d82d4a6)

commit 2a88a7a7581465ff0a6f8733550e6d42d7f71a6c
Author: dkarachentsev 
Date:   2017-04-10T07:54:37Z

IGNITE-4667 - Throw exception on starting client cache when indexed types 
cannot be loaded

commit ba6227be49c8a395a5632e9841a6acb65ae340b6
Author: dkarachentsev 
Date:   2017-04-10T08:40:17Z

IGNITE-2466 - Disable back-pressure for sender data nodes to avoid deadlock.

commit 

Re: IGNITE-6692 Select query on a client with unused field throws an exception.

[Vladimir Ozerov]

Hi Nikita,

Appears to be a bug. Could you please file a ticket with reproducer?

On Fri, Oct 20, 2017 at 3:56 PM, Nikita Amelchev 
wrote:

> Hello, Igniters.
>
> I found a bug when I execute next queries on the client:
>
> CREATE TABLE t1 (name VARCHAR(1), unused LONG, PRIMARY KEY(name));
> INSERT INTO t1 (name) values ('A');
> SELECT name FROM t1 ORDER BY name, unused;
>
> The latest query throws exception like "BinaryObjectException: Cannot find
> schema for object with compact footer [typeId=-1289534525, schemaId=0]"
>
> Is it a bug? Does anybody fix it right now?
>
>
> --
> Best wishes,
> Amelchev Nikita
>

IGNITE-6692 Select query on a client with unused field throws an exception.

[Nikita Amelchev]

Hello, Igniters.

I found a bug when I execute next queries on the client:

CREATE TABLE t1 (name VARCHAR(1), unused LONG, PRIMARY KEY(name));
INSERT INTO t1 (name) values ('A');
SELECT name FROM t1 ORDER BY name, unused;

The latest query throws exception like "BinaryObjectException: Cannot find
schema for object with compact footer [typeId=-1289534525, schemaId=0]"

Is it a bug? Does anybody fix it right now?


-- 
Best wishes,
Amelchev Nikita

[jira] [Created] (IGNITE-6692) Select query on a client with unused field throws an exception.

[Amelchev Nikita (JIRA)]

Amelchev Nikita created IGNITE-6692:
---

 Summary: Select query on a client with unused field throws an 
exception.
 Key: IGNITE-6692
 URL: https://issues.apache.org/jira/browse/IGNITE-6692
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Amelchev Nikita


Steps to reproduce:
1. Run one server, one client.
2. Execute next queries on a client:
3. Run select that throws an exception: 

Test is in attachment. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2896: IGNITE-6649: Add EvictionPolicy factory support i...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-6649: Add EvictionPolicy factory support in IgniteConfiguration.



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

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

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

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


commit 7bf47bfc6dad6efafb244a357f0687b35d44d1ee
Author: Andrey V. Mashenkov 
Date:   2017-10-17T16:32:11Z

Add eviction policy to cache configuration.

commit 7b5e23bc0212745944a4830d5ffacc67033c3884
Author: Andrey V. Mashenkov 
Date:   2017-10-17T16:32:21Z

WIP

commit 6a7118da4aece6783770d59364d162f792251d05
Author: Andrey V. Mashenkov 
Date:   2017-10-20T12:15:15Z

WIP.
Tests added.




---

[GitHub] ignite pull request #2895: Ignite-6649: Add EvictionPolicy factory support i...

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #2895: Ignite-6649: Add EvictionPolicy factory support i...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite-6649: Add EvictionPolicy factory support in IgniteConfiguration.



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

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

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

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


commit 7bf47bfc6dad6efafb244a357f0687b35d44d1ee
Author: Andrey V. Mashenkov 
Date:   2017-10-17T16:32:11Z

Add eviction policy to cache configuration.

commit 7b5e23bc0212745944a4830d5ffacc67033c3884
Author: Andrey V. Mashenkov 
Date:   2017-10-17T16:32:21Z

WIP

commit 6a7118da4aece6783770d59364d162f792251d05
Author: Andrey V. Mashenkov 
Date:   2017-10-20T12:15:15Z

WIP.
Tests added.




---

[jira] [Created] (IGNITE-6690) DiscoverySpi: Clientmode Ignite should not fail on handshake errors

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-6690:


 Summary: DiscoverySpi: Clientmode Ignite should not fail on 
handshake errors
 Key: IGNITE-6690
 URL: https://issues.apache.org/jira/browse/IGNITE-6690
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: general
Affects Versions: 2.2
Reporter: Alexey Popov
Assignee: Alexey Popov
 Fix For: 2.4


Ignite in Client mode should not fail on handshake unmarshalling errors. It 
should go to the next IP/port from ipFinder list

http://apache-ignite-developers.2346864.n4.nabble.com/DiscoverySpi-Handshake-unmarshalling-errors-at-Client-client-mode-td23467.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2894: Ignite-6669: CacheStoreSessionListener#onSessionS...

[sk0x50]

GitHub user sk0x50 opened a pull request:

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

Ignite-6669: CacheStoreSessionListener#onSessionStart() #onSessionEnd() 
methods are called by GridCacheStoreManagerAdapter even if a store operation 
should not be performed.

In the case of transactional cache, which is configured using 
```CacheStore``` and ```CacheJdbcStoreSessionListener```, every update triggers 
```CacheStoreSessionListener#onSessionStart()```, 
```CacheStoreSessionListener#onSessionEnd()``` that results in creating the 
connection to an underlying database, even if read-through and write-through 
modes are disabled.

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

$ git pull https://github.com/sk0x50/ignite ignite-6669

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

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


commit a4d72223200137fcf3a33003173b7af6b09d
Author: Slava Koptilin 
Date:   2017-10-19T17:04:38Z

ignite-6669: wip

commit 6e7aecbcecef85fb85835c95b866a9b9dc04e28e
Author: Slava Koptilin 
Date:   2017-10-20T11:55:04Z

ignite-6669: added test




---

[GitHub] ignite pull request #2891: IGNITE-6515 .NET: Enable persistence on per-cache...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-6689) SQL: Add data region option to CREATE TABLE

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6689:
---

 Summary: SQL: Add data region option to CREATE TABLE
 Key: IGNITE-6689
 URL: https://issues.apache.org/jira/browse/IGNITE-6689
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: sql
Affects Versions: 2.3
Reporter: Vladimir Ozerov
 Fix For: 2.4


Subj. We need to be able to create tables in different data regions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2893: IGNITE-6555 When a CacheStore with a @SpringResou...

[symbicator]

GitHub user symbicator opened a pull request:

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

IGNITE-6555 When a CacheStore with a @SpringResource annotated field …

…is configured Ignite fails to start via igniteSpringBean

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

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

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

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


commit 6d39c3cbab6b4c5a5eede7e0ba15aff3407d5805
Author: Alexander Fedotov 
Date:   2017-10-20T10:21:09Z

IGNITE-6555 When a CacheStore with a @SpringResource annotated field is 
configured Ignite fails to start via igniteSpringBean




---

Re: DiscoverySpi Handshake unmarshalling errors at Client (client mode)

[Yakov Zhdanov]

Alexey, I agree. Feel free to file a ticket and provide the fix. You should
suppress exceptions on handshake response unmarshall and continue to the
rest of IPs. Please make sure that exception trace is still logged if debug
level is enabled for logger.

--Yakov

2017-10-20 11:12 GMT+03:00 Alexey Popov :

> Hi Igniters,
>
> I am looking into Client DiscoverySpi procedure and see some differences in
> Client behavior when it trying to connect to servers.
> Case 1: If the Client can't connect (Connection refused) to some Server it
> goes to the next IP/port from the ipFinder list.
> Case 2: But if the client can't succesfully finish Discovery Handshake
> procedure with the Server it does not try to connect to other IPs. It just
> throws an TcpDiscoverySpi exception like this back to a user code
> "class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> marsh=JdkMarshaller [], reconCnt=10, maxAckTimeout=60,
> forceSrvMode=false, clientReconnectDisabled=false]"
>
> Case 2 can happen when IP/port was taken by non-Ignite server. For
> instance,
> it could be taken by misconfigured HTTP server and the Client just can't
> unmarshall the server HTTP response:
>
> Caused by: java.io.StreamCorruptedException: invalid stream header:
> 48545450
> at java.io.ObjectInputStream.readStreamHeader(
> ObjectInputStream.java:857)
> at java.io.ObjectInputStream.(ObjectInputStream.java:349)
> at
> org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.(
> JdkMarshallerObjectInputStream.java:39)
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(
> JdkMarshaller.java:119)
>
> So, I would like to change the client behavior in Case 2. It should handle
> Discovery Handshake unmarshalling error in the same way it does with
> "Connection refused" errors. It should try to connect to other servers.
>
> Your thoughts?
>
> Thanks,
> Alexey
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[GitHub] ignite pull request #2892: Ignite-2.1.6.b3

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite-2.1.6.b3



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

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

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

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


commit 96d86acdfe1a251758c6915b473ceb20514cbbad
Author: sboikov 
Date:   2017-08-21T13:19:18Z

Merge remote-tracking branch 'community/ignite-2.1.4' into ignite-2.1.4

commit e9f729fcb9ba7b555aed246a834e385ce2c88795
Author: Alexey Goncharuk 
Date:   2017-08-21T10:49:22Z

ignite-5872 Replace standard java maps for partition counters with more 
effective data structures

(cherry picked from commit 918c409)

commit 8e672d4a83cb20136d375818505cacccf6c9b4fd
Author: sboikov 
Date:   2017-08-21T13:39:29Z

Changed ignite version.

commit fd5d83c44624baea9466c591f119195cb092df4c
Author: Alexey Kuznetsov 
Date:   2017-08-21T15:06:36Z

IGNITE-6104 Fixed target.
(cherry picked from commit 8775d2c)

commit cca9117c805d144ff451694e7324720f8d466d94
Author: sboikov 
Date:   2017-08-21T15:39:12Z

ignite-5872 Fixed backward compatibility

commit dc9b2660723b325e1d07991cd0936ee27f624a81
Author: sboikov 
Date:   2017-08-21T15:39:36Z

Merge remote-tracking branch 'community/ignite-2.1.4' into ignite-2.1.4

commit 1072654c8762113bc49a658f2898475381b47832
Author: Sergey Chugunov 
Date:   2017-08-21T17:05:05Z

IGNITE-6052 class rename was reverted

commit cf97f3dd903549d3b5968ceb5ca9eda29ef521cf
Author: Dmitriy Govorukhin 
Date:   2017-08-21T17:04:04Z

ignite-6035 Clear indexes on cache clear/destroy

Signed-off-by: Andrey Gura 

commit 47b84ec62fb988faad438bdfde4ee48165a4065f
Author: Andrey Gura 
Date:   2017-08-21T17:36:56Z

Visor compilation issues are fixed.

commit 6e0fd7222e64b3a5e05204b300b62f60e3142e40
Author: Ilya Lantukh 
Date:   2017-08-21T18:12:41Z

ignite-gg-12639 Fill factor metric is not working with enabled persistence

Signed-off-by: Andrey Gura 

commit bbafa1e946121b7143101d4060effc48ed74a0b3
Author: Alexey Kuznetsov 
Date:   2017-08-22T03:59:15Z

IGNITE-6136 Web Console: implemented universal version check.
(cherry picked from commit 1a42e78)

commit 2a2e8407aaa99a56f79a861fc1e201dd183eea11
Author: vsisko 
Date:   2017-08-22T04:08:21Z

IGNITE-6131 Visor Cmd: Fixed "cache -a" command output cache entries count.
(cherry picked from commit 1f5054a)

commit db64729fc9ebb0217f06b0cf9d5e53ab8d657510
Author: sboikov 
Date:   2017-08-22T08:29:32Z

ignite-6124 Fixed NPE in GridDhtPartitionsExchangeFuture.topologyVersion 
after future cleanup.

(cherry picked from commit 2c9057a)

commit 5b7724714264c14cc10f4b25abc9234387224e4b
Author: Ilya Lantukh 
Date:   2017-08-22T08:50:35Z

Fixed javadoc format.

commit 785a85eb0155444b3eef48cf373a990dc4c8c6dd
Author: sboikov 
Date:   2017-08-22T09:24:03Z

ignite-5872 GridDhtPartitionsSingleMessage.partitionUpdateCounters should 
not return null.

commit 6b506e774c59b64fc6254ea151699c852620a408
Author: sboikov 
Date:   2017-08-22T09:24:21Z

Merge remote-tracking branch 'community/ignite-2.1.4' into ignite-2.1.4

commit 160d9b7c707efc359b4014aa1a481dc0fbbf596f
Author: Ilya Lantukh 
Date:   2017-08-22T11:10:10Z

Fixed flaky test.

commit 9ed4b72044ba1b2c105761b431625736166af7e7
Author: Alexey Goncharuk 
Date:   2017-08-01T09:25:25Z

master - Fixed visor compilation after merge

commit 16b819a6131c95a30d8dfaefbac6f6593826258b
Author: Ilya Lantukh 
Date:   2017-08-22T13:40:02Z

Increased test timeout.

commit 9ab49d4a743c42b4a2f645b8af7611922629c9a3
Author: oleg-ostanin 
Date:   2017-08-22T13:39:31Z

IGNITE-6155 added new jvm flag for printing gc date stamps

(cherry picked from commit 03211d2)

commit e780c6b98b5a09cff44ec5d2fa1fd30275ffc35f
Author: Ilya Lantukh 
Date:   2017-08-22T14:10:07Z

Fixed test to work with new update counter maps.

commit db6add1d2ee17381b810cff3ff978eef4cef51b0
Author: Ilya Lantukh 
Date:   2017-08-22T14:20:07Z

Removed explicit fail().

commit bc1cc99eab9641753925ef2552ba29831640e9e1
Author: Dmitriy Govorukhin 
Date:   

[jira] [Created] (IGNITE-6688) ignite.destroyCache method hangs the cluster

[Ender Ekici (JIRA)]

Ender Ekici created IGNITE-6688:
---

 Summary: ignite.destroyCache method hangs the cluster
 Key: IGNITE-6688
 URL: https://issues.apache.org/jira/browse/IGNITE-6688
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Affects Versions: 2.1
Reporter: Ender Ekici


I've posted Apache Ignite Users but couldn't get an answer. 
[Thread|http://apache-ignite-users.70518.x6.nabble.com/ignite-destroyCache-method-hangs-the-cluster-tt16850.html]

Hi,
We have a test machine which has 8 cores with 32Gb ram.
On ignite there is only one cache which has 10M records (db size 7Gb~ ignite 
cache size 14Gb~)
We reload this cache with a cron scheduler.(Every night)

For example:
cacheName: products (alias)
realCacheName: products+oldTimestamp

-cron triggered.
-create cache with name “products+newTimestamp”
-load data from db to cache
-when loading finishes, we map the products cache to “products+newTimestamp” 
and later(after 1 min) destroy the old cache;

While we measuring the cache.get() times with only one client we encountered 
4.5sec delay while ignite.destroyCache(realOldCacheName) operation.

Example Reproducer Code:
[Github|https://github.com/enderekici/ignitetest.git]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

IGNITE-6135 java.sql.Date is serialized using OptimizedMarshaller

[Nikita Amelchev]

Hello, Pavel, Igor, Igniters.

I have implemented javax.sql.Date type for a binary protocol [1,2].
According to TC tests [3] we need to add support for sql.Date in CPP and
ODBC modules. Other tests look good.

Please, review.

[1] https://issues.apache.org/jira/browse/IGNITE-6135
[2] https://reviews.ignite.apache.org/ignite/review/IGNT-CR-367
[3]
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2837%2Fhead



-- 
Best wishes,
Amelchev Nikita

IGNITE-6666 BinaryObjectImpl.writeFieldByOrder method does not support TIME

[Nikita Amelchev]

Hello, Igniters!

I found that the BinaryObjectImpl.writeFieldByOrder method does not support
the TIME type [1]. I wrote test and fixed it [2]. TC tests look good [3].

Please, review.

[1] https://issues.apache.org/jira/browse/IGNITE-
[2] https://github.com/apache/ignite/pull/2878/files
[3]
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2878%2Fhead



-- 
Best wishes,
Amelchev Nikita

Re: sql documentation

[Pavel Tupitsyn]

> that all the SQL related pages will be hidden

Denis, please make sure to update all references to these pages.
It should be obvious from Java/.NET/C++ docs that SQL features are present
and did not disappear from the docs.

Consider scenario:
As a user, I go to apacheignite-net.readme.io and search for SQL and LINQ
(in the search bar). Do I find anything?

Thanks,
Pavel

On Fri, Oct 20, 2017 at 8:09 AM, Denis Magda  wrote:

> On Thursday, October 19, 2017, Dmitriy Setrakyan 
> wrote:
>
> > Denis,
> >
> > Awesome work and great contribution!
> >
> > A minor comment. Does SELECT belong under DML?
>
>
> Thanks for feedback!
>
> It turned out that yes, SELECT belongs to DML. Personally, I deciphered ‘M’
> as ‘modification’ before while in fact it stands for ‘manipulation’.
>
> Some proof links:
> https://en.m.wikipedia.org/wiki/Data_manipulation_language
> http://www.h2database.com/html/grammar.html
>
> Denis
>
> >
> > D.
> >
> >
> > On Thu, Oct 19, 2017 at 6:36 PM, Denis Magda  > > wrote:
> >
> > > Igniters,
> > >
> > > I’m glad to share that the new SQL doc is ready for proof read:
> > > https://apacheignite-sql.readme.io/docs
> > >
> > > Main sections:
> > > - Overview - SQL capabilities outline and getting started guide.
> > > - SQL Reference - SQL itself with all the commands and operations.
> > > - Architecture - insights on how SQL engine works and some of its
> > features.
> > > - JDBC
> > > - ODBC
> > > - Tools and Analytics - tools to work with Ignite as with SQL database.
> > > -  Java Dev Guide - Java specific features
> > > - .NET Dev Guide - .NET specific features
> > > - C++ Dev Guide - C++ specific features
> > >
> > > Note, that all the SQL related pages will be hidden (consider removed)
> on
> > > Java, .NET and C++ readme.io sites in 2.3. All the SQL related
> > > capabilities have to be documented on this new specific doc.
> > >
> > > Here is we’re tracking minor documentation tasks to close before the
> > > release:
> > > https://issues.apache.org/jira/browse/IGNITE-6685
> > >
> > > Many thanks to Sergey Puchnin for the help with SQL reference
> > > documentation!
> > >
> > > —
> > > Denis
> > >
> > >
> > > > On Sep 14, 2017, at 5:00 AM, Serge Puchnin  > >
> > > wrote:
> > > >
> > > > Denis,
> > > > Thanks a lot for the link.
> > > > It's very helpful to split "function part" to more specific like
> > > 'string',
> > > > 'numeric', etc.
> > > >
> > > > the main reason to separate "Java Developer" as an independent part
> > > because
> > > > it's about a mix between Java and SQL code.
> > > > It's about classes, methods, annotation, GC, etc.
> > > > It doesn't fully belong to the SQL specification but IMHO should be
> in
> > > SQL
> > > > category.
> > > >
> > > > BR,
> > > > Serge
> > > >
> > > > On Wed, 13 Sep 2017 at 22:39, Denis Magda  > > wrote:
> > > >
> > > >> Serge,
> > > >>
> > > >> I like the proposed format. It reminds me the one chosen by MemSQL
> > which
> > > >> is crystal clear:
> > > >> https://docs.memsql.com/sql-reference/v5.8/sql-reference-overview/
> > > >>
> > > >> Not 100% sure about “Java Developer Guides” section. Let me
> > contemplate
> > > a
> > > >> bit and propose other solutions.
> > > >>
> > > >> —
> > > >> Denis
> > > >>
> > > >> On Sep 13, 2017, at 3:41 AM, Serge Puchnin <
> sergey.puch...@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >> I have done some reorganizing for the SQL documentation.
> > > >> Thanks a lot for the review and proof read.
> > > >>
> > > >>
> > > >>
> > > >> On Wed, 13 Sep 2017 at 01:22, Dmitriy Setrakyan <
> > dsetrak...@apache.org >
> > > >> wrote:
> > > >>
> > > >>> Thanks Sergey, I think we should add SQL Syntax section on the
> left.
> > > Also,
> > > >>> please let us know when we can proof read it. I would like to fix
> > some
> > > >>> phrasing on the page.
> > > >>>
> > > >>> On Tue, Sep 12, 2017 at 8:26 AM, Serge Puchnin <
> > > sergey.puch...@gmail.com >
> > > >>> wrote:
> > > >>>
> > >  I've added a page for SQL language, create index statement and
> Upper
> > >  function as an example for the new format:
> > > 
> > >  https://apacheignite-sql.readme.io/v2.1/docs/create-index
> > > 
> > > 
> > > 
> > >  For me, it'd be OK to add a separate page for each SQL statement.
> > > 
> > > 
> > >  BR,
> > > 
> > >  Serge
> > > 
> > >  On Sat, 9 Sep 2017 at 02:19, Denis Magda  > > wrote:
> > > 
> > > > Please check you inbox.
> > > >
> > > > —
> > > > Denis
> > > >
> > > >> On Sep 8, 2017, at 3:38 PM, Dmitriy Setrakyan <
> > > >>> dsetrak...@apache.org >
> > > > wrote:
> > > >>
> > > >> Denis,
> > > >>
> > > >> Can you please add me as an admin to that site?
> > > >>
> > > >> 

[GitHub] ignite pull request #2891: IGNITE-6515 .NET: Enable persistence on per-cache...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

 IGNITE-6515 .NET: Enable persistence on per-cache basis



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

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

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

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


commit ec41370c4da65c01e9b7c584e0706c40e4171b35
Author: Ivan Rakov 
Date:   2017-10-20T07:29:57Z

IGNITE-6030 Allow enabling persistence per data region

commit 6afea2c9f54379c1801d2b0023a7ecb86ab1526c
Author: Pavel Tupitsyn 
Date:   2017-10-20T08:40:56Z

IGNITE-6515 .NET: Enable persistence on per-cache basis




---

DiscoverySpi Handshake unmarshalling errors at Client (client mode)

[Alexey Popov]

Hi Igniters, 

I am looking into Client DiscoverySpi procedure and see some differences in
Client behavior when it trying to connect to servers.
Case 1: If the Client can't connect (Connection refused) to some Server it
goes to the next IP/port from the ipFinder list.
Case 2: But if the client can't succesfully finish Discovery Handshake
procedure with the Server it does not try to connect to other IPs. It just
throws an TcpDiscoverySpi exception like this back to a user code
"class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
marsh=JdkMarshaller [], reconCnt=10, maxAckTimeout=60,
forceSrvMode=false, clientReconnectDisabled=false]"

Case 2 can happen when IP/port was taken by non-Ignite server. For instance,
it could be taken by misconfigured HTTP server and the Client just can't
unmarshall the server HTTP response:

Caused by: java.io.StreamCorruptedException: invalid stream header: 48545450
at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:857)
at java.io.ObjectInputStream.(ObjectInputStream.java:349)
at
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.(JdkMarshallerObjectInputStream.java:39)
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:119)

So, I would like to change the client behavior in Case 2. It should handle
Discovery Handshake unmarshalling error in the same way it does with
"Connection refused" errors. It should try to connect to other servers.

Your thoughts?

Thanks,
Alexey




--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #2890: IGNITE-6519 Race in SplitAwareTopologyValidator o...

[akuramshingg]

GitHub user akuramshingg opened a pull request:

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

IGNITE-6519 Race in SplitAwareTopologyValidator on activator and server 
node join

Using a bigger topology
TestRecordingCommunicationSpi fix (future timeout instead of 
ClusterTopologyException)

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

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

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

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


commit 3255bab8264afea3ee29e0c4ed422feb9aa35302
Author: Alexandr Kuramshin 
Date:   2017-10-20T05:28:56Z

IGNITE-6519 Race in SplitAwareTopologyValidator on activator and server 
node join

Using a bigger topology
TestRecordingCommunicationSpi fix (future timeout instead of 
ClusterTopologyException)




---