Re: Marking and tracking usability issues

[Denis Magda]

Got required permissions from INFRA and eventually now the filter is visible to 
everyone from Ignite community:
https://issues.apache.org/jira/issues/?filter=12341720

—
Denis

> On Aug 18, 2017, at 2:31 PM, Dmitriy Setrakyan  wrote:
> 
> I don't see any list on the left. It takes me directly to the ticket.
> 
> On Fri, Aug 18, 2017 at 1:57 PM, Denis Magda  wrote:
> 
>> You should see the list to the left. IGNITE-6116 will be shown as the
>> first one.
>> 
>> —
>> Denis
>> 
>>> On Aug 18, 2017, at 1:52 PM, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> This link took me to this ticket directly:
>>> https://issues.apache.org/jira/browse/IGNITE-6116
>>> 
>>> On Fri, Aug 18, 2017 at 1:42 PM, Denis Magda  wrote:
>>> 
 Can not share the filter. That’s the query string to see the tickets:
 
 https://issues.apache.org/jira/browse/IGNITE-6116?jql=
 project%20%3D%20IGNITE%20AND%20status%20in%20(Open%2C%20%
 22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%
 20labels%20in%20(usability)
 
 —
 Denis
 
> On Aug 18, 2017, at 1:26 PM, Denis Magda  wrote:
> 
> Igniters,
> 
> Here and there we see usability issues bubbling up in the discussion on
 @dev and @user list, Stackoverflow, etc. Looking at them I would say
>> that
 the majority is pretty straightforward to fix bringing the overall
 usability to a better level.
> 
> Let’s keep using “usability” label for all of the features of this
>> kind.
 All of them will be added to this filter that I suggest to add to your
 panel:
> https://issues.apache.org/jira/issues/?filter=12341720 <
 https://issues.apache.org/jira/issues/?filter=12341720>
> 
> Most of them are easy to implement, so if you’re interested go ahead
>> and
 assign any of them on yourself.
> 
> —
> Denis
 
 
>> 
>> 

Durable memory and Ignite Persistence performance tips

[Denis Magda]

Igniters,

I’ve created two sections where we can aggregate all the performance tips for 
the memory and persistence:
https://apacheignite.readme.io/docs/performance-tips#tune-ignite-native-persistence
https://apacheignite.readme.io/docs/performance-tips#section-tune-durable-memory

Please update them once you have relevant suggestions to share with our users.

—
Denis

Re: Default page size must be changed to 4k. Should it be backwards compatible?

[Denis Magda]

Added Ignite Persistence related section to the “Performance Tips” docs and 
mentioned this suggestion there:
https://apacheignite.readme.io/docs/performance-tips#tune-ignite-native-persistence

—
Denis

> On Aug 17, 2017, at 6:18 PM, Dmitriy Setrakyan  wrote:
> 
> On Tue, Aug 15, 2017 at 10:09 PM, Serge Puchnin 
> wrote:
> 
>> #1 option looks more predictable. But it's possible to add a message "for
>> better IO performance please migrate to 4K-pages".
>> 
> 
> Agree. Can we update the ticket to make sure that this suggestion is
> printed out?
> 
> 
>> BR,
>> Serge
>> 
>> 
>> On Wed, 16 Aug 2017 at 03:46, Dmitriy Setrakyan 
>> wrote:
>> 
>>> I like #1 if possible. Of course, if the LFS is empty, then the new
>> default
>>> should be 4k.
>>> 
>>> On Tue, Aug 15, 2017 at 12:01 PM, Ivan Rakov 
>>> wrote:
>>> 
 Guys,
 
 We have benchmarked how checkpoint write speed on SSD disk depends on
 various parameters. It became absolutely obvious that using 4K pages in
 durable memory instead of 2K brings considerable, significant
>> speed-up. I
 think, we must set 4K as default page size.
 Ticket with detailed explanation: https://issues.apache.org/jira
 /browse/IGNITE-5884
 Spoiler: it depends on write order and alignment, but writing 4K is at
 least *3x faster* than writing 2K when other parameters are the same.
 
 The question is backwards compatibility. If pageSize is not explicitly
>>> set
 in user configuration, attempt to start "4k default" Ignite node from
>> "2k
 default" LFS files will fail with exception:
 
 class org.apache.ignite.IgniteCheckedException: Failed to verify store
> file (invalid page size) [expectedPageSize=4096, filePageSize=2048]
>at org.apache.ignite.internal.processors.cache.persistence.file
> .FilePageStore.checkFile(FilePageStore.java:206)
>at org.apache.ignite.internal.processors.cache.persistence.file
> .FilePageStore.init(FilePageStore.java:416)
>at org.apache.ignite.internal.processors.cache.persistence.file
> .FilePageStore.read(FilePageStore.java:315)
>at org.apache.ignite.internal.processors.cache.persistence.file
> .FilePageStoreManager.read(FilePageStoreManager.java:287)
>at org.apache.ignite.internal.processors.cache.persistence.file
> .FilePageStoreManager.read(FilePageStoreManager.java:272)
>at org.apache.ignite.internal.processors.cache.persistence.page
> mem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:569)
>at org.apache.ignite.internal.processors.cache.persistence.page
> mem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:487)
>at org.apache.ignite.internal.processors.cache.persistence.Grid
> CacheOffheapManager.getOrAllocateCacheMetas(GridCacheOffheap
> Manager.java:515)
>at org.apache.ignite.internal.processors.cache.persistence.Grid
> CacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:
>> 86)
>at org.apache.ignite.internal.processors.cache.IgniteCacheOffhe
> apManagerImpl.start(IgniteCacheOffheapManagerImpl.java:139)
>at org.apache.ignite.internal.processors.cache.CacheGroupContex
> t.start(CacheGroupContext.java:868)
> 
 
 I think, we have two options here:
 
 1) Obvious and safe - provide silent backwards compatibility. We can
 implement a task which will find any LFS file, check its pageSize and
>> use
 it as default.
 2) Less user-friendly, but in my opinion still better option - crash
>>> node,
 but make error message more informative. We'll let user know that
>> default
 pageSize was changed to 4k due to discovered performance boost on most
 UNIX-based enviroments with SSD (which is for sure most popular
>>> enviroment
 among users), and recommend user to migrate to 4K-page LFS. If user
>> still
 wants to work with 2k pages, he can always set it explicitly in
 MemoryConfiguration and start node.
 
 Thoughts?
 
 --
 Best Regards,
 Ivan Rakov
 
 
>>> 
>> 

Re: Marking and tracking usability issues

[Dmitriy Setrakyan]

I don't see any list on the left. It takes me directly to the ticket.

On Fri, Aug 18, 2017 at 1:57 PM, Denis Magda  wrote:

> You should see the list to the left. IGNITE-6116 will be shown as the
> first one.
>
> —
> Denis
>
> > On Aug 18, 2017, at 1:52 PM, Dmitriy Setrakyan 
> wrote:
> >
> > This link took me to this ticket directly:
> > https://issues.apache.org/jira/browse/IGNITE-6116
> >
> > On Fri, Aug 18, 2017 at 1:42 PM, Denis Magda  wrote:
> >
> >> Can not share the filter. That’s the query string to see the tickets:
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-6116?jql=
> >> project%20%3D%20IGNITE%20AND%20status%20in%20(Open%2C%20%
> >> 22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%
> >> 20labels%20in%20(usability)
> >>
> >> —
> >> Denis
> >>
> >>> On Aug 18, 2017, at 1:26 PM, Denis Magda  wrote:
> >>>
> >>> Igniters,
> >>>
> >>> Here and there we see usability issues bubbling up in the discussion on
> >> @dev and @user list, Stackoverflow, etc. Looking at them I would say
> that
> >> the majority is pretty straightforward to fix bringing the overall
> >> usability to a better level.
> >>>
> >>> Let’s keep using “usability” label for all of the features of this
> kind.
> >> All of them will be added to this filter that I suggest to add to your
> >> panel:
> >>> https://issues.apache.org/jira/issues/?filter=12341720 <
> >> https://issues.apache.org/jira/issues/?filter=12341720>
> >>>
> >>> Most of them are easy to implement, so if you’re interested go ahead
> and
> >> assign any of them on yourself.
> >>>
> >>> —
> >>> Denis
> >>
> >>
>
>

Re: Marking and tracking usability issues

[Denis Magda]

You should see the list to the left. IGNITE-6116 will be shown as the first one.

—
Denis 

> On Aug 18, 2017, at 1:52 PM, Dmitriy Setrakyan  wrote:
> 
> This link took me to this ticket directly:
> https://issues.apache.org/jira/browse/IGNITE-6116
> 
> On Fri, Aug 18, 2017 at 1:42 PM, Denis Magda  wrote:
> 
>> Can not share the filter. That’s the query string to see the tickets:
>> 
>> https://issues.apache.org/jira/browse/IGNITE-6116?jql=
>> project%20%3D%20IGNITE%20AND%20status%20in%20(Open%2C%20%
>> 22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%
>> 20labels%20in%20(usability)
>> 
>> —
>> Denis
>> 
>>> On Aug 18, 2017, at 1:26 PM, Denis Magda  wrote:
>>> 
>>> Igniters,
>>> 
>>> Here and there we see usability issues bubbling up in the discussion on
>> @dev and @user list, Stackoverflow, etc. Looking at them I would say that
>> the majority is pretty straightforward to fix bringing the overall
>> usability to a better level.
>>> 
>>> Let’s keep using “usability” label for all of the features of this kind.
>> All of them will be added to this filter that I suggest to add to your
>> panel:
>>> https://issues.apache.org/jira/issues/?filter=12341720 <
>> https://issues.apache.org/jira/issues/?filter=12341720>
>>> 
>>> Most of them are easy to implement, so if you’re interested go ahead and
>> assign any of them on yourself.
>>> 
>>> —
>>> Denis
>> 
>> 

Re: Marking and tracking usability issues

[Dmitriy Setrakyan]

This link took me to this ticket directly:
https://issues.apache.org/jira/browse/IGNITE-6116

On Fri, Aug 18, 2017 at 1:42 PM, Denis Magda  wrote:

> Can not share the filter. That’s the query string to see the tickets:
>
> https://issues.apache.org/jira/browse/IGNITE-6116?jql=
> project%20%3D%20IGNITE%20AND%20status%20in%20(Open%2C%20%
> 22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%
> 20labels%20in%20(usability)
>
> —
> Denis
>
> > On Aug 18, 2017, at 1:26 PM, Denis Magda  wrote:
> >
> > Igniters,
> >
> > Here and there we see usability issues bubbling up in the discussion on
> @dev and @user list, Stackoverflow, etc. Looking at them I would say that
> the majority is pretty straightforward to fix bringing the overall
> usability to a better level.
> >
> > Let’s keep using “usability” label for all of the features of this kind.
> All of them will be added to this filter that I suggest to add to your
> panel:
> > https://issues.apache.org/jira/issues/?filter=12341720 <
> https://issues.apache.org/jira/issues/?filter=12341720>
> >
> > Most of them are easy to implement, so if you’re interested go ahead and
> assign any of them on yourself.
> >
> > —
> > Denis
>
>

Re: Marking and tracking usability issues

[Denis Magda]

Can not share the filter. That’s the query string to see the tickets:

https://issues.apache.org/jira/browse/IGNITE-6116?jql=project%20%3D%20IGNITE%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20labels%20in%20(usability)

—
Denis

> On Aug 18, 2017, at 1:26 PM, Denis Magda  wrote:
> 
> Igniters,
> 
> Here and there we see usability issues bubbling up in the discussion on @dev 
> and @user list, Stackoverflow, etc. Looking at them I would say that the 
> majority is pretty straightforward to fix bringing the overall usability to a 
> better level.
> 
> Let’s keep using “usability” label for all of the features of this kind. All 
> of them will be added to this filter that I suggest to add to your panel:
> https://issues.apache.org/jira/issues/?filter=12341720 
> 
> 
> Most of them are easy to implement, so if you’re interested go ahead and 
> assign any of them on yourself.
> 
> —
> Denis

Marking and tracking usability issues

[Denis Magda]

Igniters,

Here and there we see usability issues bubbling up in the discussion on @dev 
and @user list, Stackoverflow, etc. Looking at them I would say that the 
majority is pretty straightforward to fix bringing the overall usability to a 
better level.

Let’s keep using “usability” label for all of the features of this kind. All of 
them will be added to this filter that I suggest to add to your panel:
https://issues.apache.org/jira/issues/?filter=12341720 


Most of them are easy to implement, so if you’re interested go ahead and assign 
any of them on yourself.

—
Denis

[jira] [Created] (IGNITE-6116) Easy way to enable metrics for default memory region

[Denis Magda (JIRA)]

Denis Magda created IGNITE-6116:
---

 Summary: Easy way to enable metrics for default memory region
 Key: IGNITE-6116
 URL: https://issues.apache.org/jira/browse/IGNITE-6116
 Project: Ignite
  Issue Type: Improvement
Reporter: Denis Magda


Presently it's a bit challenging to enable memory metrics for the default 
memory region unless you define a new one. Add the following two methods to 
{{MemoryConfiguration}} to address the issue.

{code}
MemoryConfiguration.setDefaultMemoryPolicyMetricsEnabled(boolean)
boolean MemoryConfiguration.isDefaultMemoryPolicyMetricsEnabled()
{code}

Discussion on @dev list: 
http://apache-ignite-developers.2346864.n4.nabble.com/Enabling-memory-and-persistence-metrics-td19582.html



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

Re: Ignite2.1: Page eviction is not compatible with persistence when startup

[Denis Magda]

Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-6115 


If anybody is interested go ahead and take over it.

—
Denis

> On Aug 17, 2017, at 5:16 PM, Dmitriy Setrakyan  wrote:
> 
> Agree. If we remove the exception though, we need to make sure to print out
> the warning that the eviction policy will be ignored with Ignite native
> persistence enabled.
> 
> On Thu, Aug 17, 2017 at 1:35 PM, Denis Magda  wrote:
> 
>> Dmitriy,
>> 
 Developers,
 
 Let me bring this to your attention. Why do we throw an exception if the
 user has both an eviction policy and the Ignite persistence configured?
>> Why
 don’t we simply ignore the eviction policy printing a warning and
>> proceed
 with the node startup?
 
>>> 
>>> Denis, any reason one approach is better than another?
>> 
>> The user doesn’t need to struggle with a bout of failures once he enable
>> the Ignite persistence. This specific user had the memory policy configured
>> before and once he enabled the disk he got extra exception he has to deal
>> with. It shouldn’t work this way.
>> 
>> In any case, the exception’s message doesn’t explain how to overcome the
>> issue and has to be improved:
>> 
>> Caused by: class org.apache.ignite.IgniteCheckedException: Page eviction
>> is
>> not compatible with persistence: 1G_Region
>> 
>> —
>> Denis

[jira] [Created] (IGNITE-6115) Ignore page eviction mode if Ignite persistence is enabled

[Denis Magda (JIRA)]

Denis Magda created IGNITE-6115:
---

 Summary: Ignore page eviction mode if Ignite persistence is enabled
 Key: IGNITE-6115
 URL: https://issues.apache.org/jira/browse/IGNITE-6115
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.1
Reporter: Denis Magda
 Fix For: 2.2


If a page eviction mode is defined for a memory region and the Ignite Native 
Persistence is enabled then the following exception is thrown on a node startup:
{code}
class org.apache.ignite.IgniteCheckedException: Failed to start processor:
GridProcessorAdapter []
   at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1791)
   at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:929)
   at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1896)
   at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1648)
   at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1076)
   at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:994)
   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:880)
   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:779)
   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:649)
   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:618)
   at org.apache.ignite.Ignition.start(Ignition.java:347)
   at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Page eviction is
not compatible with persistence: 1G_Region
   at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkPolicyEvictionProperties(GridCacheDatabaseSharedManager.java:660)
   at
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager.validateConfiguration(IgniteCacheDatabaseSharedManager.java:336)
   at
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:109)
   at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.start0(GridCacheDatabaseSharedManager.java:358)
   at
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:61)
   at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:696)
   at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1788)
{code}

That case has to be processed differently:
* Ignore the page eviction mode and let the node to proceed with the startup.
* Print a warning "Page eviction mode for {name} memory region is ignored 
because Ignite Native Persistence is enabled".

Discussion on the dev list: 
http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-Ignite2-1-Page-eviction-is-not-compatible-with-persistence-when-startup-td20934.html



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

Re: SQL Getting Started Guide

[Prachi Garg]

Hi Igor,

The getting started guide is missing an example oh how to create a Person
table (under ODBC tab).
https://apacheignite.readme.io/docs/getting-started-sql#section-create-tables

I am trying to put one on the website. Does the following look ok?

// Create table based on PARTITIONED template with one backup
SQLCHAR query[] = "CREATE TABLE Person ( "
"id LONG, name VARCHAR, city_id LONG "
"PRIMARY KEY (id, city_id)) "
"WITH \"backups=1, affinityKey=city_id\"";
SQLSMALLINT queryLen = static_cast(sizeof(query));

SQLRETURN ret = SQLExecDirect(stmt, query, queryLen);


On Fri, Aug 18, 2017 at 12:09 PM, Denis Magda  wrote:

> Igor, thanks a lot. Appreciate this!
>
> —
> Denis
>
> > On Aug 18, 2017, at 8:56 AM, Igor Sapego  wrote:
> >
> > I've checked ODBC snippets and fixed all found issues.
> >
> > Best Regards,
> > Igor
> >
> > On Thu, Aug 17, 2017 at 11:16 PM, Denis Magda  wrote:
> >
> >> Igor,
> >>
> >> Would you mind helping us to test the snippets? I do believe it will
> take
> >> you a couple of minutes since the environment is set up on your side.
> >>
> >> —
> >> Denis
> >>
> >>> On Aug 17, 2017, at 5:37 AM, Igor Sapego  wrote:
> >>>
> >>> Akmal,
> >>>
> >>> I work on the ODBC driver and would be glad to help. You can send
> >>> mails with your requests to devlist and I will try to help as much as I
> >>> can.
> >>>
> >>> Best Regards,
> >>> Igor
> >>>
> >>> On Thu, Aug 17, 2017 at 3:28 PM, Akmal Chaudhri <
> >> akmal.chaud...@gridgain.com
>  wrote:
> >>>
>  When I have the opportunity to test the ODBC code and ensure that it
>  performs, I will add it to GH. At the moment, just snippets exist. If
>  anyone can assist with this, I would appreciate it, as I have no
> >> experience
>  with ODBC. I made some efforts to build the ODBC driver and have had
> >> some
>  success on Windows and Linux, but have been unable to run any C++
> code.
> 
>  On 16 August 2017 at 21:41, Denis Magda  wrote:
> 
> > Igniters,
> >
> > The SQL getting started guide is ready and published:
> > https://apacheignite.readme.io/v2.1/docs/getting-started-sql
> >
> > Akmal thanks for your efforts and please apply the following minor
>  changes:
> > * Add ODBC source files to your GitHub project.
> > * Add a flat SQL file (script) to the same project that will include
> >> all
> > the pure SQL statements used in the guide.
> >
> > Basing on this guide I’ve prepared and release a guide for DBeaver
> SQL
> > tool:
> > https://apacheignite-tools.readme.io/docs/dbeaver
> >
> > —
> > Denis
> >
> > On Aug 11, 2017, at 3:17 PM, Denis Magda  wrote:
> >
> > Akmal,
> >
> > Good start! Please consider the following feedback:
> >
> > 1. Connectivity section. Emphasize that ignite-core.jar has to be
> >> copied
> > to the classpath of an app or tool and give a link to more advanced
> >> JDBC
> > Thin driver documentation if the one needs more details. Probably,
>  similar
> > steps should be brought up for the ODBC once it’s ready.
> >
> > 2. Make the first letters of city and people tables uppercase: city
> ->
> > City, people -> People
> >
> > 3. Rename INSERT section to “Inserting Data”, SELECT to “Querying
> >> Data”,
> > UPDATE -> “Modifying Data”, DELETE to “Removing Data” or to better
> > alternatives.
> >
> > 4. Show how to insert at least 2 cities and 5 people in the INSERT
>  section.
> >
> > —
> > Denis
> >
> > On Aug 11, 2017, at 10:42 AM, Akmal Chaudhri <
>  akmal.chaud...@gridgain.com>
> > wrote:
> >
> > Denis, All
> >
> > I have made some progress with the documentation:
> >
> > https://apacheignite.readme.io/v2.1/docs/getting-started-sql <
> > https://apacheignite.readme.io/v2.1/docs/getting-started-sql>
> >
> > ODBC connectivity and examples are missing, but should be completed
> >> very
> > soon.
> >
> > Community feedback welcome.
> >
> > Thanks.
> >
> > On 31 July 2017 at 19:02, Denis Magda  > mailto:dma...@apache.org >> wrote:
> > Igniters,
> >
> > There is a lot of SQL related documentation available for Ignite.
>  However,
> > the one can get lost in it when he/she does her first steps on a
> >> learning
> > path. It’s time to simplify these are first steps with a clear and
> > straightforward getting started guide. I’ve put the requirements into
>  this
> > JIRA ticket:
> > https://issues.apache.org/jira/browse/IGNITE-5886 <
> > https://issues.apache.org/jira/browse/IGNITE-5886>
> >
> > Please share your thoughts in JIRA or in this discussion.
> >
> > Akmal, who perfected his technical writer skills 

Re: SQL Getting Started Guide

[Denis Magda]

Igor, thanks a lot. Appreciate this!

—
Denis

> On Aug 18, 2017, at 8:56 AM, Igor Sapego  wrote:
> 
> I've checked ODBC snippets and fixed all found issues.
> 
> Best Regards,
> Igor
> 
> On Thu, Aug 17, 2017 at 11:16 PM, Denis Magda  wrote:
> 
>> Igor,
>> 
>> Would you mind helping us to test the snippets? I do believe it will take
>> you a couple of minutes since the environment is set up on your side.
>> 
>> —
>> Denis
>> 
>>> On Aug 17, 2017, at 5:37 AM, Igor Sapego  wrote:
>>> 
>>> Akmal,
>>> 
>>> I work on the ODBC driver and would be glad to help. You can send
>>> mails with your requests to devlist and I will try to help as much as I
>>> can.
>>> 
>>> Best Regards,
>>> Igor
>>> 
>>> On Thu, Aug 17, 2017 at 3:28 PM, Akmal Chaudhri <
>> akmal.chaud...@gridgain.com
 wrote:
>>> 
 When I have the opportunity to test the ODBC code and ensure that it
 performs, I will add it to GH. At the moment, just snippets exist. If
 anyone can assist with this, I would appreciate it, as I have no
>> experience
 with ODBC. I made some efforts to build the ODBC driver and have had
>> some
 success on Windows and Linux, but have been unable to run any C++ code.
 
 On 16 August 2017 at 21:41, Denis Magda  wrote:
 
> Igniters,
> 
> The SQL getting started guide is ready and published:
> https://apacheignite.readme.io/v2.1/docs/getting-started-sql
> 
> Akmal thanks for your efforts and please apply the following minor
 changes:
> * Add ODBC source files to your GitHub project.
> * Add a flat SQL file (script) to the same project that will include
>> all
> the pure SQL statements used in the guide.
> 
> Basing on this guide I’ve prepared and release a guide for DBeaver SQL
> tool:
> https://apacheignite-tools.readme.io/docs/dbeaver
> 
> —
> Denis
> 
> On Aug 11, 2017, at 3:17 PM, Denis Magda  wrote:
> 
> Akmal,
> 
> Good start! Please consider the following feedback:
> 
> 1. Connectivity section. Emphasize that ignite-core.jar has to be
>> copied
> to the classpath of an app or tool and give a link to more advanced
>> JDBC
> Thin driver documentation if the one needs more details. Probably,
 similar
> steps should be brought up for the ODBC once it’s ready.
> 
> 2. Make the first letters of city and people tables uppercase: city ->
> City, people -> People
> 
> 3. Rename INSERT section to “Inserting Data”, SELECT to “Querying
>> Data”,
> UPDATE -> “Modifying Data”, DELETE to “Removing Data” or to better
> alternatives.
> 
> 4. Show how to insert at least 2 cities and 5 people in the INSERT
 section.
> 
> —
> Denis
> 
> On Aug 11, 2017, at 10:42 AM, Akmal Chaudhri <
 akmal.chaud...@gridgain.com>
> wrote:
> 
> Denis, All
> 
> I have made some progress with the documentation:
> 
> https://apacheignite.readme.io/v2.1/docs/getting-started-sql <
> https://apacheignite.readme.io/v2.1/docs/getting-started-sql>
> 
> ODBC connectivity and examples are missing, but should be completed
>> very
> soon.
> 
> Community feedback welcome.
> 
> Thanks.
> 
> On 31 July 2017 at 19:02, Denis Magda  mailto:dma...@apache.org >> wrote:
> Igniters,
> 
> There is a lot of SQL related documentation available for Ignite.
 However,
> the one can get lost in it when he/she does her first steps on a
>> learning
> path. It’s time to simplify these are first steps with a clear and
> straightforward getting started guide. I’ve put the requirements into
 this
> JIRA ticket:
> https://issues.apache.org/jira/browse/IGNITE-5886 <
> https://issues.apache.org/jira/browse/IGNITE-5886>
> 
> Please share your thoughts in JIRA or in this discussion.
> 
> Akmal, who perfected his technical writer skills working for IBM,
> volunteered to take over this task. Akmal, please create an account in
> Ignite JIRA and share it with us. You’ll be able to assign the task on
> yourself afterwards.
> https://issues.apache.org/jira/projects/IGNITE <
 https://issues.apache.org/
> jira/projects/IGNITE>
> 
> Moreover, once the guide is ready Prachi will use it as a basis for the
> new SQL screencast we need to produce.
> 
> —
> Denis
> 
> 
> 
> 
 
>> 
>> 

Re: Cluster auto activation design proposal

[Alexey Dmitriev]

API is proposed in the head of the thread by Sergey, as I understood:
__

API for BaselineTopology manipulation may look like this: 

*Ignite::activation::establishBaselineTopology();* 
*Ignite::activation::establishBaselineTopology(BaselineTopology bltTop);* 

Both methods will establish BT and activate cluster once it is established. 

The first one allows user to establish BT using current topology. If any 
changes happen to the topology during establishing process, user will be 
notified and allowed to proceed or abort the procedure. 

Second method allows to use some monitoring'n'management tools like 
WebConsole where user can prepare a list of nodes, using them create a BT 
and send to the cluster a command to finally establish it. 

>From high level BaselineTopology entity contains only collection of nodes: 

*BaselineTopology {* 
*  Collection nodes;* 
*}* 

*TopologyNode* here contains information about node - its consistent id and 
set of user attributes used to calculate affinity function. 




--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Cluster-auto-activation-design-proposal-tp20295p21066.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request #2488: IGNITE-6024: support for server-side dml

[skalashnikov]

GitHub user skalashnikov opened a pull request:

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

IGNITE-6024: support for server-side dml



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

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

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

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


commit 7b3af51a3d6ec538a55c8b0172205a38b87f4e22
Author: skalashnikov 
Date:   2017-08-18T17:13:21Z

IGNITE-6024: support for server-side dml




---
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-6114) Replace standard java maps for partition counters in continuous queries

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-6114:


 Summary: Replace standard java maps for partition counters in 
continuous queries
 Key: IGNITE-6114
 URL: https://issues.apache.org/jira/browse/IGNITE-6114
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.1
Reporter: Alexey Goncharuk
 Fix For: 2.2


This is a continuation of IGNITE-5872.

We need to replace standard java maps in StartRoutineDiscoveryMessage with the 
maps introduced in IGNITE-5872.



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

[GitHub] ignite pull request #2487: IGNITE-6035 clean index on cache destroy

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

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

IGNITE-6035 clean index on cache destroy



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

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

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

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


commit c3e91201623d6bdcfaa460a0c81bddb112eaa3eb
Author: Dmitriy Govorukhin 
Date:   2017-08-18T16:48:28Z

IGNITE-6035 WIP. Dirty fix.




---
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 #2423: IGNITE-5943

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: SQL Getting Started Guide

[Igor Sapego]

I've checked ODBC snippets and fixed all found issues.

Best Regards,
Igor

On Thu, Aug 17, 2017 at 11:16 PM, Denis Magda  wrote:

> Igor,
>
> Would you mind helping us to test the snippets? I do believe it will take
> you a couple of minutes since the environment is set up on your side.
>
> —
> Denis
>
> > On Aug 17, 2017, at 5:37 AM, Igor Sapego  wrote:
> >
> > Akmal,
> >
> > I work on the ODBC driver and would be glad to help. You can send
> > mails with your requests to devlist and I will try to help as much as I
> > can.
> >
> > Best Regards,
> > Igor
> >
> > On Thu, Aug 17, 2017 at 3:28 PM, Akmal Chaudhri <
> akmal.chaud...@gridgain.com
> >> wrote:
> >
> >> When I have the opportunity to test the ODBC code and ensure that it
> >> performs, I will add it to GH. At the moment, just snippets exist. If
> >> anyone can assist with this, I would appreciate it, as I have no
> experience
> >> with ODBC. I made some efforts to build the ODBC driver and have had
> some
> >> success on Windows and Linux, but have been unable to run any C++ code.
> >>
> >> On 16 August 2017 at 21:41, Denis Magda  wrote:
> >>
> >>> Igniters,
> >>>
> >>> The SQL getting started guide is ready and published:
> >>> https://apacheignite.readme.io/v2.1/docs/getting-started-sql
> >>>
> >>> Akmal thanks for your efforts and please apply the following minor
> >> changes:
> >>> * Add ODBC source files to your GitHub project.
> >>> * Add a flat SQL file (script) to the same project that will include
> all
> >>> the pure SQL statements used in the guide.
> >>>
> >>> Basing on this guide I’ve prepared and release a guide for DBeaver SQL
> >>> tool:
> >>> https://apacheignite-tools.readme.io/docs/dbeaver
> >>>
> >>> —
> >>> Denis
> >>>
> >>> On Aug 11, 2017, at 3:17 PM, Denis Magda  wrote:
> >>>
> >>> Akmal,
> >>>
> >>> Good start! Please consider the following feedback:
> >>>
> >>> 1. Connectivity section. Emphasize that ignite-core.jar has to be
> copied
> >>> to the classpath of an app or tool and give a link to more advanced
> JDBC
> >>> Thin driver documentation if the one needs more details. Probably,
> >> similar
> >>> steps should be brought up for the ODBC once it’s ready.
> >>>
> >>> 2. Make the first letters of city and people tables uppercase: city ->
> >>> City, people -> People
> >>>
> >>> 3. Rename INSERT section to “Inserting Data”, SELECT to “Querying
> Data”,
> >>> UPDATE -> “Modifying Data”, DELETE to “Removing Data” or to better
> >>> alternatives.
> >>>
> >>> 4. Show how to insert at least 2 cities and 5 people in the INSERT
> >> section.
> >>>
> >>> —
> >>> Denis
> >>>
> >>> On Aug 11, 2017, at 10:42 AM, Akmal Chaudhri <
> >> akmal.chaud...@gridgain.com>
> >>> wrote:
> >>>
> >>> Denis, All
> >>>
> >>> I have made some progress with the documentation:
> >>>
> >>> https://apacheignite.readme.io/v2.1/docs/getting-started-sql <
> >>> https://apacheignite.readme.io/v2.1/docs/getting-started-sql>
> >>>
> >>> ODBC connectivity and examples are missing, but should be completed
> very
> >>> soon.
> >>>
> >>> Community feedback welcome.
> >>>
> >>> Thanks.
> >>>
> >>> On 31 July 2017 at 19:02, Denis Magda  >>> mailto:dma...@apache.org >> wrote:
> >>> Igniters,
> >>>
> >>> There is a lot of SQL related documentation available for Ignite.
> >> However,
> >>> the one can get lost in it when he/she does her first steps on a
> learning
> >>> path. It’s time to simplify these are first steps with a clear and
> >>> straightforward getting started guide. I’ve put the requirements into
> >> this
> >>> JIRA ticket:
> >>> https://issues.apache.org/jira/browse/IGNITE-5886 <
> >>> https://issues.apache.org/jira/browse/IGNITE-5886>
> >>>
> >>> Please share your thoughts in JIRA or in this discussion.
> >>>
> >>> Akmal, who perfected his technical writer skills working for IBM,
> >>> volunteered to take over this task. Akmal, please create an account in
> >>> Ignite JIRA and share it with us. You’ll be able to assign the task on
> >>> yourself afterwards.
> >>> https://issues.apache.org/jira/projects/IGNITE <
> >> https://issues.apache.org/
> >>> jira/projects/IGNITE>
> >>>
> >>> Moreover, once the guide is ready Prachi will use it as a basis for the
> >>> new SQL screencast we need to produce.
> >>>
> >>> —
> >>> Denis
> >>>
> >>>
> >>>
> >>>
> >>
>
>

[jira] [Created] (IGNITE-6113) Partition eviction prevents exchange from completion

[Vladislav Pyatkov (JIRA)]

Vladislav Pyatkov created IGNITE-6113:
-

 Summary: Partition eviction prevents exchange from completion
 Key: IGNITE-6113
 URL: https://issues.apache.org/jira/browse/IGNITE-6113
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Vladislav Pyatkov


Customer has waited for 3 hours for completion without any success.

exchange-worker is blocked.

{noformat}
"exchange-worker-#92%DPL_GRID%grid554.ca.sbrf.ru%" #173 prio=5 os_prio=0 
tid=0x7f0835c2e000 nid=0xb907 runnable [0x7e74ab1d]
   java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x7efee630a7c0> (a 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition$1)
at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:189)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.assign(GridDhtPreloader.java:340)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1801)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)

   Locked ownable synchronizers:
- None
{noformat}

{noformat}
"sys-#124%DPL_GRID%grid554.ca.sbrf.ru%" #278 prio=5 os_prio=0 
tid=0x7e731c02d000 nid=0xbf4d runnable [0x7e734e7f7000]
   java.lang.Thread.State: RUNNABLE
at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
at sun.nio.ch.IOUtil.write(IOUtil.java:51)
at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211)
- locked <0x7f056161bf88> (a java.lang.Object)
at 
org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.writeBuffer(FileWriteAheadLogManager.java:1829)
at 
org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.flush(FileWriteAheadLogManager.java:1572)
at 
org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:1421)
at 
org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.access$800(FileWriteAheadLogManager.java:1331)
at 
org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:339)
at 
org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.beforeReleaseWrite(PageMemoryImpl.java:1287)
at 
org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1142)
at 
org.gridgain.grid.internal.processors.cache.database.pagemem.PageImpl.releaseWrite(PageImpl.java:167)
at 
org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writeUnlock(PageHandler.java:193)
at 
org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:242)
at 
org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:119)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.doRemoveFromLeaf(BPlusTree.java:2886)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.removeFromLeaf(BPlusTree.java:2865)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.access$6900(BPlusTree.java:2515)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1607)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1574)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1574)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1574)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1574)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.doRemove(BPlusTree.java:1481)
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.remove(BPlusTree.java:1451)
at 

Re: Ignite Add-on/Extension Request: Please add GA Grid (beta) to Ignite website

[Prachi Garg]

Turik,

Thanks for you contribution. I will add it to the website early next week.

-P

On Fri, Aug 18, 2017 at 3:57 AM, techbysample  wrote:

> Dennis/Prachi,
>
> Thanks you! Please include GA Grid Architecture within the addon section..
>
> For example, Here is content from my initial post in Ignite users forum:
>
> http://apache-ignite-users.70518.x6.nabble.com/GA-Grid-
> Beta-Genetic-Algorithm-component-for-Ignite-is-here-td16041.html
>
> Best
> Turik
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Ignite-Add-on-Extension-
> Request-Please-add-GA-Grid-beta-to-Ignite-website-tp20947p21042.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>

Re: Ignite Add-on/Extension Request: Please add GA Grid (beta) to Ignite website

[techbysample]

Dennis/Prachi,

Thanks you! Please include GA Grid Architecture within the addon section..

For example, Here is content from my initial post in Ignite users forum:

http://apache-ignite-users.70518.x6.nabble.com/GA-Grid-Beta-Genetic-Algorithm-component-for-Ignite-is-here-td16041.html

Best
Turik 



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Add-on-Extension-Request-Please-add-GA-Grid-beta-to-Ignite-website-tp20947p21042.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request #2486: Fill factor metric for persistent mode.

[ilantukh]

GitHub user ilantukh opened a pull request:

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

Fill factor metric for persistent mode.



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

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

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

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


commit 1e08c3fb5c02ec8acafd71b50b6ad3b749259f1a
Author: Andrey V. Mashenkov 
Date:   2017-07-31T11:14:56Z

IGNITE-4800: Lucene query may fails with NPE. This closes #2315.

commit 3fdf453e89a7bd76dff6b6d0646e3821ea3921d5
Author: Andrey V. Mashenkov 
Date:   2017-07-31T14:32:12Z

IGNITE-4800: Lucene query may fails with NPE.
Test fixed.

commit e255a564985a12113984ec02f15a4443495b8ffc
Author: Nikolay Izhikov 
Date:   2017-08-02T08:52:44Z

ignite-5712 Context switching for optimistic transactions

commit 772d462b68c7de8517d1f61e2e05ec8eefb18eac
Author: Alexey Kuznetsov 
Date:   2017-08-03T04:55:15Z

Merge branch ignite-2.1.3 into ignite-2.1.4

commit 0f3b7ca25313083e4dc35e7842931a655abd
Author: tledkov-gridgain 
Date:   2017-08-04T08:46:14Z

IGNITE-5126: Batch support for this JDBC driver. This closes #2162.

commit d1a74a4be8744528e6ed23706174041ddb0f2618
Author: devozerov 
Date:   2017-08-04T09:04:38Z

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

commit 0b3a9a7176f5ae44a96ecf700c8147193dfbf064
Author: Igor Sapego 
Date:   2017-08-04T10:18:00Z

IGNITE-5923: ODBC: SQLGetTypeInfo now works with SQL_ALL_TYPES

(cherry picked from commit 48c914d)

commit 4e0385fbc0f50548f2da3407fdfdfe939b463c67
Author: Igor Sapego 
Date:   2017-08-04T15:34:27Z

IGNITE-5939: ODBC: SQLColAttributes now works with legacy attribute codes.

(cherry picked from commit 70ffa2c)

commit 4f02504475fd1e5cc3b9f4754856e44d20fdc1cb
Author: Alexey Kuznetsov 
Date:   2017-08-07T02:41:22Z

Merge branch ignite-2.1.3 into ignite-2.1.4.

commit b093afb8231135a4904f5fffd62f5b4c332f1d47
Author: tledkov-gridgain 
Date:   2017-08-08T09:05:36Z

IGNITE-5211: Added new constructor: QueryEntity(Class keyCls, Class 
valCls). This closes #2371. This closes #2388. This closes #2407.

commit 879f19106b22e66d5f6ea94424d961d049397410
Author: devozerov 
Date:   2017-08-08T12:16:58Z

IGNITE-5982: GridMapQueryExecutor was split into several pieces.

commit 7c77b869bc3efdf19e53cc2b064f4290fd73e2b2
Author: devozerov 
Date:   2017-08-09T08:47:58Z

IGNITE-5993: Removed unused SQL-related classes and methods (old tree 
index, snapshots, etc). This closes #2414.

commit ab18fdfcc4f6db1e54fb1f3b68ba7fbc31a7f6e7
Author: Andrey V. Mashenkov 
Date:   2017-07-14T17:14:47Z

IGNITE-5452: GridTimeoutProcessor can hang on stop. This closes #2279.

commit 580b6aa8e5a8a887397eab5c4c830ec28f45cd30
Author: Alexey Kuznetsov 
Date:   2017-08-09T10:22:54Z

IGNITE-5734 Web Console: Fixed npm dependencies.
(cherry picked from commit aeafbf1)

commit 841db65e56063605475710bc170de4aea672c31d
Author: Alexey Kuznetsov 
Date:   2017-08-09T11:55:04Z

IGNITE-5987 Added -nq (visor will not quit in batch mode) option for Visor 
Cmd.
(cherry picked from commit 8d6e842)

commit 5c2097856714a7803956d754735c68b21156019c
Author: Alexey Kuznetsov 
Date:   2017-08-11T03:25:36Z

IGNITE-5902 Implemented stop caches at once.
(cherry picked from commit ebb8765)

commit 8b2461942c18f228c0107020aa28c03711bdceda
Author: Alexey Kuznetsov 
Date:   2017-08-11T04:07:26Z

IGNITE-6012 Refactored GridJettyRestHandler.processRequest(): replace 
mapper.writeValueAsString with writeValue(stream, v).
(cherry picked from commit 3a390c8)

commit 3a7d4f4a79e7c0a23244387e3a68535375a66a87
Author: Alexey Kuznetsov 
Date:   2017-08-11T04:18:42Z

IGNITE-6013 Optimized processing response from cluster.
(cherry picked from commit b02c481)

commit 74d6ab9916b3a01c78cdf1ad86211c9fcbb2214d
Author: Alexey Goncharuk 
Date:   2017-08-14T08:08:28Z

Merge branch 'ignite-2.1.3' into ignite-2.1.4

commit fde550bac56fd0cc7c51c62a9c291dd4c3f3030c
Author: Ilya Lantukh 
Date:   2017-08-14T08:32:11Z

IGNITE-5941 - Fixed index name length restrictions. This closes #2408

commit 13f38d79b57b395e43d42a8f3c278cf48336d7c5
Author: Dmitriy Govorukhin 

[GitHub] ignite pull request #2484: Backport IGNITE-3196

[alamar]

GitHub user alamar reopened a pull request:

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

Backport IGNITE-3196

Add support for BigDecimals with negative scale in BinaryMarshaller

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

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

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

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


commit a62a0136d295486d95c6e2ab5bba88270d831753
Author: dkarachentsev 
Date:   2016-11-02T16:07:45Z

GG-11655 - Fix merge

commit 348593986b56ddfcec4a4455e49d9b279eae4dc8
Author: devozerov 
Date:   2016-11-05T10:28:03Z

Merge branch 'ignite-1.7.3' into ignite-1.7.4

commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d
Author: tledkov-gridgain 
Date:   2016-11-07T06:16:58Z

IGNITE-3432:  check data/meta cache names are different for different IGFS 
instances. This closes #1201

commit ead15193899d08f41491166003cabed0560f0c59
Author: Pavel Tupitsyn 
Date:   2016-11-07T07:49:03Z

IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget

This closes #1192

commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd
Author: Dmitriy Govorukhin 
Date:   2016-11-07T09:09:41Z

ignite-4178 support permission builder

commit df670c7d64046d282c053f296c47a4743c58c8b1
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:40:00Z

IGNITE-4118 .NET: Optimistic transaction example

This closes #1200

commit 474f22fda4c7cf4d7b2623c451cd7c10f0d8c636
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:55:20Z

IGNITE-4119 .NET: add TransactionDeadlockException

commit fc7ce5a4d72145f2e8a86debeda264ef0a5b37e3
Author: isapego 
Date:   2016-11-07T10:26:05Z

IGNITE-4090: Added flags so stdint and limits can be used in C++.

commit a98804a249496ba9bafbc96daa7aaf25b3d36724
Author: Igor Sapego 
Date:   2016-11-07T11:00:00Z

IGNITE-4113: Added tests. Added Statement::Set/GetAttribute.

commit b1c7c9bb95c900083702d0ba0362edf3aea5a7b4
Author: sboikov 
Date:   2016-11-07T12:40:36Z

GG-11360 - Implement SQL queries cancellation
Fix for commit 80abd1b: for distributed joins need always send cancel 
request.

commit 319014de075c80fb15e58172cc24e35ce16b56cf
Author: Pavel Tupitsyn 
Date:   2016-11-07T14:53:40Z

IGNITE-4132 .NET: Improve BinaryConfiguration documentation

commit 950bad474ef29f9b808e74034c49a69d57eb2740
Author: dkarachentsev 
Date:   2016-11-08T11:03:34Z

GG-11655 - Restore service compatibility with releases before 1.5.30.

commit 3d19bfc2b66574e3945ce17c7a4dfe77d0070b8d
Author: dkarachentsev 
Date:   2016-11-08T11:04:36Z

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

commit 1612b6d66fed032182a41e90da71e6b986ae087b
Author: Pavel Tupitsyn 
Date:   2016-11-08T11:07:54Z

.NET: Fix minor analysis warnings

commit e821dc0083003bc81058b1cb223d8a8a2ee44daf
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:09:21Z

IGNITE-2079 (revert commit) GridCacheIoManager eats exception trail if it 
falls into the directed case

commit c2c82ca44befe4570325dd6cf2ba885e0d90596c
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:10:10Z

Merge remote-tracking branch 'professional/ignite-1.6.11' into ignite-1.6.11

commit 865bbcf0f41a0c4944e0928f1758d43a0eae82c5
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:18:29Z

Revert "Merge remote-tracking branch 'professional/ignite-1.6.11' into 
ignite-1.6.11"

This reverts commit c2c82ca44befe4570325dd6cf2ba885e0d90596c, reversing
changes made to e821dc0083003bc81058b1cb223d8a8a2ee44daf.

commit 9726421ff9efb2b19813b2fd6ad27a3728b5ab1a
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:59:00Z

  Revert  Revert  Merge remote-tracking branch 'professional/ignite-1.6.11'

commit 5a3a1960fff1dcf32961c45c0ba5149d6748d2fc
Author: Igor Sapego 
Date:   2016-11-08T14:36:35Z

Added license header.

commit f697fb5786fb4ce15f581c465ff0dcb3d2bb7b14
Author: Pavel Tupitsyn 
Date:   2016-11-08T16:13:48Z

IGNITE-4185 .NET: Fix NullReferenceException in IgniteOutputCacheProvider 
when igniteConfiguration is missing

commit 69487f2c375010737311af65750a519b403fc17f
Author: Pavel Tupitsyn 
Date:   2016-11-08T16:38:28Z

.NET: Fix error messages when IgniteConfigurationSection content is missing

commit 

[GitHub] ignite pull request #2484: Backport IGNITE-3196

[alamar]

Github user alamar closed the pull request at:

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


---
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 #2485: Backport IGNITE-3196

[alamar]

Github user alamar closed the pull request at:

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


---
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 #2484: Backport IGNITE-3196

[alamar]

GitHub user alamar opened a pull request:

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

Backport IGNITE-3196

Add support for BigDecimals with negative scale in BinaryMarshaller

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

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

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

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


commit a62a0136d295486d95c6e2ab5bba88270d831753
Author: dkarachentsev 
Date:   2016-11-02T16:07:45Z

GG-11655 - Fix merge

commit 348593986b56ddfcec4a4455e49d9b279eae4dc8
Author: devozerov 
Date:   2016-11-05T10:28:03Z

Merge branch 'ignite-1.7.3' into ignite-1.7.4

commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d
Author: tledkov-gridgain 
Date:   2016-11-07T06:16:58Z

IGNITE-3432:  check data/meta cache names are different for different IGFS 
instances. This closes #1201

commit ead15193899d08f41491166003cabed0560f0c59
Author: Pavel Tupitsyn 
Date:   2016-11-07T07:49:03Z

IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget

This closes #1192

commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd
Author: Dmitriy Govorukhin 
Date:   2016-11-07T09:09:41Z

ignite-4178 support permission builder

commit df670c7d64046d282c053f296c47a4743c58c8b1
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:40:00Z

IGNITE-4118 .NET: Optimistic transaction example

This closes #1200

commit 474f22fda4c7cf4d7b2623c451cd7c10f0d8c636
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:55:20Z

IGNITE-4119 .NET: add TransactionDeadlockException

commit fc7ce5a4d72145f2e8a86debeda264ef0a5b37e3
Author: isapego 
Date:   2016-11-07T10:26:05Z

IGNITE-4090: Added flags so stdint and limits can be used in C++.

commit a98804a249496ba9bafbc96daa7aaf25b3d36724
Author: Igor Sapego 
Date:   2016-11-07T11:00:00Z

IGNITE-4113: Added tests. Added Statement::Set/GetAttribute.

commit b1c7c9bb95c900083702d0ba0362edf3aea5a7b4
Author: sboikov 
Date:   2016-11-07T12:40:36Z

GG-11360 - Implement SQL queries cancellation
Fix for commit 80abd1b: for distributed joins need always send cancel 
request.

commit 319014de075c80fb15e58172cc24e35ce16b56cf
Author: Pavel Tupitsyn 
Date:   2016-11-07T14:53:40Z

IGNITE-4132 .NET: Improve BinaryConfiguration documentation

commit 950bad474ef29f9b808e74034c49a69d57eb2740
Author: dkarachentsev 
Date:   2016-11-08T11:03:34Z

GG-11655 - Restore service compatibility with releases before 1.5.30.

commit 3d19bfc2b66574e3945ce17c7a4dfe77d0070b8d
Author: dkarachentsev 
Date:   2016-11-08T11:04:36Z

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

commit 1612b6d66fed032182a41e90da71e6b986ae087b
Author: Pavel Tupitsyn 
Date:   2016-11-08T11:07:54Z

.NET: Fix minor analysis warnings

commit e821dc0083003bc81058b1cb223d8a8a2ee44daf
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:09:21Z

IGNITE-2079 (revert commit) GridCacheIoManager eats exception trail if it 
falls into the directed case

commit c2c82ca44befe4570325dd6cf2ba885e0d90596c
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:10:10Z

Merge remote-tracking branch 'professional/ignite-1.6.11' into ignite-1.6.11

commit 865bbcf0f41a0c4944e0928f1758d43a0eae82c5
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:18:29Z

Revert "Merge remote-tracking branch 'professional/ignite-1.6.11' into 
ignite-1.6.11"

This reverts commit c2c82ca44befe4570325dd6cf2ba885e0d90596c, reversing
changes made to e821dc0083003bc81058b1cb223d8a8a2ee44daf.

commit 9726421ff9efb2b19813b2fd6ad27a3728b5ab1a
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:59:00Z

  Revert  Revert  Merge remote-tracking branch 'professional/ignite-1.6.11'

commit 5a3a1960fff1dcf32961c45c0ba5149d6748d2fc
Author: Igor Sapego 
Date:   2016-11-08T14:36:35Z

Added license header.

commit f697fb5786fb4ce15f581c465ff0dcb3d2bb7b14
Author: Pavel Tupitsyn 
Date:   2016-11-08T16:13:48Z

IGNITE-4185 .NET: Fix NullReferenceException in IgniteOutputCacheProvider 
when igniteConfiguration is missing

commit 69487f2c375010737311af65750a519b403fc17f
Author: Pavel Tupitsyn 
Date:   2016-11-08T16:38:28Z

.NET: Fix error messages when IgniteConfigurationSection content is missing

commit 

Re: ODBC doc needs to be updated

[Igor Sapego]

Denis,

Ok, I've filed a ticket [1] and will take a look.

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

Best Regards,
Igor

On Fri, Aug 18, 2017 at 3:19 AM, Dmitriy Setrakyan 
wrote:

> Denis, it will be helpful to also file a ticket on this.
>
> On Thu, Aug 17, 2017 at 1:20 PM, Denis Magda  wrote:
>
> > Hi Igor,
> >
> > Could you spend some time walking through the doc and updating it
> > considering the latest features and changes?
> > https://apacheignite.readme.io/docs/quering-data <
> > https://apacheignite.readme.io/docs/quering-data>
> >
> > For instance:
> >
> > 1. The configuration section [1] can be switched to the usage of DDL
> > statements for tables creation and indexes definition.
> >
> > 2. Information about “_key” and “_value” should be wiped out because
> > presently there is a way to set unique names for the whole key and value.
> >
> >
> > [1] https://apacheignite.readme.io/docs/quering-data#
> > configuring-ignite-cluster  > io/docs/quering-data#configuring-ignite-cluster>
> >
> > —
> > Denis
>

[jira] [Created] (IGNITE-6112) Review and update C++ documentation according to new features.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-6112:
---

 Summary: Review and update C++ documentation according to new 
features.
 Key: IGNITE-6112
 URL: https://issues.apache.org/jira/browse/IGNITE-6112
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.1
Reporter: Igor Sapego
Assignee: Igor Sapego


It is needed to spend some time walking through the doc and updating it 
considering the latest features and changes 
https://apacheignite.readme.io/docs/quering-data 

For instance:

1. The configuration section [1] can be switched to the usage of DDL statements 
for tables creation and indexes definition.

2. Information about "_key" and "_value" should be wiped out because presently 
there is a way to set unique names for the whole key and value.



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

[GitHub] ignite pull request #2478: IGNITE-5925: Get row/col for matrices

[ybabak]

Github user ybabak closed the pull request at:

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


---
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 #2483: IGNITE-GG-12646 Fix tests for JSR-310 Java 8 Date...

[asfedotov]

GitHub user asfedotov opened a pull request:

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

IGNITE-GG-12646 Fix tests for JSR-310 Java 8 Date and Time API introduced 
with IGNITE-GG-12549

For CI purposes

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

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

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

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


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

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

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

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

(cherry picked from commit ba6227b)

commit 960e454b4b68c76ed94ca58a3ee9a9d8e79c2039
Author: dkarachentsev 
Date:   2017-04-10T07:28:15Z

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

(cherry picked from commit 220db88)

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

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

(cherry picked from commit ba6227b)

(cherry picked from commit bb3ff12)

commit 5fbbc37669bcf0557a98d8ab70c3dbb79ebcd340
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 b8e3d1b)

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

IGNITE-4879: Fixed System pool starvation while partition evicting.

commit 89e9dbe484312c251f02c9fbe9698c3ac2e03df8
Author: Alexander Fedotov 
Date:   2017-04-10T13:36:33Z

Fix org.apache.ignite.internal.processors.cache.expiry
.IgniteCacheExpiryPolicyAbstractTest#testNearExpiresWithCacheStore

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

IGNITE-4863: Disallow change RootLogger log-level if it can have negative 
effect on other loggers. This closes #1687.

commit 02b194268071b179d291b28472cef5d587e7558a
Author: Alexander Fedotov 
Date:   2017-04-11T09:00:59Z

Fix missing test resource directory for
org.apache.ignite.spi.discovery.tcp
.TcpDiscoveryNodeAttributesUpdateOnReconnectTest.testReconnect

commit 20016a20f780eb3c21f249d3cb74d08018c4eea5
Author: Alexander Fedotov 
Date:   2017-04-11T11:54:06Z

Fix org.apache.ignite.internal.processors.cache.expiry
.IgniteCacheExpiryPolicyAbstractTest#testNearExpiresWithCacheStore

commit 6d12bd4b9fbded5e5862b5c3d89b05a5ddd11755
Author: Igor Sapego 
Date:   2017-03-21T14:54:51Z

IGNITE-4200: Added copying of the C++ binaries.

(cherry picked from commit 8b3860f)

commit 0f7ef74216fab64f5d1d2b6d432b552b7fe40d2f
Author: Andrey V. Mashenkov 
Date:   2017-04-12T10:01:25Z

IGNITE-4907: Fixed excessive service instances can be started with dynamic 
deployment. This closes #1766.

commit 465084da5b00dcfc056d338f5d0a24875ca2af08
Author: Andrey V. Mashenkov 
Date:   2017-04-12T10:01:25Z

IGNITE-4907: Fixed excessive service instances can be started with dynamic 
deployment. This closes #1766.

(cherry picked from commit 0f7ef74)

commit a20c307df1dd000309a273ef93231fdc41a2a81c
Author: dkarachentsev 
Date:   2017-04-13T06:31:17Z

IGNITE-4891 - Fix. Key is deserialized during transactional get() even if 
withKeepBinary is set

(Backport from master)

commit 630558dfeb373f237057e394e8f2f63230d59dab
Author: vladisav 
Date:   2017-04-13T10:24:42Z

ignite-4173 IgniteSemaphore with failoverSafe enabled doesn't release 
permits in case permits owner node left topology

Backport from master.

(cherry picked from commit 76485fc)

commit 870b752c095ed3776e91a65b99763142b9f2ebc0
Author: Vladisav Jelisavcic 
Date:   2017-04-11T11:09:12Z

ignite-1977 - fixed IgniteSemaphore fault tolerance.

Backport from master.

(cherry picked from commit 902bf42)

commit cd0b92950c6691c6fc1a26cb4f7e55f5ee459298
Author: Yakov 

Re: Ignite: configuration changes at runtime

[Alexey Kuznetsov]

Just as idea...

Can we have reference to read-only "initialConfig" - a config node was
started with.
And current "mutable via special API" config?

Having this we could show in some management tool what was changed
 (for example, TeamCity has such functionality - history of who and what
was changed in build properties).

On Fri, Aug 18, 2017 at 3:57 PM, Yakov Zhdanov  wrote:

> Here is the list of params that can be changed - https://cwiki.apache.org/
> confluence/display/IGNITE/Allow+Configuration+Settings+Change+At+Runtime
>
> >No, the Ignite configuration is what Ignite receives on startup. Runtime
> >changes are outside of configuration, especially given that if cluster
> >restarts, they are likely lost.
>
> Again, how you provide all-in-one-place current node configuration? Also,
> why changes should be lost? In case of persistence they should not be lost,
> moreover, nodes joining with previous configuration should pick up current
> properties of running nodes.
>
> >I think providing API is important for users who want to integrate Ignite
> >with their own management tools.
>
> This maybe done via JMX. Currently, I guess we expose only configuration
> toString() via it.
>
> --Yakov
>



-- 
Alexey Kuznetsov

[GitHub] ignite pull request #2482: IGNITE-5869 client hangs infinitely while binary ...

[zstan]

GitHub user zstan opened a pull request:

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

IGNITE-5869 client hangs infinitely while binary configuration differs from 
server



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

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

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

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


commit 4de9de484dc595e816f8024b18c2988d5bd03983
Author: Evgeny Stanilovskiy 
Date:   2017-08-18T12:23:42Z

IGNITE-5869 client hangs infinitely while binary configuration differs from 
server




---
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 #2481: IGNITE-4643 Fix NPE in getIndexInfo() with test

[alamar]

GitHub user alamar opened a pull request:

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

IGNITE-4643 Fix NPE in getIndexInfo() with test

Also ported several tests from Thin driver implementation.
Fixed a problem in Primary Keys metadata.
Fixed several get*Version() methods to return Ignite version/JDBC 4.1 
instead of dummy values.

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

$ git pull https://github.com/alamar/ignite ignite-4643

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

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


commit f3bf90943ce9a613296929d8050c55aa0cdc88b0
Author: Ilya Kasnacheev 
Date:   2017-08-18T11:40:42Z

IGNITE-4643 Fix NPE in getIndexInfo() with test

Also ported several tests from Thin driver implementation.
Fixed a problem in Primary Keys metadata.
Fixed several get*Version() methods to return Ignite version/JDBC 4.1 
instead of dummy 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.
---

[GitHub] ignite pull request #2479: IGNITE-6101

[gvvinblade]

GitHub user gvvinblade opened a pull request:

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

IGNITE-6101



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

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

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

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


commit 71b887a7ea8e4b778eb53193b79202fed77a16f7
Author: Igor Seliverstov 
Date:   2017-08-18T11:36:44Z

IGNITE-6101 Try to improve local scans performance




---
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 #2478: IGNITE-5925: Get row/col for matrices

[ybabak]

GitHub user ybabak opened a pull request:

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

IGNITE-5925: Get row/col for matrices



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

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

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

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


commit 227e1315e0739ab71c83c9889c67e616a997a34b
Author: Yury Babak 
Date:   2017-08-14T17:08:15Z

IGNITE-5925: Get row/col for matrices
WIP

commit 49e5846469d73e356a960e8a26fac82508fc10d1
Author: Yury Babak 
Date:   2017-08-18T10:24:25Z

IGNITE-5925: Get row/col for matrices
- implemented




---
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-6111) SQL: Add ability to do INSERT without specifying the column names

[Alexandr Fedotov (JIRA)]

Alexandr Fedotov created IGNITE-6111:


 Summary: SQL: Add ability to do INSERT without specifying the 
column names
 Key: IGNITE-6111
 URL: https://issues.apache.org/jira/browse/IGNITE-6111
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.1
Reporter: Alexandr Fedotov
 Fix For: 2.2


Having the following classes
{code:java}
class PersonKey {
private Long id;
}

class Person {
private Long id;
private String name;
}
{code}
with proper configuration it should be possible to execute queries 
of the following type passing {{id}} and {{name}} as the arguments
{code:sql}"insert into Person values(?,?)"{code}




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

[jira] [Created] (IGNITE-6110) CLONE - SQL: Add ability to do INSERT without specifying the column names

[Alexandr Fedotov (JIRA)]

Alexandr Fedotov created IGNITE-6110:


 Summary: CLONE - SQL: Add ability to do INSERT without specifying 
the column names
 Key: IGNITE-6110
 URL: https://issues.apache.org/jira/browse/IGNITE-6110
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.1
Reporter: Alexandr Fedotov
 Fix For: 2.2


Having the following classes
{code:java}
class PersonKey {
private Long id;
}

class Person {
private Long id;
private String name;
}
{code}
with proper configuration it should be possible to execute queries 
of the following type passing {{id}} and {{name}} as the arguments
{code:sql}"insert into Person values(?,?)"{code}




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

[GitHub] ignite pull request #2477: Ignite gg 12620

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

Ignite gg 12620



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

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

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

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


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

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

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

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

(cherry picked from commit ba6227b)

commit 960e454b4b68c76ed94ca58a3ee9a9d8e79c2039
Author: dkarachentsev 
Date:   2017-04-10T07:28:15Z

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

(cherry picked from commit 220db88)

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

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

(cherry picked from commit ba6227b)

(cherry picked from commit bb3ff12)

commit 5fbbc37669bcf0557a98d8ab70c3dbb79ebcd340
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 b8e3d1b)

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

IGNITE-4879: Fixed System pool starvation while partition evicting.

commit 89e9dbe484312c251f02c9fbe9698c3ac2e03df8
Author: Alexander Fedotov 
Date:   2017-04-10T13:36:33Z

Fix org.apache.ignite.internal.processors.cache.expiry
.IgniteCacheExpiryPolicyAbstractTest#testNearExpiresWithCacheStore

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

IGNITE-4863: Disallow change RootLogger log-level if it can have negative 
effect on other loggers. This closes #1687.

commit 02b194268071b179d291b28472cef5d587e7558a
Author: Alexander Fedotov 
Date:   2017-04-11T09:00:59Z

Fix missing test resource directory for
org.apache.ignite.spi.discovery.tcp
.TcpDiscoveryNodeAttributesUpdateOnReconnectTest.testReconnect

commit 20016a20f780eb3c21f249d3cb74d08018c4eea5
Author: Alexander Fedotov 
Date:   2017-04-11T11:54:06Z

Fix org.apache.ignite.internal.processors.cache.expiry
.IgniteCacheExpiryPolicyAbstractTest#testNearExpiresWithCacheStore

commit 6d12bd4b9fbded5e5862b5c3d89b05a5ddd11755
Author: Igor Sapego 
Date:   2017-03-21T14:54:51Z

IGNITE-4200: Added copying of the C++ binaries.

(cherry picked from commit 8b3860f)

commit 0f7ef74216fab64f5d1d2b6d432b552b7fe40d2f
Author: Andrey V. Mashenkov 
Date:   2017-04-12T10:01:25Z

IGNITE-4907: Fixed excessive service instances can be started with dynamic 
deployment. This closes #1766.

commit 465084da5b00dcfc056d338f5d0a24875ca2af08
Author: Andrey V. Mashenkov 
Date:   2017-04-12T10:01:25Z

IGNITE-4907: Fixed excessive service instances can be started with dynamic 
deployment. This closes #1766.

(cherry picked from commit 0f7ef74)

commit a20c307df1dd000309a273ef93231fdc41a2a81c
Author: dkarachentsev 
Date:   2017-04-13T06:31:17Z

IGNITE-4891 - Fix. Key is deserialized during transactional get() even if 
withKeepBinary is set

(Backport from master)

commit 630558dfeb373f237057e394e8f2f63230d59dab
Author: vladisav 
Date:   2017-04-13T10:24:42Z

ignite-4173 IgniteSemaphore with failoverSafe enabled doesn't release 
permits in case permits owner node left topology

Backport from master.

(cherry picked from commit 76485fc)

commit 870b752c095ed3776e91a65b99763142b9f2ebc0
Author: Vladisav Jelisavcic 
Date:   2017-04-11T11:09:12Z

ignite-1977 - fixed IgniteSemaphore fault tolerance.

Backport from master.

(cherry picked from commit 902bf42)

commit cd0b92950c6691c6fc1a26cb4f7e55f5ee459298
Author: Yakov Zhdanov 
Date:   2017-04-13T12:52:20Z

ignite-4946 

[jira] [Created] (IGNITE-6109) SQL: Add ability to do INSERT without specifying the column names

[Alexandr Fedotov (JIRA)]

Alexandr Fedotov created IGNITE-6109:


 Summary: SQL: Add ability to do INSERT without specifying the 
column names
 Key: IGNITE-6109
 URL: https://issues.apache.org/jira/browse/IGNITE-6109
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.1
Reporter: Alexandr Fedotov
 Fix For: 2.2


Having the following classes
{code:java}
class PersonKey {
private Long id;
}

class Person {
private Long id;
private String name;
}
{code}
with proper configuration it should be possible to execute queries 
of the following type passing {{id}} and {{name}} as the arguments
{code:sql}"insert into Person values(?,?)"{code}




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

Re: Service versioning

[Ilya Lantukh]

Sergey,

I think the ticket covers single atomic piece of functionality.

I'd prefer to avoid to separately address flaws in current service upgrade
process because this process had never been designed, implemented and
supported. Yes, in current ServiceGrid implementation you can (technically)
replace existing service with newer implementation, and there are a number
of potential problems you might encounter while doing so. But it doesn't
make much sense to me to fix flaws in functionality that officially doesn't
exist. Those issues should be addressed in the scope of service versioning.

Use-cases that you described are interesting and we should try to support
them, but I don't think that we should implement functionality for all
possible cases in single step. I'll think how we can technically support
them in Ignite and I'm open to suggestions from you (and anyone else).

I don't think I understand your concept of ServiceRegistry in the same way
you do. Could you please describe it in more detail?

Thanks.

On Wed, Aug 16, 2017 at 6:06 PM, Sergey Chugunov 
wrote:

> Ilya,
>
> I think the proposed change definitely makes sense.
>
> At the same time I think the scope of the ticket is too broad. It covers at
> least two different aspects of service grid functionality:
>
>- Very specific issue of service upgrade process which is caused by
>current design flaw (although it's not a bug).
>- Very high-level suggestions about improving upgrade process in
> general.
>
>
> I think it is better to separate these things. Lets firstly address item#1
> and then reiterate on #2.
>
> Managing services deployment in distributed system is a non-trivial task
> with a lot of options and different requirements; all changes and
> improvements must be designed thoughtfully.
>
> E.g. for the requirement from the ticket that all services under the same
> name must be of the same version: what if a user wants to test a new
> implementation transparently to the clients of the cluster?
> It would be convenient for that user to be able to redeploy only one
> instance of the service to the newer version (without touching other
> instances) and see if any client reports a problem.
>
> Also I'm familiar with an example when a system with service-like entities
> connected to it supported both upgrades and downgrades: it was possible to
> connect new versions of services to the "parent" system, send some work to
> them but in case of any issues with newer version it was always possible to
> quickly fall back to the previous one known to be stable.
> This use case isn't covered in your ticket at all although I think it is
> kind of obvious feature.
>
> From my point of view Ignite just doesn't have necessary internal
> abstractions to support rich service functionality with managing versions,
> upgrades/downgrades and so on.
> Something like distributed ServiceRegistry concept with managing API to the
> user. We don't have anything like this now.
>
> So I think we should focus on addressing existing issue described in item#1
> and start a new discussion about ways to improve our service grid
> capabilities in a separate thread.
> Item#2 will be addressed automatically as part of that discussion.
>
> Makes sense?
>
> Thanks,
> Sergey.
>
> On Wed, Aug 16, 2017 at 2:22 AM, Denis Magda  wrote:
>
> > Ilya,
> >
> > Every Service Grid user will welcome this feature. Fully for it.
> >
> > Mentioned in the ticket that it has to be documented before the ticket is
> > closed.
> >
> > —
> > Denis
> >
> > > On Aug 15, 2017, at 8:18 AM, Ilya Lantukh 
> wrote:
> > >
> > > Igniters,
> > >
> > > Our current ServiceGrid implementation lacks several important
> features,
> > > one of which is ability to upgrade Service without downtime.
> > >
> > > I've created ticket to add this feature:
> > > https://issues.apache.org/jira/browse/IGNITE-6069.
> > >
> > > To implement it, the following problems must be solved:
> > > - currently we can store only one BinaryMetadata instance for given
> > > classname - if you change Service class implementation and then try to
> > > deploy it, you might get an exception like
> > > "org.apache.ignite.binary.BinaryObjectException: Binary type has
> > different
> > > field types". It can be solved by making (className, version) unique
> > > metadata identifier. We can use serialVersionUuid as version.
> > > - ServiceProxy must be aware of actual version and know if service is
> > > currently being upgraded. If user tries to execute any method during
> > > upgrade, proxy should implicitly wait until new version is ready. We
> > > already have similar logic in IgniteCacheProxyImpl.
> > > - To effectively and conveniently migrate service state to newer
> version,
> > > we should add method to Service interface that will be executed before
> > > start if older version was present. To keep API compatible, I suggest
> to
> > > introduce interface 

[jira] [Created] (IGNITE-6108) Hangs in streamer when using store

[Aleksey Chetaev (JIRA)]

Aleksey Chetaev created IGNITE-6108:
---

 Summary: Hangs in streamer when using store
 Key: IGNITE-6108
 URL: https://issues.apache.org/jira/browse/IGNITE-6108
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Aleksey Chetaev
Priority: Critical


I have hangs in IgniteStreamer benchmarks when using store with WAL mode 
different from NONE. 
Configuration: 1 client 4 servers.Cache mode:  transaction. Range 400_000_000. 
Problems: 
* Time for next 100_000_000 entries every is always greater than for the 
previous one.
* We can found hangs for greater that 1 minutes in drivers logs for example 
11:47:21 - 11:48:27 in archive named "log_with_memory_policy".

Yardstick logs in attachments. 



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

Re: Failure to deserialize simple model object

[kukushal .]

This is a suggested fix:
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-269

On Fri, Aug 18, 2017 at 12:15 PM, kukushal . 
wrote:

> I am fixing this issue: https://issues.apache.org/jira/browse/IGNITE-5966?
> filter=-1
> Reviewing it with Vladimir Ozerov and Sergey Chugunov:
> --
> ПРОБЛЕМА
> “get” не работает для данных загруженных из cache store
> ROOT CAUSE
> There two separate type information stores: metadata store backed by the
> file system and binary marshaller’s “type ID -> type name” store. Binary
> marshaller use the latter one when deserialising objects.
> BinaryObjectBuilderImpl used by the CacheJdbcPojoStore updates only
> metadata store but not the marshaller mappings cache. Thus we get this
> issue described in the ticket.
> SOLUTION
> Update BinaryObjectBuilderImpl to add type mapping to the marshaller cache.
>
> On Fri, Aug 18, 2017 at 1:41 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Guys,
>>
>> Does anyone has ideas?
>>
>> -Val
>>
>> On Mon, Aug 14, 2017 at 4:33 PM, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>>
>>> Cross-posting to dev
>>>
>>> Folks,
>>>
>>> I'm confused by the issue discussed in this thread.
>>>
>>> Here is the scenario:
>>> - Start server node with a cache with POJO store configured. There is
>>> one type declared, read-through enabled.
>>> - Start client node and execute get() for a key that exists in
>>> underlying DB.
>>> - During deserialization on the client, 'Requesting mapping from grid
>>> failed for' exception is thrown.
>>>
>>> Specifying the type explicitly in BinaryConfiguration solves the issue,
>>> and I think I understand technical reasons for this. But is this really
>>> expected? Is it possible to fix the issue without requiring to provide this
>>> configuration?
>>>
>>> I thought we do not require to provide types in configuration as long as
>>> there is only one platform involved, am I wrong? If yes, we need to
>>> identify scenarios when this documentation is required and document them.
>>>
>>> -Val
>>>
>>> On Mon, Aug 14, 2017 at 4:23 AM, franck102  wrote:
>>>
 My bad, here is the whole project.

 Franck ignite-binary-sample.zip
 



 --
 View this message in context: http://apache-ignite-users.705
 18.x6.nabble.com/Failure-to-deserialize-simple-model-object-
 tp15440p16158.html
 Sent from the Apache Ignite Users mailing list archive at Nabble.com.

>>>
>>>
>>
>
>
> --
> Best regards,
> Alexey
>



-- 
Best regards,
Alexey

[jira] [Created] (IGNITE-6107) GridFunc.first(list) throws NPE for null arg, but GridFunc.first(iterable) returns null

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-6107:


 Summary: GridFunc.first(list) throws NPE for null arg, but 
GridFunc.first(iterable) returns null
 Key: IGNITE-6107
 URL: https://issues.apache.org/jira/browse/IGNITE-6107
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.1
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.2


GridFunc.first(list) should return null in case of null argument.



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

Re: Failure to deserialize simple model object

[kukushal .]

I am fixing this issue:
https://issues.apache.org/jira/browse/IGNITE-5966?filter=-1
Reviewing it with Vladimir Ozerov and Sergey Chugunov:
--
ПРОБЛЕМА
“get” не работает для данных загруженных из cache store
ROOT CAUSE
There two separate type information stores: metadata store backed by the
file system and binary marshaller’s “type ID -> type name” store. Binary
marshaller use the latter one when deserialising objects.
BinaryObjectBuilderImpl used by the CacheJdbcPojoStore updates only
metadata store but not the marshaller mappings cache. Thus we get this
issue described in the ticket.
SOLUTION
Update BinaryObjectBuilderImpl to add type mapping to the marshaller cache.

On Fri, Aug 18, 2017 at 1:41 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Guys,
>
> Does anyone has ideas?
>
> -Val
>
> On Mon, Aug 14, 2017 at 4:33 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Cross-posting to dev
>>
>> Folks,
>>
>> I'm confused by the issue discussed in this thread.
>>
>> Here is the scenario:
>> - Start server node with a cache with POJO store configured. There is one
>> type declared, read-through enabled.
>> - Start client node and execute get() for a key that exists in underlying
>> DB.
>> - During deserialization on the client, 'Requesting mapping from grid
>> failed for' exception is thrown.
>>
>> Specifying the type explicitly in BinaryConfiguration solves the issue,
>> and I think I understand technical reasons for this. But is this really
>> expected? Is it possible to fix the issue without requiring to provide this
>> configuration?
>>
>> I thought we do not require to provide types in configuration as long as
>> there is only one platform involved, am I wrong? If yes, we need to
>> identify scenarios when this documentation is required and document them.
>>
>> -Val
>>
>> On Mon, Aug 14, 2017 at 4:23 AM, franck102  wrote:
>>
>>> My bad, here is the whole project.
>>>
>>> Franck ignite-binary-sample.zip
>>> >> ignite-binary-sample.zip>
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/Failure-to-deserialize-simple-model-object-
>>> tp15440p16158.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>


-- 
Best regards,
Alexey

[jira] [Created] (IGNITE-6106) Web console: New function descriptions on homepage carousel and getting started dialog

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-6106:
-

 Summary: Web console: New function descriptions on homepage 
carousel and getting started dialog
 Key: IGNITE-6106
 URL: https://issues.apache.org/jira/browse/IGNITE-6106
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 2.1
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
Priority: Minor






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

Re: Ignite: configuration changes at runtime

[Yakov Zhdanov]

Here is the list of params that can be changed - https://cwiki.apache.org/
confluence/display/IGNITE/Allow+Configuration+Settings+Change+At+Runtime

>No, the Ignite configuration is what Ignite receives on startup. Runtime
>changes are outside of configuration, especially given that if cluster
>restarts, they are likely lost.

Again, how you provide all-in-one-place current node configuration? Also,
why changes should be lost? In case of persistence they should not be lost,
moreover, nodes joining with previous configuration should pick up current
properties of running nodes.

>I think providing API is important for users who want to integrate Ignite
>with their own management tools.

This maybe done via JMX. Currently, I guess we expose only configuration
toString() via it.

--Yakov

Re: How a new index is built in runtime?

[Yakov Zhdanov]

Of course, iteration should have an option to be run from more than 1
thread. What will really help, IMO, is ability to insert presorted batches
in a single tree operation.

--
Yakov Zhdanov