Re: Ignite Marshalling & Serialization

[Valentin Kulichenko]

Hi John,

These are synonyms from Ignite perspective.

-Val

On Fri, Jan 12, 2018 at 11:43 AM, John Wilson 
wrote:

> Hi,
>
> Ignite marshals data before it writes it to the off-heap data regions. Can
> someone please explain to me the difference between marshaling and
> serialization, in the context of Ignite?
>
> Thanks,
>

Re: Apache Ignite 2.4 release

[Denis Magda]

Here is the page create before:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 


This is good news. It will be perfect if we also release as many "required 
tickets" as we can:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 


My favorite is memory metrics in bytes: 
https://issues.apache.org/jira/browse/IGNITE-6902 


The discussion lists are flooded with the demands for this essential 
capability. Who is going to review it?

-
Denis

> On Jan 12, 2018, at 11:22 AM, Dmitriy Setrakyan  wrote:
> 
> +1
> 
> Do we have a list of features for 2.4 documented anywhere?
> 
> D.
> 
> On Fri, Jan 12, 2018 at 7:43 AM, Pavel Tupitsyn 
> wrote:
> 
>> +1
>> 
>> But some stuff is not yet in master (like baseline topology), so it is too
>> soon to create a branch, I think.
>> 
>> Pavel
>> 
>> On Fri, Jan 12, 2018 at 5:31 PM, Vladimir Ozerov 
>> wrote:
>> 
>>> Igniters,
>>> 
>>> A number of major improvements have been made (or being finalized at the
>>> moment) to Ignite since recent 2.3 release. This includes baseline
>>> topology, new DDL commands, migration to Java 8 and Java 9 support,
>>> critical performance improvements to WAL, etc..
>>> 
>>> I think it makes sense to make a new release. What do you think if we
>>> release AI 2.4 with all this great stuff by the end of Jan?
>>> 
>>> If there are no objections, I'll create a branch to start stabilization
>>> process.
>>> 
>>> Vladimir.
>>> 
>> 

[jira] [Created] (IGNITE-7405) Distributed MLP cleanup/refactoring phase 2

[Artem Malykh (JIRA)]

Artem Malykh created IGNITE-7405:


 Summary: Distributed MLP cleanup/refactoring phase 2
 Key: IGNITE-7405
 URL: https://issues.apache.org/jira/browse/IGNITE-7405
 Project: Ignite
  Issue Type: Bug
  Components: ml
Affects Versions: 2.4
Reporter: Artem Malykh
Assignee: Artem Malykh
 Fix For: 2.4


All refactoring which is not done in 
https://issues.apache.org/jira/browse/IGNITE-7350.



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

Re: Thin Client examples for documentation

[Denis Magda]

> We need to make sure the spec is correct, so someone else (not me) has to
> follow the spec, write code and see if it works.
> It helps finding issues like missing 27 code, etc.

Exactly, Pavel! We’re on the same page here. Thanks for the help and 
responsiveness.

—
Denis

> On Jan 12, 2018, at 3:08 AM, Pavel Tupitsyn  wrote:
> 
> Hi Prachi,
> 
> I've forked your repo, my changes are there:
> https://github.com/ptupitsyn/ignite-examples/blob/fix/src/main/java/ignite/myexamples/thinclient/ThinClientExample2.java
>  
> 
> 
> * getOrCreateCache fixed
> * 27: documentation updated, I've forgot about wrapped complex objects
> * Common readBinaryObject method added, you can extend it further. Works
> with doSQLQuery
> * getQueryCursorPage: fixed by using readBinaryObject method
> * putBinaryType: Fixed that for you. Request length was wrong, and some
> extra data in the schema.
> * doQueryScan: filter object is a Java object
> implementing IgniteBiPredicate, serialized as BinaryObject.
> 
> I could write all the code for you, but that does not make sense.
> We need to make sure the spec is correct, so someone else (not me) has to
> follow the spec, write code and see if it works.
> It helps finding issues like missing 27 code, etc.
> 
> Thanks,
> Pavel
> 
> 
> 
> On Fri, Jan 12, 2018 at 4:57 AM, Prachi Garg  > wrote:
> 
>> The question was incomplete for one of the points :-)
>> 
>> 
>>   - doQueryScan() - I could not create a proper request.  If I want to
>>  scan for records where salary>1000, then what is the filter object
>>  in the request? Where is the query in the request?
>> 
>> 
>> On Thu, Jan 11, 2018 at 5:47 PM, Prachi Garg  wrote:
>> 
>>> Hi Pavel,
>>> 
>>> Thanks for your input. I have already used the debugger for several other
>>> operations :-) However, these 4 are giving me a hard time. Now as you
>>> suggested -
>>> 
>>>   1. I have created separate methods for request and response header,
>>>   and writeString. The code is much cleaner now.
>>>   2. I have tried to debug on the server side, but they all have
>>>   different issues -
>>> 
>>> 
>>>   - doSQLQuery() - Request is fine, but in response I get 27 as the
>>>  type code for value which is not mentioned in the wiki doc.
>>>  - getQueryCursorPage() - Request is fine, but response is some
>>>  lengthy numbers.
>>>  - putBinaryType() - I could not create a proper request. From the
>>>  wiki docs, it is unclear what "Binary schemas, set of (schemaId + 
>>> fieldIds)
>>>  pairs"
>>>  - doQueryScan() - I could not create a proper request. What is
>>>  filter object in the request?
>>> 
>>> Please go through the above 4 methods and fix the issues. I need your
>>> help to finish this doc before the release.
>>> 
>>> Also, until I get OP_QUERY_SCAN and OP_PUT_BINARY_TYPE working, I cannot
>>> write examples for OP_QUERY_SCAN_CURSOR_GET_PAGE and OP_GET_BINARY_TYPE.
>>> 
>>> Thanks,
>>> -P
>>> 
>>> On Thu, Jan 11, 2018 at 7:36 AM, Pavel Tupitsyn 
>>> wrote:
>>> 
 Hi Prachi,
 
 I've fixed cache creation method for you, see attachment. I did not fix
 anything else.
 Sorry, but this kind of code with hardcoded message lengths, operation
 codes, etc is very hard to work with.
 Hardcoded values may be useful for trivial operations so that users get
 an idea of the protocol.
 But for complex stuff like SQL this gets out of hand quickly.
 
 My recommendations:
 - Create a common SendRequest method which will deal with message
 lengths, op codes and request ids automatically
 - Create writeString method to deal with UTF stuff in one place
 - When something does not work, use debugger on the server side
 (see ClientMessageParser class), it is easy to step through and see which
 value went wrong
 
 Thanks,
 Pavel
 
 On Wed, Jan 10, 2018 at 11:58 PM, Denis Magda  wrote:
 
> Pavel, as a side note,
> 
> The methods/operations Prachi is struggling with look pretty standard
> to me.
> 
> Do you have tests for them in the code base? I mean *not* the tests you
> shared before where we use existing internal binary marshaller APIs but
> where we code every operation from scratch (what Prachi is doing for
> documentation code snippets).
> 
> Such tests would help to complete the doc quicker and would ensure that
> the protocol works as expected on the user side where people are not going
> to sit on the internal binary marshaller apis.
> 
> —
> Denis
> 
>> On Jan 10, 2018, at 12:29 PM, Prachi Garg  wrote:
>> 
>> Pavel,
>> 
>> I am having trouble creating examples for some of 

[jira] [Created] (IGNITE-7404) Use various backgrounds for Ignite main page's main blocks

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7404:
---

 Summary: Use various backgrounds for Ignite main page's main blocks
 Key: IGNITE-7404
 URL: https://issues.apache.org/jira/browse/IGNITE-7404
 Project: Ignite
  Issue Type: Task
  Components: site
Reporter: Denis Magda
Assignee: Vica Abramova
 Fix For: 2.4


This ticket is intended to improve the main page:
https://ignite.apache.org

All the content that goes below the banner is shown on a *white* background. As 
a result, it's difficult to separate main building blocks from each other 
*visually*.

Suggest to come up with a second background and rotate it together with the 
white one among the building blocks. For instance:
- Apache Ignite definition and use cases (white)
- Features (new background - probably grey)
- How Ignite compares (white)
- Screencast (new background)
- News (white)



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

[jira] [Created] (IGNITE-7403) Improve content on What's Ignite page

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7403:
---

 Summary: Improve content on What's Ignite page
 Key: IGNITE-7403
 URL: https://issues.apache.org/jira/browse/IGNITE-7403
 Project: Ignite
  Issue Type: Task
  Components: site
Affects Versions: 2.4
Reporter: Denis Magda
Assignee: Vica Abramova


A proposed of a new draft for the What's Ignite page:
https://ignite.apache.org/whatisignite-2.html

The goal is to make the page more informative and tell about the main things of 
Ignite or provide references to them. Overall, the structure should be as 
follows:
- Product name and definition.
- Diagram.
- Features and Benefits
- Ignite facts




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

Ignite Marshalling & Serialization

[John Wilson]

Hi,

Ignite marshals data before it writes it to the off-heap data regions. Can
someone please explain to me the difference between marshaling and
serialization, in the context of Ignite?

Thanks,

[GitHub] ignite pull request #3369: IGNITE-6923 Cache metrics optimization

[alex-plekhanov]

GitHub user alex-plekhanov opened a pull request:

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

IGNITE-6923 Cache metrics optimization



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

$ git pull https://github.com/alex-plekhanov/ignite IGNITE-6923

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

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


commit eef3fed408d7cfbeedcabcb354989c64be773724
Author: Aleksey Plekhanov 
Date:   2017-12-19T14:44:06Z

IGNITE-6923 Optimized nonHeapMemoryUsed

commit 122467d0ca4cfe859e2fc5af276b20c4f50dc89c
Author: Aleksey Plekhanov 
Date:   2017-12-20T16:13:34Z

IGNITE-6923 getTotalPartitionsCount, getRebalancingPartitionsCount 
optimization

commit e20d842f9ccf9c4d1e4703a52cd723d8e37ddbea
Author: Aleksey Plekhanov 
Date:   2017-12-22T08:56:36Z

IGNITE-6923 Cluster metrics optimization (proxy class implemented)

commit bff0a1845799ad90c6ecdd3812e84418ba45bd07
Author: Aleksey Plekhanov 
Date:   2017-12-25T08:40:24Z

IGNITE-6923 Partitions metrics optimization

commit 6dd59b9961f9fc073d4616367e36607430f113b8
Author: Aleksey Plekhanov 
Date:   2017-12-26T12:57:01Z

IGNITE-6923 Cache metrics optimization

commit 96b0396f05c7aacb24bd9ee88e2564d240fae0be
Author: Aleksey Plekhanov 
Date:   2017-12-26T12:58:30Z

IGNITE-6923 Cache metrics optimization

commit 79067428f7252700bb23d29f3e3b4b7dfa5586bf
Author: Aleksey Plekhanov 
Date:   2017-12-27T07:48:56Z

IGNITE-6923 Disable cache metrics update flag

commit 5e5d675f6fb6a25eda57fcbf53e49ec87fda3ba2
Author: Aleksey Plekhanov 
Date:   2017-12-27T08:07:57Z

IGNITE-6923 License header

commit e90d778d9fab0b1e467ef1314505060494fea1db
Author: Aleksey Plekhanov 
Date:   2018-01-11T20:57:29Z

IGNITE-6923 Bugfix

commit 77e50a74dadc6ae40d301f63cd0e4b73b6203303
Author: Aleksey Plekhanov 
Date:   2018-01-12T14:43:29Z

IGNITE-6923 Unit test

commit 39f7c653e8b91ec7b02244e2633e27ea9103793d
Author: Aleksey Plekhanov 
Date:   2018-01-12T14:47:35Z

Revert "IGNITE-6923 Disable cache metrics update flag"

This reverts commit 9bb904f

commit 62ea9f5d6524eff6e9a69fbc8ca2ac0c95325796
Author: Aleksey Plekhanov 
Date:   2018-01-12T19:24:57Z

IGNITE-6923 Test comment added




---

Re: Apache Ignite 2.4 release

[Dmitriy Setrakyan]

+1

Do we have a list of features for 2.4 documented anywhere?

D.

On Fri, Jan 12, 2018 at 7:43 AM, Pavel Tupitsyn 
wrote:

> +1
>
> But some stuff is not yet in master (like baseline topology), so it is too
> soon to create a branch, I think.
>
> Pavel
>
> On Fri, Jan 12, 2018 at 5:31 PM, Vladimir Ozerov 
> wrote:
>
> > Igniters,
> >
> > A number of major improvements have been made (or being finalized at the
> > moment) to Ignite since recent 2.3 release. This includes baseline
> > topology, new DDL commands, migration to Java 8 and Java 9 support,
> > critical performance improvements to WAL, etc..
> >
> > I think it makes sense to make a new release. What do you think if we
> > release AI 2.4 with all this great stuff by the end of Jan?
> >
> > If there are no objections, I'll create a branch to start stabilization
> > process.
> >
> > Vladimir.
> >
>

[jira] [Created] (IGNITE-7402) Add ODBC security support

[Blackfield (JIRA)]

Blackfield created IGNITE-7402:
--

 Summary: Add ODBC security support
 Key: IGNITE-7402
 URL: https://issues.apache.org/jira/browse/IGNITE-7402
 Project: Ignite
  Issue Type: Improvement
  Components: odbc
Affects Versions: 2.3
Reporter: Blackfield


ODBC driver does not support username password to be passed to security plugin 
in.

Please enable end user to provide user name and password.

The DSN info on Windows is stored in registry as plain text. The password 
should NOT be stored as plain text (e.g. encrypted).

See Ignite-6941 for the JDBC counter part.



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

[GitHub] ignite pull request #3292: IGNITE-6923 Optimize metrics calculation

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

Re: IGNITE-6853: Cassandra cache store does not clean prepared statements cache when remove old cassandra session

[Denis Magda]

Just for the records.

Igor replied and reviewed the changes:
https://issues.apache.org/jira/browse/IGNITE-6853 


—
Denis

> On Jan 11, 2018, at 9:13 AM, Igor Rudyak  wrote:
> 
> Hi Denis, Jason
> 
> Sorry just found your email regarding IGNITE-6853. It's being a long 
> Christmas holiday and your email got lost among tons of other emails. 
> 
> Anyway, I'll look at this PR: 
> https://github.com/apache/ignite/pull/3088/files 
> 
> 
> Igor
>  
> 
> On Wed, Dec 20, 2017 at 10:15 PM, Denis Magda  > wrote:
> Hi Igor,
> 
> Could you please do the review by the end of the year? It will be great to 
> include the fix into 2.4.
> 
> —
> Denis
> 
>> Begin forwarded message:
>> 
>> From: Denis Magda >
>> Subject: Re: IGNITE-6853: Cassandra cache store does not clean prepared 
>> statements cache when remove old cassandra session
>> Date: December 20, 2017 at 10:14:33 PM PST
>> To: dev@ignite.apache.org , Igor Rudyak 
>> >
>> 
>> Hi Jason,
>> 
>> Thanks for fixing the bug! Please assign the ticket on yourself, move it to 
>> “PATCH AVAILABLE” state and run Cassandra specific tests on TeamCity. More 
>> on this can be found here:
>> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforReview
>>  
>> 
>> 
>> Igor Rudyak (copied) is a main maintainer. Igor, would you mind checking the 
>> patch and explain how to test the integration on TeamCity (if needed)?
>> 
>> —
>> Denis
>> 
>>> On Dec 20, 2017, at 10:08 PM, Jason Man, CLSA >> > wrote:
>>> 
>>> Hi Igniters,
>>> 
>>> I've got a PR to resolve this JIRA available:
>>> 
>>> https://issues.apache.org/jira/browse/IGNITE-6853 
>>> 
>>> https://github.com/apache/ignite/pull/3088 
>>> 
>>> 
>>> The JIRA was tagged previously with fix version = 2.4
>>> 
>>> May I know what is the process to move things forward?  (The PR has been 
>>> created 3 weeks ago).  I'm hoping this fix would be included in 2.4 
>>> release. 
>>> 
>>> Thanks.
>>> Jason  
>>> The content of this communication is intended for the recipient and is 
>>> subject to CLSA Legal and Regulatory Notices.
>>> These can be viewed at https://www.clsa.com/disclaimer.html 
>>>  or sent to you upon request.
>>> CLSA is ISO14001 certified and committed to reducing environmental impact.
>> 
> 
> 

[jira] [Created] (IGNITE-7401) Entry can be expired even if it doesn't define expiry policy in "putWithPolicy-then-put" scenario

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-7401:
---

 Summary: Entry can be expired even if it doesn't define expiry 
policy in "putWithPolicy-then-put" scenario
 Key: IGNITE-7401
 URL: https://issues.apache.org/jira/browse/IGNITE-7401
 Project: Ignite
  Issue Type: Bug
Reporter: Andrey Gura


Entry can be expired even if it doesn't define expiry policy in 
"putWithPolicy-then-put" scenario. The following test case demonstrate the 
problem.

{code:java}
public void testPutWithTtlThenPut() throws Exception {
Ignite ignite = startGrid();

try {
IgniteCache cache = ignite.cache("cache");

CreatedExpiryPolicy expiryPlc = new CreatedExpiryPolicy(new 
Duration(TimeUnit.MILLISECONDS, 10));

IgniteCache cacheTtl = 
cache.withExpiryPolicy(expiryPlc);

cacheTtl.put("key", "v1");
cache.put("key", "v2");

U.sleep(10);

assertEquals("v2", cache.get("key")); // Fill fail (flaky)
}
finally {
stopAllGrids();
}
}
{code}



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

[GitHub] ignite pull request #3368: IGNITE-7350: Distributed MLP cleanup/refactoring.

[artemmalykh]

GitHub user artemmalykh opened a pull request:

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

IGNITE-7350: Distributed MLP cleanup/refactoring.



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

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

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

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


commit 995d781b58b57c4721b3fd92d3867975d652272a
Author: Artem Malykh 
Date:   2018-01-12T13:22:21Z

IGNITE-7397: Fix cache configuration and reduced trainings count in MLP 
group training test.

commit 123f14ccc8b8c0e27104061b4644876b45a8a123
Author: Artem Malykh 
Date:   2018-01-12T13:23:02Z

Merge branch 'master-apache' into ignite-7397

commit b2cfa9017b69b8ebfd2bca4143c91315c1fd3a06
Author: Artem Malykh 
Date:   2018-01-12T15:15:01Z

IGNITE-7350: Moved update calculators from nn package to optimization.

commit 32de402cd6939aba24cec572e42ddc8d90dc3251
Author: Artem Malykh 
Date:   2018-01-12T15:24:33Z

IGNITE-7350: Moved LossFunctions, fixed some comments.

commit eb1ceb580c418ec91c3e5b42585132b15073aa97
Author: Artem Malykh 
Date:   2018-01-12T16:03:26Z

IGNITE-7350: Removed in-place changing of update and model in Nesterov 
update calculator.

commit e5d3299c6b344fb2b9c54b6f578cdda2739c7ffa
Author: Artem Malykh 
Date:   2018-01-12T16:07:31Z

IGNITE-7350: Default implementation for 'withParameters'.

commit b0dc57dcf8e717def820806dab62d50715de02f6
Author: Artem Malykh 
Date:   2018-01-12T16:11:26Z

IGNITE-7350: Moved some files to appropriate packages.




---

Re: Apache Ignite 2.4 release

[Pavel Tupitsyn]

+1

But some stuff is not yet in master (like baseline topology), so it is too
soon to create a branch, I think.

Pavel

On Fri, Jan 12, 2018 at 5:31 PM, Vladimir Ozerov 
wrote:

> Igniters,
>
> A number of major improvements have been made (or being finalized at the
> moment) to Ignite since recent 2.3 release. This includes baseline
> topology, new DDL commands, migration to Java 8 and Java 9 support,
> critical performance improvements to WAL, etc..
>
> I think it makes sense to make a new release. What do you think if we
> release AI 2.4 with all this great stuff by the end of Jan?
>
> If there are no objections, I'll create a branch to start stabilization
> process.
>
> Vladimir.
>

[jira] [Created] (IGNITE-7400) OptimizedMarshallerIndexNameTest doesn't kill the grid after the test

[Kirill Shirokov (JIRA)]

Kirill Shirokov created IGNITE-7400:
---

 Summary: OptimizedMarshallerIndexNameTest doesn't kill the grid 
after the test
 Key: IGNITE-7400
 URL: https://issues.apache.org/jira/browse/IGNITE-7400
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.4
Reporter: Kirill Shirokov
Assignee: Kirill Shirokov






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

Re: Spring3 support

[Michael Cherkasov]

Hi Val,

>What are the features that depend on Spring 4?
at least this one breaks compatibility for sure with spring3:
https://github.com/gridgain/apache-ignite/commit/
dde348607ed266f87bf594cb2a221ec39d84cfdb

Thanks,
Mike.

2018-01-12 2:32 GMT+03:00 Valentin Kulichenko :

> Mike,
>
> What are the features that depend on Spring 4?
>
> -Val
>
> On Thu, Jan 11, 2018 at 12:42 PM, Michael Cherkasov <
> michael.cherka...@gmail.com> wrote:
>
> > Hi all,
> >
> > I want to integrate the following change:
> > https://github.com/apache/ignite/pull/3147/
> >
> > It adds spring3 support.
> >
> > With Ignite versions older 2.1 you can to force maven to use sprint3
> > dependency and everything would work fine.
> > With newer versions this doesn't work, because now Ignite uses spring4
> > specific features and spring3 and ignite 2.1+ don't work simultaneously
> on
> > one project.
> >
> > If you need ignite 2.1+ you have to update spring in your project to
> > version 4 at least, however, it isn't always possible to do so.
> > So I want to add a new module that has no spring4 specific features and
> > itself depends on spring3, with this module you don't even need to force
> > maven to use specific spring version, you just can import ignite-spring3
> > and that's it.
> >
> > This will allow updating ignite version in legacy apps easier and
> increase
> > ignite 2+ adaptation.
> >
> > Any thoughts? Objections?
> >
> > Thanks,
> > Mike.
> >
>

Apache Ignite 2.4 release

[Vladimir Ozerov]

Igniters,

A number of major improvements have been made (or being finalized at the
moment) to Ignite since recent 2.3 release. This includes baseline
topology, new DDL commands, migration to Java 8 and Java 9 support,
critical performance improvements to WAL, etc..

I think it makes sense to make a new release. What do you think if we
release AI 2.4 with all this great stuff by the end of Jan?

If there are no objections, I'll create a branch to start stabilization
process.

Vladimir.

[jira] [Created] (IGNITE-7399) .NET: Thin client: NullRefException when connection to arbitrary server

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7399:
--

 Summary: .NET: Thin client: NullRefException when connection to 
arbitrary server
 Key: IGNITE-7399
 URL: https://issues.apache.org/jira/browse/IGNITE-7399
 Project: Ignite
  Issue Type: Bug
  Components: platforms, thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Reproducer:

{code}
var cfg = new IgniteClientConfiguration { Host = "ya.ru", Port=80 };
var client = Ignition.StartClient(cfg);
{code}

Result:
{code}
Object reference not set to an instance of an object.
at Apache.Ignite.Core.Impl.Client.ClientSocket.Dispose()
   at Apache.Ignite.Core.Impl.Client.ClientSocket.ReceiveBytes(Int32 size)
   at 
Apache.Ignite.Core.Impl.Client.ClientSocket.Handshake(ClientProtocolVersion 
version)
   at 
Apache.Ignite.Core.Impl.Client.ClientSocket..ctor(IgniteClientConfiguration 
clientConfiguration, Nullable`1 version)
   at 
Apache.Ignite.Core.Impl.Client.IgniteClient..ctor(IgniteClientConfiguration 
clientConfiguration)
   at Apache.Ignite.Core.Ignition.StartClient(IgniteClientConfiguration 
clientConfiguration)
{code}



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

[GitHub] ignite pull request #3367: Ignite-7397: Fix wrong cache configuration for ML...

[artemmalykh]

GitHub user artemmalykh opened a pull request:

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

Ignite-7397: Fix wrong cache configuration for MLP training data.



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

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

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

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


commit 995d781b58b57c4721b3fd92d3867975d652272a
Author: Artem Malykh 
Date:   2018-01-12T13:22:21Z

IGNITE-7397: Fix cache configuration and reduced trainings count in MLP 
group training test.

commit 123f14ccc8b8c0e27104061b4644876b45a8a123
Author: Artem Malykh 
Date:   2018-01-12T13:23:02Z

Merge branch 'master-apache' into ignite-7397




---

[GitHub] ignite pull request #3366: ignite-7396: fixed NullPointerException

[sk0x50]

GitHub user sk0x50 opened a pull request:

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

ignite-7396: fixed NullPointerException

In case of a newly joined node does not specify 
ATTR_DATA_REGIONS_OFFHEAP_SIZE via node attributes, IgniteUtils.offheapSize() 
throws NullPointerException

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

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

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

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


commit 769348dbb4db5be315ee497a71233b4b398cecc6
Author: Slava Koptilin 
Date:   2018-01-12T13:19:04Z

ignite-7396: fixed NPE




---

[GitHub] ignite pull request #3365: Ignite-7380:

[dspavlov]

GitHub user dspavlov opened a pull request:

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

Ignite-7380: 



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

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

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

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


commit e7ca9b65a68de7752195c8f4d2b5180f3c77d19f
Author: Dmitriy Govorukhin 
Date:   2017-11-13T18:52:47Z

ignite-blt-merge -> ignite-2.4.1

commit cc8168fc184bb7f5e3cc3bbb0743397097f78bfb
Author: Dmitriy Govorukhin 
Date:   2017-11-13T19:13:01Z

merge ignite-pitr-rc1 -> ignite-2.4.1

commit 87e6d74cf6a251c7984f9e68c391f790feccc281
Author: Dmitriy Govorukhin 
Date:   2017-11-14T12:49:33Z

ignite-gg-12877 Compact consistent ID in WAL

commit 9f5a22711baea05bd37ab07c8f928a4837dd83a4
Author: Ilya Lantukh 
Date:   2017-11-14T14:12:28Z

Fixed javadoc.

commit d5af2d78dd8eef8eca8ac5391d31d8c779649bb0
Author: Alexey Kuznetsov 
Date:   2017-11-15T08:09:00Z

IGNITE-6913 Baseline: Added new options to controls.sh for baseline 
manipulations.

commit 713924ce865752b6e99b03bd624136541cea5f9f
Author: Sergey Chugunov 
Date:   2017-11-15T09:03:12Z

IGNITE-5850 failover tests for cache operations during BaselineTopology 
changes

commit b65fd134e748d496f732ec2aa0953a0531f544b8
Author: Ilya Lantukh 
Date:   2017-11-15T12:54:35Z

TX read logging if PITR is enabled.

commit 9b2a567c0e04dc33116b51f88bee75f76e9107d1
Author: Ilya Lantukh 
Date:   2017-11-15T13:45:16Z

TX read logging if PITR is enabled.

commit 993058ccf0b2b8d9e80750c3e45a9ffa31d85dfa
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:51:54Z

ignite-2.4.1 optimization for store full set node more compacted

commit 1eba521f608d39967aec376b397b7fc800234e54
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:52:22Z

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

commit 564b3fd51f8a7d1d81cb6874df66d0270623049c
Author: Sergey Chugunov 
Date:   2017-11-15T14:00:51Z

IGNITE-5850 fixed issue with initialization of data regions on node 
activation, fixed issue with auto-activation when random node joins inactive 
cluster with existing BLT

commit c6d1fa4da7adfadc80abdc7eaf6452b86a4f6aa4
Author: Sergey Chugunov 
Date:   2017-11-15T16:23:08Z

IGNITE-5850 transitionResult is set earlier when request for changing 
BaselineTopology is sent

commit d65674363163e38a4c5fdd73d1c8d8e1c7610797
Author: Sergey Chugunov 
Date:   2017-11-16T11:59:07Z

IGNITE-5850 new failover tests for changing BaselineTopology up (new node 
added to topology)

commit 20552f3851fe8825191b144179be032965e0b5c6
Author: Sergey Chugunov 
Date:   2017-11-16T12:53:43Z

IGNITE-5850 improved error message when online node is removed from baseline

commit 108bbcae4505ac904a6db774643ad600bfb42c21
Author: Sergey Chugunov 
Date:   2017-11-16T13:45:52Z

IGNITE-5850 BaselineTopology should not change on cluster deactivation

commit deb641ad3bdbf260fa60ad6bf607629652e324bd
Author: Dmitriy Govorukhin 
Date:   2017-11-17T09:45:44Z

ignite-2.4.1 truncate wal and checkpoint history on move/delete snapshot

commit 3c8b06f3659af30d1fd148ccc0f40e216a56c998
Author: Alexey Goncharuk 
Date:   2017-11-17T12:48:12Z

IGNITE-6947 Abandon remap after single map if future is done (fixes NPE)

commit ba2047e5ae7d271a677e0c418375d82d78c4023e
Author: devozerov 
Date:   2017-11-14T12:26:31Z

IGNITE-6901: Fixed assertion during 
IgniteH2Indexing.rebuildIndexesFromHash. This closes #3027.

commit abfc0466d6d61d87255d0fe38cbdf11ad46d4f89
Author: Sergey Chugunov 
Date:   2017-11-17T13:40:57Z

IGNITE-5850 tests for queries in presence of BaselineTopology

commit f4eabaf2a905abacc4c60c01d3ca04f6ca9ec188
Author: Sergey Chugunov 
Date:   2017-11-17T17:23:02Z

IGNITE-5850 implementation for setBaselineTopology(long topVer) migrated 
from wc-251

commit 4edeccd3e0b671aa277f58995df9ff9935baa95a
Author: EdShangGG 
Date:   2017-11-17T18:21:17Z

GG-13074 Multiple snapshot test failures after baseline topology is 
introduced
-adding baseline test to suite
-fixing issues with baseline

commit edae228c8f55990c15ef3044be987dcb00d6c81a
Author: EdShangGG 
Date:   2017-11-18T10:36:41Z

hack with sleep

commit b5bffc7580a4a8ffbcc06f60c282e73979179578
Author: Ilya Lantukh 

[jira] [Created] (IGNITE-7398) InstanceNotFoundException appears in the log when a cache is closed and MBeans are disabled

[Stanislav Lukyanov (JIRA)]

Stanislav Lukyanov created IGNITE-7398:
--

 Summary: InstanceNotFoundException appears in the log when a cache 
is closed and MBeans are disabled
 Key: IGNITE-7398
 URL: https://issues.apache.org/jira/browse/IGNITE-7398
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.4
Reporter: Stanislav Lukyanov
Priority: Minor


If IGNITE_MBEANS_DISABLED is set to true, whenever a cache is started the 
following error is logged:
javax.management.InstanceNotFoundException: 
org.apache:clsLdr=18b4aac2,igniteInstanceName=mbeans.GridMBeanDisableSelfTest0,group=Cache
 groups,name=MyCache
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415)
at 
com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:606)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2264)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2253)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:907)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:872)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2316)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2182)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2512)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2475)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:362)
at org.apache.ignite.Ignition.stop(Ignition.java:224)
at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3509)
at 
org.apache.ignite.util.mbeans.GridMBeanDisableSelfTest.testCorrectMBeanInfo(GridMBeanDisableSelfTest.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
at java.lang.Thread.run(Thread.java:748)

That's because GridCacheProcessor::cleanup unconditionally attempts to 
unregister cache's MBean, not checking whether or not the cache actually has an 
MBean registered for it.



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

[jira] [Created] (IGNITE-7397) Fix wrong cache configuration for MLP training data

[Artem Malykh (JIRA)]

Artem Malykh created IGNITE-7397:


 Summary: Fix wrong cache configuration for MLP training data
 Key: IGNITE-7397
 URL: https://issues.apache.org/jira/browse/IGNITE-7397
 Project: Ignite
  Issue Type: Bug
Reporter: Artem Malykh


Replicated cache used in MLP group training should be configured as FULL_SYNC.



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

[jira] [Created] (IGNITE-7396) IgniteUtils.offheapSize may throw NullPointerException

[Vyacheslav Koptilin (JIRA)]

Vyacheslav Koptilin created IGNITE-7396:
---

 Summary: IgniteUtils.offheapSize may throw NullPointerException
 Key: IGNITE-7396
 URL: https://issues.apache.org/jira/browse/IGNITE-7396
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.4
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin


In case of a newly joined node does not specify 
{{ATTR_DATA_REGIONS_OFFHEAP_SIZE}} via node attributes, 
{{IgniteUtils.offheapSize()}} throws {{NullPointerException}}
{code}
[2018-01-11 
12:57:14,257][ERROR][disco-event-worker-#222%cache%][GridDiscoveryManager] 
Unexpected exception in discovery worker thread (ignored).
java.lang.NullPointerException
at 
org.apache.ignite.internal.util.IgniteUtils.offheapSize(IgniteUtils.java:1250)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.ackTopology(GridDiscoveryManager.java:1485)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.access$9500(GridDiscoveryManager.java:166)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2644)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2573)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}



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

[GitHub] ignite pull request #3359: ignite-6736 Unsafe.monitorEnter/Exit usages are r...

[agura]

Github user agura closed the pull request at:

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


---

IGNITE-6826 is ready for review (Change default DiscoverySpi ipFinder type for examples)

[Дмитрий Рябов]

Hello Igniters!
I’ve changed default ipFinder in examples from multicast to static, so
examples will run faster.
Please, review.

JIRA: https://issues.apache.org/jira/browse/IGNITE-6826
GitHub: https://github.com/apache/ignite/pull/3362
Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-454

Re: Thin Client examples for documentation

[Pavel Tupitsyn]

Hi Prachi,

I've forked your repo, my changes are there:
https://github.com/ptupitsyn/ignite-examples/blob/fix/src/main/java/ignite/myexamples/thinclient/ThinClientExample2.java

* getOrCreateCache fixed
* 27: documentation updated, I've forgot about wrapped complex objects
* Common readBinaryObject method added, you can extend it further. Works
with doSQLQuery
* getQueryCursorPage: fixed by using readBinaryObject method
* putBinaryType: Fixed that for you. Request length was wrong, and some
extra data in the schema.
* doQueryScan: filter object is a Java object
implementing IgniteBiPredicate, serialized as BinaryObject.

I could write all the code for you, but that does not make sense.
We need to make sure the spec is correct, so someone else (not me) has to
follow the spec, write code and see if it works.
It helps finding issues like missing 27 code, etc.

Thanks,
Pavel



On Fri, Jan 12, 2018 at 4:57 AM, Prachi Garg  wrote:

> The question was incomplete for one of the points :-)
>
>
>- doQueryScan() - I could not create a proper request.  If I want to
>   scan for records where salary>1000, then what is the filter object
>   in the request? Where is the query in the request?
>
>
> On Thu, Jan 11, 2018 at 5:47 PM, Prachi Garg  wrote:
>
>> Hi Pavel,
>>
>> Thanks for your input. I have already used the debugger for several other
>> operations :-) However, these 4 are giving me a hard time. Now as you
>> suggested -
>>
>>1. I have created separate methods for request and response header,
>>and writeString. The code is much cleaner now.
>>2. I have tried to debug on the server side, but they all have
>>different issues -
>>
>>
>>- doSQLQuery() - Request is fine, but in response I get 27 as the
>>   type code for value which is not mentioned in the wiki doc.
>>   - getQueryCursorPage() - Request is fine, but response is some
>>   lengthy numbers.
>>   - putBinaryType() - I could not create a proper request. From the
>>   wiki docs, it is unclear what "Binary schemas, set of (schemaId + 
>> fieldIds)
>>   pairs"
>>   - doQueryScan() - I could not create a proper request. What is
>>   filter object in the request?
>>
>> Please go through the above 4 methods and fix the issues. I need your
>> help to finish this doc before the release.
>>
>> Also, until I get OP_QUERY_SCAN and OP_PUT_BINARY_TYPE working, I cannot
>> write examples for OP_QUERY_SCAN_CURSOR_GET_PAGE and OP_GET_BINARY_TYPE.
>>
>> Thanks,
>> -P
>>
>> On Thu, Jan 11, 2018 at 7:36 AM, Pavel Tupitsyn 
>> wrote:
>>
>>> Hi Prachi,
>>>
>>> I've fixed cache creation method for you, see attachment. I did not fix
>>> anything else.
>>> Sorry, but this kind of code with hardcoded message lengths, operation
>>> codes, etc is very hard to work with.
>>> Hardcoded values may be useful for trivial operations so that users get
>>> an idea of the protocol.
>>> But for complex stuff like SQL this gets out of hand quickly.
>>>
>>> My recommendations:
>>> - Create a common SendRequest method which will deal with message
>>> lengths, op codes and request ids automatically
>>> - Create writeString method to deal with UTF stuff in one place
>>> - When something does not work, use debugger on the server side
>>> (see ClientMessageParser class), it is easy to step through and see which
>>> value went wrong
>>>
>>> Thanks,
>>> Pavel
>>>
>>> On Wed, Jan 10, 2018 at 11:58 PM, Denis Magda  wrote:
>>>
 Pavel, as a side note,

 The methods/operations Prachi is struggling with look pretty standard
 to me.

 Do you have tests for them in the code base? I mean *not* the tests you
 shared before where we use existing internal binary marshaller APIs but
 where we code every operation from scratch (what Prachi is doing for
 documentation code snippets).

 Such tests would help to complete the doc quicker and would ensure that
 the protocol works as expected on the user side where people are not going
 to sit on the internal binary marshaller apis.

 —
 Denis

 > On Jan 10, 2018, at 12:29 PM, Prachi Garg  wrote:
 >
 > Pavel,
 >
 > I am having trouble creating examples for some of the thin protocol
 > operations. I have uploaded my project on github -
 >
 > https://github.com/pgarg/ignite-examples/blob/master/src/mai
 n/java/ignite/myexamples/thinclient/ThinClientExample2.java
 >
 > Please look into the following methods and provide a fix for them:
 >
 >   - doSQLQuery()
 >   - getQueryCursorPage()
 >   - putBinaryType()
 >   - doQueryScan()
 >   - createCacheWithConfiguration()
 >
 > Thanks,
 > -Prachi


>>>
>>
>

[jira] [Created] (IGNITE-7395) Web console: improve list-editable scope variables access

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-7395:


 Summary: Web console: improve list-editable scope variables access
 Key: IGNITE-7395
 URL: https://issues.apache.org/jira/browse/IGNITE-7395
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Ilya Borisov
Assignee: Ilya Borisov
Priority: Minor


*The problem:*
The only way to access an item instance from inside list-editable transclusion 
slots is via _$parent.item_. This approach is both cumbersome and prone to 
$scope-related issues (i.e. input elements can't access it if there are 
intermidate scopes).

*What to do:*
Provide an easy and reliable way to access item (maybe as _$item_?) and 
_$index_ variables (used by unique ignite-validator). It would also be handy to 
be able to change item alias name (useful for nested list-editable's).



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

[GitHub] ignite pull request #3364: Ignite 2.4.1-merge-master-weakref-checkpointentry

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

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

Ignite 2.4.1-merge-master-weakref-checkpointentry



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-2.4.1-merge-master-weakref-checkpointentry

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

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


commit e7ca9b65a68de7752195c8f4d2b5180f3c77d19f
Author: Dmitriy Govorukhin 
Date:   2017-11-13T18:52:47Z

ignite-blt-merge -> ignite-2.4.1

commit cc8168fc184bb7f5e3cc3bbb0743397097f78bfb
Author: Dmitriy Govorukhin 
Date:   2017-11-13T19:13:01Z

merge ignite-pitr-rc1 -> ignite-2.4.1

commit 87e6d74cf6a251c7984f9e68c391f790feccc281
Author: Dmitriy Govorukhin 
Date:   2017-11-14T12:49:33Z

ignite-gg-12877 Compact consistent ID in WAL

commit 9f5a22711baea05bd37ab07c8f928a4837dd83a4
Author: Ilya Lantukh 
Date:   2017-11-14T14:12:28Z

Fixed javadoc.

commit d5af2d78dd8eef8eca8ac5391d31d8c779649bb0
Author: Alexey Kuznetsov 
Date:   2017-11-15T08:09:00Z

IGNITE-6913 Baseline: Added new options to controls.sh for baseline 
manipulations.

commit 713924ce865752b6e99b03bd624136541cea5f9f
Author: Sergey Chugunov 
Date:   2017-11-15T09:03:12Z

IGNITE-5850 failover tests for cache operations during BaselineTopology 
changes

commit b65fd134e748d496f732ec2aa0953a0531f544b8
Author: Ilya Lantukh 
Date:   2017-11-15T12:54:35Z

TX read logging if PITR is enabled.

commit 9b2a567c0e04dc33116b51f88bee75f76e9107d1
Author: Ilya Lantukh 
Date:   2017-11-15T13:45:16Z

TX read logging if PITR is enabled.

commit 993058ccf0b2b8d9e80750c3e45a9ffa31d85dfa
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:51:54Z

ignite-2.4.1 optimization for store full set node more compacted

commit 1eba521f608d39967aec376b397b7fc800234e54
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:52:22Z

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

commit 564b3fd51f8a7d1d81cb6874df66d0270623049c
Author: Sergey Chugunov 
Date:   2017-11-15T14:00:51Z

IGNITE-5850 fixed issue with initialization of data regions on node 
activation, fixed issue with auto-activation when random node joins inactive 
cluster with existing BLT

commit c6d1fa4da7adfadc80abdc7eaf6452b86a4f6aa4
Author: Sergey Chugunov 
Date:   2017-11-15T16:23:08Z

IGNITE-5850 transitionResult is set earlier when request for changing 
BaselineTopology is sent

commit d65674363163e38a4c5fdd73d1c8d8e1c7610797
Author: Sergey Chugunov 
Date:   2017-11-16T11:59:07Z

IGNITE-5850 new failover tests for changing BaselineTopology up (new node 
added to topology)

commit 20552f3851fe8825191b144179be032965e0b5c6
Author: Sergey Chugunov 
Date:   2017-11-16T12:53:43Z

IGNITE-5850 improved error message when online node is removed from baseline

commit 108bbcae4505ac904a6db774643ad600bfb42c21
Author: Sergey Chugunov 
Date:   2017-11-16T13:45:52Z

IGNITE-5850 BaselineTopology should not change on cluster deactivation

commit deb641ad3bdbf260fa60ad6bf607629652e324bd
Author: Dmitriy Govorukhin 
Date:   2017-11-17T09:45:44Z

ignite-2.4.1 truncate wal and checkpoint history on move/delete snapshot

commit 3c8b06f3659af30d1fd148ccc0f40e216a56c998
Author: Alexey Goncharuk 
Date:   2017-11-17T12:48:12Z

IGNITE-6947 Abandon remap after single map if future is done (fixes NPE)

commit ba2047e5ae7d271a677e0c418375d82d78c4023e
Author: devozerov 
Date:   2017-11-14T12:26:31Z

IGNITE-6901: Fixed assertion during 
IgniteH2Indexing.rebuildIndexesFromHash. This closes #3027.

commit abfc0466d6d61d87255d0fe38cbdf11ad46d4f89
Author: Sergey Chugunov 
Date:   2017-11-17T13:40:57Z

IGNITE-5850 tests for queries in presence of BaselineTopology

commit f4eabaf2a905abacc4c60c01d3ca04f6ca9ec188
Author: Sergey Chugunov 
Date:   2017-11-17T17:23:02Z

IGNITE-5850 implementation for setBaselineTopology(long topVer) migrated 
from wc-251

commit 4edeccd3e0b671aa277f58995df9ff9935baa95a
Author: EdShangGG 
Date:   2017-11-17T18:21:17Z

GG-13074 Multiple snapshot test failures after baseline topology is 
introduced
-adding baseline test to suite
-fixing issues with baseline

commit edae228c8f55990c15ef3044be987dcb00d6c81a
Author: EdShangGG 
Date:   2017-11-18T10:36:41Z

hack with 

[GitHub] ignite pull request #3363: IGNITE-5725 Adapt TracerTest for TC builds.

[oignatenko]

GitHub user oignatenko opened a pull request:

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

IGNITE-5725 Adapt TracerTest for TC builds.

- implemented adaptive testing approach
-- verified with diffs overview, clean rebuild and execution of unit tests 
in both desktop and headless environments

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

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

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

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


commit 57ac99736f0748eab79bc408111dfb9e2d077e2e
Author: Oleg Ignatenko 
Date:   2018-01-12T10:02:20Z

IGNITE-5725 Adapt TracerTest for TC builds.
- implemented adaptive testing approach
-- verified with diffs overview, clean rebuild and execution of unit tests 
in both desktop and headless environments




---

[GitHub] ignite pull request #3316: IGNITE-7332: Add test suite for ML examples

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3348: IGNITE-7203 Java 8 by default

[vveider]

Github user vveider closed the pull request at:

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


---

[jira] [Created] (IGNITE-7394) .NET: Add F# tests

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7394:
--

 Summary: .NET: Add F# tests
 Key: IGNITE-7394
 URL: https://issues.apache.org/jira/browse/IGNITE-7394
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Priority: Minor


Add tests to ensure that Ignite.NET can be used from F#. In particular, check 
that all F# data types can be used in cache without issues (records, tuples, 
etc).

These tests can be added to {{Apache.Ignite.DotNetCore.sln}}.



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

[jira] [Created] (IGNITE-7393) Apache Ignite delivery in RPM / DEV packages

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7393:


 Summary: Apache Ignite delivery in RPM / DEV packages
 Key: IGNITE-7393
 URL: https://issues.apache.org/jira/browse/IGNITE-7393
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov
Priority: Critical
 Fix For: 2.5


Aggregation task for first stage of preparing Apache Ignite delivery through 
RPM / DEB packages.
Steps:
# Prepare source-based package build procedures for RPM and DEB.
# Introduce these build procedures to Release Apache Ignite task in PublicTC 
(including generation of RPM / DEB repositories structure for deployment to 
apache.org/dist).
# Introduce PPA DEB repository for Apache Ignite.



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

[GitHub] ignite pull request #3362: IGNITE-6826

[SomeFire]

GitHub user SomeFire opened a pull request:

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

IGNITE-6826



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

$ git pull https://github.com/SomeFire/ignite ignite-6826

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

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


commit cd268cf53b769d26e3ae8a243013cb028569a846
Author: Dmitrii Ryabov 
Date:   2017-12-27T10:25:39Z

IGNITE-6826: ipFinder changed in java examples.

commit 78783a17fb625b854a7a3e3fa86bea918b2b2637
Author: Dmitrii Ryabov 
Date:   2018-01-11T14:11:11Z

IGNITE-6826: ipFinder changed in dotnet examples.

commit 69f85efa93195de88e691368b333f3633504ce50
Author: Dmitrii Ryabov 
Date:   2018-01-11T14:16:53Z

IGNITE-6826: ipFinder changed in cpp examples.




---