Re: Dedicated readme.io documentation for Ignite integrations

[Dmitriy Setrakyan]

Denis, do you think RDBMS integrations should be there as well?

On Wed, Nov 30, 2016 at 4:22 AM, Denis Magda  wrote:

> Igniters,
>
> Ignite can already boast about a number of integrations it has with a
> other products and technologies. Up to this point all the integrations were
> documented on our main readme.io  making the overall
> documentation a bit messy.
>
> I’ve decoupled the integrations from the core modules by moving them to a
> new documentation domain “Apache Ignite Integrations” <
> https://apacheignite-mix.readme.io/docs>. As a result integrations as
> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the streamers
> reside there.
>
> Dmitriy, looks like we have to upgrade readme.io subscription to
> “Developer Hub” for the new documentation domain because now there is now
> way to change the appearance. Appearance themes settings are poor. Could
> you handle this?
>
> —
> Denis

Re: Blogging about new .NET features

[Denis Magda]

Cos,

This sounds interesting. Did it help to promote BigTop somehow?

As I understand the blogging engine lacks of advanced text and code formatting 
capabilities. Is it so? This will be an issue for those posts that contains 
code snippets as a part of the content.  However, in any case we should have at 
least one shared Apache Ignite account that can be used for release and big 
features announcements. Could you assist with setting it up?

—
Denis

> On Nov 26, 2016, at 1:21 PM, Konstantin Boudnik  wrote:
> 
> Gents, 
> 
> I would encourage you to use
> 
>https://blogs.apache.org/
> 
> as this place gets contant attention of the ASF media team and all the blogs
> here got quite a bit of the spot light. In fact, I would encourage this group
> to start using it. I'd be happy to help to set this up.
> 
> Cos
> 
> On Wed, Nov 23, 2016 at 10:34AM, Denis Magda wrote:
>> Pavel,
>> 
>> Do you mind blogging about ASP.NET session state [1] and Entity Framework 
>> 2nd level cache [2] support after 1.8 release goes public?
>> 
>> Also I would remind everyone in the community that it’s always welcomed to 
>> share your experience or Ignite related news over blog posts. We track all 
>> the posts on this page.
>> https://ignite.apache.org/blogs.html 
>> 
>> 
>> [1] https://apacheignite-net.readme.io/docs/aspnet-session-state-caching 
>> 
>> [2] 
>> https://apacheignite-net.readme.io/docs/entity-framework-second-level-cache 
>> 
>> 
>> —
>> Denis

Dedicated readme.io documentation for Ignite integrations

[Denis Magda]

Igniters,

Ignite can already boast about a number of integrations it has with a other 
products and technologies. Up to this point all the integrations were 
documented on our main readme.io  making the overall 
documentation a bit messy.

I’ve decoupled the integrations from the core modules by moving them to a new 
documentation domain “Apache Ignite Integrations” 
. As a result integrations as 
Cassandra CacheStore, OSGi support, Zeppelin and bunch of the streamers reside 
there.

Dmitriy, looks like we have to upgrade readme.io subscription to “Developer 
Hub” for the new documentation domain because now there is now way to change 
the appearance. Appearance themes settings are poor. Could you handle this? 

—
Denis

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

The list of issues found today:

IGNITE-4334 DML: INSERT INTO SELECT FROM statement fails if copy from
partitioned to replicated cache


On Tue, Nov 29, 2016 at 9:56 PM, Sergey Kozlov  wrote:

> Denis
>
> We've good progress for DML. But unlike the regular queries DML has
> significantly more specific cases that required our attention. Though some
> cases aren't bugs but they've another behavior than user can expect using
> SQL-related experience.
>
>
> On Tue, Nov 29, 2016 at 8:33 PM, Denis Magda  wrote:
>
>> Alexander,
>>
>> Now I see, thanks. Ok, I would suggest fixing it under 2.0 and document
>> this limitation on the DML page you have been working on.
>>
>> —
>> Denis
>>
>> > On Nov 29, 2016, at 9:31 AM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>> >
>> > Denis,
>> >
>> > See the comment to issue. Note that this affects DML in case of INSERT
>> > from subquery with specific returned column result types AND aside of
>> > DML affects SELECTs - the user isn't able to retrieve exactly what
>> > they have put to cache as some object's field. However, according to
>> > Vlad, arrays of wrappers are seldom present in real SQL related use
>> > cases, so there's little to worry about.
>> >
>> > - Alex
>> >
>> > 2016-11-29 20:21 GMT+03:00 Denis Magda :
>> >> Alexander,
>> >>
>> >> Do you mean this issue recently opened by you?
>> >> https://issues.apache.org/jira/browse/IGNITE-4331 <
>> https://issues.apache.org/jira/browse/IGNITE-4331>
>> >>
>> >> How would it affect the overall user experience? Could you provide DML
>> queries examples that won’t work due to the bug.
>> >>
>> >> —
>> >> Denis
>> >>
>> >>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>> >>>
>> >>> DML is done as for now, example is done too, currently there's no open
>> >>> issues related with it (besides documentation which I'm working on).
>> >>> Yesterday's problem turned out to be binary/SQL engine (pre DML)
>> >>> related and is currently in won't fix state as agreed with Vlad, I've
>> >>> created issues detailing it.
>> >>>
>> >>> - Alex
>> >>>
>> >>> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
>>  Hi
>> 
>>  There's update for DML testing and binary package:
>> 
>>  IGNITE-4321 Cassandra modules
>>  
>>  IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
>>  IgniteException: Wrong value has been set
>>  
>> 
>>  On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov <
>> akuznet...@apache.org>
>>  wrote:
>> 
>> > Vladimir,
>> >
>> > IGNITE-3443 Implement collecting what SQL statements executed on
>> cluster
>> > and their metrics.
>> >
>> > --
>> > Alexey Kuznetsov
>> >
>> 
>> 
>> 
>>  --
>>  Sergey Kozlov
>>  GridGain Systems
>>  www.gridgain.com
>> >>
>>
>>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-4334) DML: INSERT INTO SELECT FROM statement fails if copy from partitioned to replicated cache

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4334:
-

 Summary: DML: INSERT INTO SELECT FROM statement fails if copy from 
partitioned to replicated cache
 Key: IGNITE-4334
 URL: https://issues.apache.org/jira/browse/IGNITE-4334
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


INSERT INTO SELECT FROM statement fails if executed on a replicated cache and 
used partitioned cache as data source:

{code:title=test.java|borderStyle=solid}
public static void main(String[] args) throws Exception {
Ignition.setClientMode(true);

final Long PRELOAD_NUM = 1_000L;
final Long RANGE_NUM = 2*PRELOAD_NUM;
final int OPERATION_LIMIT = 500;

ArrayList fields = new ArrayList<>(
Arrays.asList("intCol", "longCol", "shortCol", "stringCol", 
"doubleCol", "bigDecimalCol", "booleanCol", "mapCol")
);

List cacheNames = Arrays.asList(
"tx-part-full-sync",
"tx-repl-full-sync",
);

List cacheTxNames = new ArrayList();

for (int i=0; i < cacheNames.size(); i++) {
if (cacheNames.get(i).startsWith("tx"))
cacheTxNames.add(cacheNames.get(i));
}
String srcCache = null;
try (Ignite ig = Ignition.start("examples/config/ext-sql.xml")) {

for (String cacheName : cacheNames) {

ig.cache(cacheName).query(new SqlFieldsQuery("delete from 
AllTypes"));

if (srcCache == null) {
System.out.println("The cache size " + cacheName + ": " + 
ig.cache(cacheName).sizeLong());
for (long i = 0L; i < PRELOAD_NUM; i=i+50) {

ArrayList sqlArgs = new ArrayList();
for (int j = 0; j < 50; j++) {
sqlArgs.add(i + j);
}

ig.cache(cacheName).query(
makeInsertSqlAndArgsByKey(sqlArgs, false)
);

if (i > 0 && i % (PRELOAD_NUM / 10) == 0) {
Date d = new Date();
System.out.println(d.toString() + " Done: " + i);
Object val = ig.cache(cacheName).get(i);
}
}
srcCache = cacheName;
}
else {
ig.cache(cacheName).query(new SqlFieldsQuery("insert into 
AllTypes (_key, _val) select _key, _val from \"" + srcCache + "\".AllTypes"));
}
System.out.println("The cache size " + cacheName + ": " + 
ig.cache(cacheName).sizeLong());
}

}
{code}

{noformat}
Exception in thread "main" javax.cache.CacheException: Queries running on 
replicated cache should not contain JOINs with partitioned tables 
[rCache=tx-repl-full-sync, pCache=tx-part-full-sync]
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.stableDataNodes(GridReduceQueryExecutor.java:432)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:529)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:700)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:282)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:155)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:185)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1777)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExampl

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Denis

We've good progress for DML. But unlike the regular queries DML has
significantly more specific cases that required our attention. Though some
cases aren't bugs but they've another behavior than user can expect using
SQL-related experience.


On Tue, Nov 29, 2016 at 8:33 PM, Denis Magda  wrote:

> Alexander,
>
> Now I see, thanks. Ok, I would suggest fixing it under 2.0 and document
> this limitation on the DML page you have been working on.
>
> —
> Denis
>
> > On Nov 29, 2016, at 9:31 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
> >
> > Denis,
> >
> > See the comment to issue. Note that this affects DML in case of INSERT
> > from subquery with specific returned column result types AND aside of
> > DML affects SELECTs - the user isn't able to retrieve exactly what
> > they have put to cache as some object's field. However, according to
> > Vlad, arrays of wrappers are seldom present in real SQL related use
> > cases, so there's little to worry about.
> >
> > - Alex
> >
> > 2016-11-29 20:21 GMT+03:00 Denis Magda :
> >> Alexander,
> >>
> >> Do you mean this issue recently opened by you?
> >> https://issues.apache.org/jira/browse/IGNITE-4331 <
> https://issues.apache.org/jira/browse/IGNITE-4331>
> >>
> >> How would it affect the overall user experience? Could you provide DML
> queries examples that won’t work due to the bug.
> >>
> >> —
> >> Denis
> >>
> >>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
> >>>
> >>> DML is done as for now, example is done too, currently there's no open
> >>> issues related with it (besides documentation which I'm working on).
> >>> Yesterday's problem turned out to be binary/SQL engine (pre DML)
> >>> related and is currently in won't fix state as agreed with Vlad, I've
> >>> created issues detailing it.
> >>>
> >>> - Alex
> >>>
> >>> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
>  Hi
> 
>  There's update for DML testing and binary package:
> 
>  IGNITE-4321 Cassandra modules
>  
>  IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
>  IgniteException: Wrong value has been set
>  
> 
>  On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov <
> akuznet...@apache.org>
>  wrote:
> 
> > Vladimir,
> >
> > IGNITE-3443 Implement collecting what SQL statements executed on
> cluster
> > and their metrics.
> >
> > --
> > Alexey Kuznetsov
> >
> 
> 
> 
>  --
>  Sergey Kozlov
>  GridGain Systems
>  www.gridgain.com
> >>
>
>


-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Re: Apache Ignite 1.8 Release

[Denis Magda]

Alexander,

Now I see, thanks. Ok, I would suggest fixing it under 2.0 and document this 
limitation on the DML page you have been working on.

—
Denis

> On Nov 29, 2016, at 9:31 AM, Alexander Paschenko 
>  wrote:
> 
> Denis,
> 
> See the comment to issue. Note that this affects DML in case of INSERT
> from subquery with specific returned column result types AND aside of
> DML affects SELECTs - the user isn't able to retrieve exactly what
> they have put to cache as some object's field. However, according to
> Vlad, arrays of wrappers are seldom present in real SQL related use
> cases, so there's little to worry about.
> 
> - Alex
> 
> 2016-11-29 20:21 GMT+03:00 Denis Magda :
>> Alexander,
>> 
>> Do you mean this issue recently opened by you?
>> https://issues.apache.org/jira/browse/IGNITE-4331 
>> 
>> 
>> How would it affect the overall user experience? Could you provide DML 
>> queries examples that won’t work due to the bug.
>> 
>> —
>> Denis
>> 
>>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko 
>>>  wrote:
>>> 
>>> DML is done as for now, example is done too, currently there's no open
>>> issues related with it (besides documentation which I'm working on).
>>> Yesterday's problem turned out to be binary/SQL engine (pre DML)
>>> related and is currently in won't fix state as agreed with Vlad, I've
>>> created issues detailing it.
>>> 
>>> - Alex
>>> 
>>> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
 Hi
 
 There's update for DML testing and binary package:
 
 IGNITE-4321 Cassandra modules
 
 IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
 IgniteException: Wrong value has been set
 
 
 On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
 wrote:
 
> Vladimir,
> 
> IGNITE-3443 Implement collecting what SQL statements executed on cluster
> and their metrics.
> 
> --
> Alexey Kuznetsov
> 
 
 
 
 --
 Sergey Kozlov
 GridGain Systems
 www.gridgain.com
>> 

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

Denis,

See the comment to issue. Note that this affects DML in case of INSERT
from subquery with specific returned column result types AND aside of
DML affects SELECTs - the user isn't able to retrieve exactly what
they have put to cache as some object's field. However, according to
Vlad, arrays of wrappers are seldom present in real SQL related use
cases, so there's little to worry about.

- Alex

2016-11-29 20:21 GMT+03:00 Denis Magda :
> Alexander,
>
> Do you mean this issue recently opened by you?
> https://issues.apache.org/jira/browse/IGNITE-4331 
> 
>
> How would it affect the overall user experience? Could you provide DML 
> queries examples that won’t work due to the bug.
>
> —
> Denis
>
>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko 
>>  wrote:
>>
>> DML is done as for now, example is done too, currently there's no open
>> issues related with it (besides documentation which I'm working on).
>> Yesterday's problem turned out to be binary/SQL engine (pre DML)
>> related and is currently in won't fix state as agreed with Vlad, I've
>> created issues detailing it.
>>
>> - Alex
>>
>> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
>>> Hi
>>>
>>> There's update for DML testing and binary package:
>>>
>>> IGNITE-4321 Cassandra modules
>>> 
>>> IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
>>> IgniteException: Wrong value has been set
>>> 
>>>
>>> On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
>>> wrote:
>>>
 Vladimir,

 IGNITE-3443 Implement collecting what SQL statements executed on cluster
 and their metrics.

 --
 Alexey Kuznetsov

>>>
>>>
>>>
>>> --
>>> Sergey Kozlov
>>> GridGain Systems
>>> www.gridgain.com
>

Re: Apache Ignite 1.8 Release

[Denis Magda]

Alexander,

Do you mean this issue recently opened by you?
https://issues.apache.org/jira/browse/IGNITE-4331 


How would it affect the overall user experience? Could you provide DML queries 
examples that won’t work due to the bug.

—
Denis

> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko 
>  wrote:
> 
> DML is done as for now, example is done too, currently there's no open
> issues related with it (besides documentation which I'm working on).
> Yesterday's problem turned out to be binary/SQL engine (pre DML)
> related and is currently in won't fix state as agreed with Vlad, I've
> created issues detailing it.
> 
> - Alex
> 
> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
>> Hi
>> 
>> There's update for DML testing and binary package:
>> 
>> IGNITE-4321 Cassandra modules
>> 
>> IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
>> IgniteException: Wrong value has been set
>> 
>> 
>> On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
>> wrote:
>> 
>>> Vladimir,
>>> 
>>> IGNITE-3443 Implement collecting what SQL statements executed on cluster
>>> and their metrics.
>>> 
>>> --
>>> Alexey Kuznetsov
>>> 
>> 
>> 
>> 
>> --
>> Sergey Kozlov
>> GridGain Systems
>> www.gridgain.com

[jira] [Created] (IGNITE-4333) SQL engine does not preserve metadata about array content's type

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4333:
---

 Summary: SQL engine does not preserve metadata about array 
content's type
 Key: IGNITE-4333
 URL: https://issues.apache.org/jira/browse/IGNITE-4333
 Project: Ignite
  Issue Type: Sub-task
  Components: SQL
Affects Versions: 1.8
Reporter: Alexander Paschenko
 Fix For: 2.0


This problem arises on SQL *SELECT* from grid table and on results page 
transfer over network.

First, when data is *SELECT* ed, 
{{org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.RowDescriptor#wrap}}
 does not look at array's component type and tries to convert any array to 
{{Object[]}} which turns to {{ClassCastException}} when array is of primitive 
type and erases metadata about its contents when its type is not primitive.

Then, when results page is transferred over network, array is wrapped into 
{{org.apache.ignite.internal.processors.query.h2.twostep.msg.GridH2Array}} 
which does not have any metadata too, so, even if we had returned primitive 
array from native H2's local *SELECT*, information about its primitiveness 
would be lost anyway, and it would be converted to, say, {{java.lang.Byte[]}} 
after all.

So, currently there's no way to *SELECT* a primitive array field via SQL.

Probably this could be fixed by changing {{GridH2Array}}, but this would break 
backward compatibility, so it's an open question for now.



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

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

DML is done as for now, example is done too, currently there's no open
issues related with it (besides documentation which I'm working on).
Yesterday's problem turned out to be binary/SQL engine (pre DML)
related and is currently in won't fix state as agreed with Vlad, I've
created issues detailing it.

- Alex

2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
> Hi
>
> There's update for DML testing and binary package:
>
> IGNITE-4321 Cassandra modules
> 
> IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
> IgniteException: Wrong value has been set
> 
>
> On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
> wrote:
>
>> Vladimir,
>>
>> IGNITE-3443 Implement collecting what SQL statements executed on cluster
>> and their metrics.
>>
>> --
>> Alexey Kuznetsov
>>
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com

Fwd: [jira] [Created] (IGNITE-4331) Binary marshaller does not preserve component type when deserealizing even basic array typed fields

[Denis Magda]

How does this affect the overall user experience? Please give an example of 
what kind of queries won’t be supported.

—
Denis


> Begin forwarded message:
> 
> From: "Alexander Paschenko (JIRA)" 
> Subject: [jira] [Created] (IGNITE-4331) Binary marshaller does not preserve 
> component type when deserealizing even basic array typed fields
> Date: November 29, 2016 at 7:03:58 AM PST
> To: dev@ignite.apache.org
> Reply-To: dev@ignite.apache.org
> 
> Alexander Paschenko created IGNITE-4331:
> ---
> 
> Summary: Binary marshaller does not preserve component type when 
> deserealizing even basic array typed fields
> Key: IGNITE-4331
> URL: https://issues.apache.org/jira/browse/IGNITE-4331
> Project: Ignite
>  Issue Type: Sub-task
>  Components: binary
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.0
> 
> 
> How to reproduce: try to deserialize *single* field having type of {{Byte[]}} 
> or any other primitive wrapper type array. It will be deserialized as 
> {{Object[]}} and won't be suitable even to set the same field's value again - 
> metadata check on object building will fail as required ({{Byte[]}}) and 
> given ({{Object[]}}) types won't match.
> 
> As agreed with [~vozerov], currently we're not fixing it. Probably will get 
> back to this while working on 2.0 release.
> 
> Discovered by [~skozlov] while running SQL DML examples during 1.8 release QA 
> process, exact reasons found by [~al.psc].
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)

[GitHub] ignite pull request #1299: Ignite 4332

[EdShangGG]

GitHub user EdShangGG opened a pull request:

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

Ignite 4332



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

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

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

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


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 7a47a0185d308cd3a58c7bfcb4d1cd548bff5b87
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit bf330251734018467fa3291fccf0414c9da7dd1b
Author: Andrey Novikov 
Date:   2016-11-24T10:08:08Z

Web console beta-6.

commit 7d88c5bfe7d6f130974fab1ed4266fff859afd3d
Author: Andrey Novikov 
Date:   2016-11-24T10:59:33Z

Web console beta-6. Minor fix.

commit 9c6824b4f33fbdead64299d9e0c34365d5d4a570
Author: nikolay_tikhonov 
Date:   2016-11-24T13:27:05Z

IGNITE-3958 Fixed "Client node should not start rest processor".

commit 56998e704e9a67760c70481c10c56e72c0a866bb
Author: Konstantin Dudkov 
Date:   2016-10-28T13:27:34Z

ignite-4088 Added methods to create/destroy multiple caches. This closes 
#1174.

(cherry picked from commit f445e7b)

commit 3e2ccfd30427ba0552eea8667c0129ae5ace9c0b
Author: Igor Sapego 
Date:   2016-11-25T11:26:54Z

IGNITE-4299: Fixes for examples.

commit 6fbaef45af8f40062a95058df7ec0984c99035b9
Author: Konstantin Dudkov 
Date:   2016-11-25T10:58:58Z

IGNITE-4305 marshalling fix in GridNearAtomicSingleUpdateInvokeRequest

commit 6d310e56b80627950746f85f023b22827b71bcf0
Author: EdShangGG 
Date:   2016-11-29T15:13:41Z

IGNITE-4332 Usage of cache.getEntry inside GridCacheQueryManager.runQuery 
causes to remote operations




---
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-4332) Usage of cache.getEntry inside GridCacheQueryManager.runQuery causes to remote operations

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-4332:
-

 Summary: Usage of cache.getEntry inside 
GridCacheQueryManager.runQuery causes to remote operations
 Key: IGNITE-4332
 URL: https://issues.apache.org/jira/browse/IGNITE-4332
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
 Fix For: 1.8






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

[jira] [Created] (IGNITE-4331) Binary marshaller does not preserve component type when deserealizing even basic array typed fields

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4331:
---

 Summary: Binary marshaller does not preserve component type when 
deserealizing even basic array typed fields
 Key: IGNITE-4331
 URL: https://issues.apache.org/jira/browse/IGNITE-4331
 Project: Ignite
  Issue Type: Sub-task
  Components: binary
Affects Versions: 1.8
Reporter: Alexander Paschenko
 Fix For: 2.0


How to reproduce: try to deserialize *single* field having type of {{Byte[]}} 
or any other primitive wrapper type array. It will be deserialized as 
{{Object[]}} and won't be suitable even to set the same field's value again - 
metadata check on object building will fail as required ({{Byte[]}}) and given 
({{Object[]}}) types won't match.

As agreed with [~vozerov], currently we're not fixing it. Probably will get 
back to this while working on 2.0 release.

Discovered by [~skozlov] while running SQL DML examples during 1.8 release QA 
process, exact reasons found by [~al.psc].



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

[jira] [Created] (IGNITE-4330) Cache is loaded twice in the case of BinaryMarshaller

[Steve Hostettler (JIRA)]

Steve Hostettler created IGNITE-4330:


 Summary: Cache is loaded twice in the case of BinaryMarshaller
 Key: IGNITE-4330
 URL: https://issues.apache.org/jira/browse/IGNITE-4330
 Project: Ignite
  Issue Type: Bug
  Components: Ignite RDD
Affects Versions: 1.7
Reporter: Steve Hostettler
Priority: Critical


We noticed that while loading a cache with the BinaryMarshaller, the cache gets 
loaded twice.

In method loadCache(final IgniteBiInClosure clo, @Nullable Object... 
args) on line 735, we iterate over the entryMappings

In my case because I do use the BinaryMarshaller,  I end with the mappings 
described twice

In method getOrCreateCacheMappings(@Nullable String cacheName) line 654 adds a 
different EntryMapping  and different key with the same Jdbc type.




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

[jira] [Created] (IGNITE-4329) .NET: Document web deployment specifics on readme.io

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4329:
--

 Summary: .NET: Document web deployment specifics on readme.io 
 Key: IGNITE-4329
 URL: https://issues.apache.org/jira/browse/IGNITE-4329
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.8


Deploying Ignite.NET requires additional steps in regards to Libs folder. We 
have some details on 
https://apacheignite-net.readme.io/docs/aspnet-output-caching page, but this 
should be documented in a more general way with better visibility.



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

[jira] [Created] (IGNITE-4328) .NET: Create readme.md

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4328:
--

 Summary: .NET: Create readme.md
 Key: IGNITE-4328
 URL: https://issues.apache.org/jira/browse/IGNITE-4328
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.9


Java part has both readme.txt (for local viewing) and readme.md (for nice 
github appearance).

.NET should have the same:
https://github.com/apache/ignite/tree/master/modules/platforms/dotnet

We can also include a build status icon:
http://ci.ignite.apache.org/app/rest/builds/buildType:(id:IgniteTests_IgnitePlatformNet)/statusIcon



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

[jira] [Created] (IGNITE-4327) Failed to INSERT array of Bytes from SELECT

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4327:
---

 Summary: Failed to INSERT array of Bytes from SELECT
 Key: IGNITE-4327
 URL: https://issues.apache.org/jira/browse/IGNITE-4327
 Project: Ignite
  Issue Type: Bug
  Components: binary, SQL
Affects Versions: 1.8
Reporter: Alexander Paschenko
 Fix For: 2.0


An attempt to INSERT binary object having a {{Byte[]}} typed field from 
{{SELECT *}} yeilds following exception (initially observed in IGNITE-4323):

{code}
Exception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteCheckedException: Can not set [Ljava.lang.Byte; field 
org.apache.ignite.testtools.model.AllTypes.bytesCol to [Ljava.lang.Object;
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1440)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:2183)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1125)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:237)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteCheckedException: Can not set 
[Ljava.lang.Byte; field org.apache.ignite.testtools.model.AllTypes.bytesCol to 
[Ljava.lang.Object;
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7185)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:169)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:118)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.get(GridDhtAtomicCache.java:482)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4783)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1395)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1118)
... 6 more
Caused by: java.lang.IllegalArgumentException: Can not set [Ljava.lang.Byte; 
field org.apache.ignite.testtools.model.AllTypes.bytesCol to [Ljava.lang.Object;
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
at 
sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
at java.lang.reflect.Field.set(Field.java:741)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:829)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1498)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:147)
at 
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1760)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:630)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:492)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:155)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$2200(GridDhtAtomicCache.java:125)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$12.apply(GridDhtAtomicCache.java:440)
at 
o

[jira] [Created] (IGNITE-4326) .NET: Rebuild in Visual Studio fails the first time

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4326:
--

 Summary: .NET: Rebuild in Visual Studio fails the first time
 Key: IGNITE-4326
 URL: https://issues.apache.org/jira/browse/IGNITE-4326
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.9


Clean than Rebuild fails:
{code}
CS0234  The type or namespace name 'Linq' does not exist in the namespace 
'Apache.Ignite' (are you missing an assembly reference?)  
Apache.Ignite.Examples  
C:\W\incubator-ignite\modules\platforms\dotnet\Examples\Apache.Ignite.Examples\Datagrid\LinqExample.cs
{code}

Consequent build succeeds.
Looks like a missing build dependency.



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