Re: Web Console Beta 2 release

[Dmitriy Setrakyan]

Just checked it out, looks awesome! Very nice and easy way to configure,
manage, and query Ignite clusters.

On Tue, Jun 28, 2016 at 1:41 AM, Alexey Kuznetsov 
wrote:

> Igniters!
>
> I'd like to announce that we just pushed Ignite Web Console Beta 2 to
> master branch and deployed new version at https://console.gridgain.com
>
> NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
> Console.
>
> What's new:
>
>- Implemented Monitoring of grid and caches (please note, you will
>need grid started from latest nightly build of master branch).
>-  Improved Demo mode (you may test SQL and Monitoring in Demo mode).
>-  Added a lot of properties to grid configuration.
>-  Improved validation of configuration properties.
>-  Improved XML and Java code generation.
>-  Fixed a lot of bugs and usability issues.
>
> Feedback and suggestions are welcome!
>
> What's next:
>
>- Migrate build to Webpack from jspm.
>- Frontend and backend tests.
>- .NET configuration and code generation.
>- Logs view and logs search.
>- Many new features are coming...
>
>
> Stay tuned!
> --
> Alexey Kuznetsov
>

Re: great ticket for a newbie

[Bryan Karlovitz]

My username is my email: bryan.a.karlov...@gmail.com

Looking forward to it :)

Bryan

On Wed, Jun 29, 2016 at 8:17 PM, Dmitriy Setrakyan 
wrote:

> Hi Bryan,
>
> Welcome to the Ignite community!
>
> Please familiarize yourself with Ignite development process:
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
> Also, please let us know your Apache Jira username, so we could add you to
> the list of Ignite contributors. This way you will be able to assign the
> ticket to yourself.
>
> If you have any questions, send them here.
>
> Thanks,
> D.
>
> On Wed, Jun 29, 2016 at 6:13 PM, Bryan Karlovitz <
> bryan.a.karlov...@gmail.com> wrote:
>
> > Hello.
> >
> > My name is Bryan. I'm a software engineer based in Chicago. I haven't
> > contributed to Ignite before, and I'd love to start with this ticket.
> >
> > Thanks.
> >
> > On Wed, Jun 29, 2016 at 6:58 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > I believe this is an absolutely great ticket to get started with
> Ignite:
> > > https://issues.apache.org/jira/browse/IGNITE-3399
> > >
> > > On top of being a great way to get started with the project, it will
> also
> > > significantly enhance SQL querying support when used with binary
> > protocol.
> > >
> > > Hope someone in the community picks it up.
> > >
> > > D.
> > >
> >
>

Re: great ticket for a newbie

[Dmitriy Setrakyan]

Hi Bryan,

Welcome to the Ignite community!

Please familiarize yourself with Ignite development process:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Also, please let us know your Apache Jira username, so we could add you to
the list of Ignite contributors. This way you will be able to assign the
ticket to yourself.

If you have any questions, send them here.

Thanks,
D.

On Wed, Jun 29, 2016 at 6:13 PM, Bryan Karlovitz <
bryan.a.karlov...@gmail.com> wrote:

> Hello.
>
> My name is Bryan. I'm a software engineer based in Chicago. I haven't
> contributed to Ignite before, and I'd love to start with this ticket.
>
> Thanks.
>
> On Wed, Jun 29, 2016 at 6:58 PM, Dmitriy Setrakyan 
> wrote:
>
> > I believe this is an absolutely great ticket to get started with Ignite:
> > https://issues.apache.org/jira/browse/IGNITE-3399
> >
> > On top of being a great way to get started with the project, it will also
> > significantly enhance SQL querying support when used with binary
> protocol.
> >
> > Hope someone in the community picks it up.
> >
> > D.
> >
>

Re: great ticket for a newbie

[Bryan Karlovitz]

Hello.

My name is Bryan. I'm a software engineer based in Chicago. I haven't
contributed to Ignite before, and I'd love to start with this ticket.

Thanks.

On Wed, Jun 29, 2016 at 6:58 PM, Dmitriy Setrakyan 
wrote:

> I believe this is an absolutely great ticket to get started with Ignite:
> https://issues.apache.org/jira/browse/IGNITE-3399
>
> On top of being a great way to get started with the project, it will also
> significantly enhance SQL querying support when used with binary protocol.
>
> Hope someone in the community picks it up.
>
> D.
>

great ticket for a newbie

[Dmitriy Setrakyan]

I believe this is an absolutely great ticket to get started with Ignite:
https://issues.apache.org/jira/browse/IGNITE-3399

On top of being a great way to get started with the project, it will also
significantly enhance SQL querying support when used with binary protocol.

Hope someone in the community picks it up.

D.

[jira] [Created] (IGNITE-3399) Support primitive type names in QueryEntity

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-3399:


 Summary: Support primitive type names in QueryEntity
 Key: IGNITE-3399
 URL: https://issues.apache.org/jira/browse/IGNITE-3399
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Alexey Goncharuk
 Fix For: 1.7


When BinaryMarshaller is enabled (default), it is impossible to use primitive 
type names (such as int, short,...) as field type in QueryEntity. 

I think we should support such aliases because it will improve usability for 
.NET and C++ users, who will not need to deal with java types when configuring 
SQL.

A test reproducing the issue is committed to master: 
org.apache.ignite.internal.processors.cache.IgniteCachePrimitiveFieldsQuerySelfTest



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

[jira] [Created] (IGNITE-3398) .NET: Allow extending predefined Affinity Functions

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3398:
--

 Summary: .NET: Allow extending predefined Affinity Functions
 Key: IGNITE-3398
 URL: https://issues.apache.org/jira/browse/IGNITE-3398
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Priority: Critical
 Fix For: 1.7


Allow inheritance from FairAffinityFunction and RendezvousAffinityFunction.

User can override only certain methods. In this case other methods should not 
be delegated to .NET for performance.



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

Re: IGNITE-3337

[Saikat Maitra]

Thank you Andrey!!

Saikat

On Wed, Jun 29, 2016 at 4:49 PM, Andrey Novikov  wrote:

> Hi Saikat!
>
> I’ve just reviewed and merged your pull request.
>
> Thank you for your contribution!
>
> —
> Andrey
>
> On Wed, Jun 29, 2016 at 3:25 AM, Saikat Maitra 
> wrote:
>
> > Hello Andrey,
> >
> > I have updated the PR. Please review and share feedback.
> >
> > https://github.com/apache/ignite/pull/816
> >
> > Regards
> > Saikat
> >
> > On Thu, Jun 23, 2016 at 8:41 PM, Saikat Maitra 
> > wrote:
> >
> > > Thank you Andrey
> > >
> > > I will update the PR accordingly.
> > >
> > > Regards
> > > Saikat
> > >
> > > On Thu, Jun 23, 2016 at 12:33 PM, Andrey Novikov 
> > > wrote:
> > >
> > >> Saint,
> > >>
> > >> I've reviewed your PR and left comments in the ticket.
> > >>
> > >>
> > >> On Tue, Jun 21, 2016 at 1:14 AM, Saikat Maitra <
> saikat.mai...@gmail.com
> > >
> > >> wrote:
> > >>
> > >> > Hi Alexey , Sergey
> > >> >
> > >> > Thank you for your time and reviewing the PR. I agree we can
> deprecate
> > >> > cacheName for metadata command. I have updated the files and request
> > >> you to
> > >> > review the changes.
> > >> >
> > >> > Also can you please share where the docs are hosted and I can then
> > >> update
> > >> > the rest api doc.
> > >> >
> > >> > Regards
> > >> > Saikat
> > >> >
> > >> > On Mon, Jun 20, 2016 at 3:08 PM, Sergey Kozlov <
> skoz...@gridgain.com>
> > >> > wrote:
> > >> >
> > >> > > Hi Saikat and Alexey.
> > >> > >
> > >> > > I think that the solution suggested by Alexey is simple one.
> > Actually
> > >> > > null-named cache is widely used for now and we can't remove it (or
> > at
> > >> > least
> > >> > > we should re-think the approach for such caches). On the other
> hand
> > >> the
> > >> > > size of metadata returned by REST command even for dozen caches is
> > not
> > >> > > large and can be filtered (iterated) on the client side. So I
> > suppose
> > >> the
> > >> > > ticket should be updated according suggested approach.
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Mon, Jun 20, 2016 at 12:28 PM, Alexey Kuznetsov <
> > >> > > akuznet...@gridgain.com>
> > >> > > wrote:
> > >> > >
> > >> > > > Hi, Saikat
> > >> > > >
> > >> > > > I reviewed you PR and I think we should deprecate "cacheName"
> > >> > parameter
> > >> > > > in metadata command.
> > >> > > >
> > >> > > > In current implementation when "cacheName" was not specified
> that
> > >> means
> > >> > > to
> > >> > > > get "default" cache (with name=null)
> > >> > > > And now it will be impossible to take metadata for such cache.
> > >> > > >
> > >> > > > But I think for this command there is a little sense to extract
> > >> > metadata
> > >> > > > for single cache,
> > >> > > >  because any way on server side they will be extracted for all
> > >> caches.
> > >> > > > See:
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager#sqlMetadata
> > >> > > > line 999.
> > >> > > >
> > >> > > > Also for performance reason it is much faster to get all
> metadata
> > at
> > >> > > once.
> > >> > > >
> > >> > > > So, I suggest - to deprecate "cacheName" parameter and fix
> > >> > documentation.
> > >> > > >
> > >> > > > Thoughts?
> > >> > > >
> > >> > > >
> > >> > > > On Sun, Jun 19, 2016 at 10:42 PM, Saikat Maitra <
> > >> > saikat.mai...@gmail.com
> > >> > > >
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Hello,
> > >> > > > >
> > >> > > > > I have raised the PR[1] for the following Jira ticket[2].
> > >> > > > >
> > >> > > > > Please review and let me know any feedback
> > >> > > > >
> > >> > > > > Regards
> > >> > > > > Saikat
> > >> > > > >
> > >> > > > > [1] https://github.com/apache/ignite/pull/816
> > >> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-3337
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > Alexey Kuznetsov
> > >> > > > GridGain Systems
> > >> > > > www.gridgain.com
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Sergey Kozlov
> > >> > > GridGain Systems
> > >> > > www.gridgain.com
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>

[GitHub] ignite pull request #840: IGNITE-3329 .NET: Fix TestDeployNodeSingleton test...

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

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


---
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 #841: Ignite 1088 H2 based cache store for multi JVM tes...

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

Ignite 1088 H2 based cache store for multi JVM tests



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

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

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

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


commit c60eed556f7421ca36660845453c4734aebc5125
Author: Alexander Paschenko 
Date:   2016-06-23T18:09:19Z

IGNITE-1088 H2 based cache store for multi JVM tests

commit 9cc5a2cb77224b9136f929f3e47d9aa6aa91dc01
Author: Alexander Paschenko 
Date:   2016-06-24T14:26:21Z

IGNITE-1088 H2 cache store based tests fix; code style/javadoc fixes

commit 719915210b83a59ee660452fdf9d2044879f3bc3
Author: Alexander Paschenko 
Date:   2016-06-24T17:31:49Z

IGNITE-1088 Moved test cache store related stuff to separate classes to use 
in other tests affected by the issue

commit d649d76a437c2110def5baf63e944a52b94ab3bf
Author: Alexander Paschenko 
Date:   2016-06-29T12:37:08Z

IGNITE-1088 Switched IgniteCache* tests to new store strategy and unmuted 
previously failing tests




---
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-3397) CLONE - Aggregation query with where clause failed

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-3397:
-

 Summary: CLONE - Aggregation query with where clause failed
 Key: IGNITE-3397
 URL: https://issues.apache.org/jira/browse/IGNITE-3397
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: Sergey Kozlov
Priority: Critical


1. Extract everything from attached zip file into examples directory
2. Run {{CacheQueryFailures query3}}. It fails:
{noformat}
[14:52:52] Ignite node started OK (id=2821d4cc)
[14:52:52] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=3.5GB]
>>> initialize 300 keys
>>> run query3, type: SqlFieldsQuery, query SELECT COUNT(longCol), shortCol 
>>> FROM AllTypes WHERE shortCol > ? GROUP BY shortCol
>>> Query: SqlFieldsQuery [sql=SELECT COUNT(longCol), shortCol FROM AllTypes 
>>> WHERE shortCol > ? GROUP BY shortCol, args=[1], collocated=false]
[14:52:52,517][ERROR][main][GridMapQueryExecutor] Failed to execute local 
query: GridQueryRequest [reqId=1, pageSize=1024, space=cache_0001, 
qrys=[GridCacheSqlQuery [qry=SELECT
COUNT(LONGCOL) __C0,
SHORTCOL __C1
FROM "cache_0001".ALLTYPES
WHERE SHORTCOL > ?1
GROUP BY SHORTCOL, params=[1], paramIdxs=[0], paramsSize=1, 
cols={__C0=GridSqlType [type=5, scale=0, precision=19, displaySize=20, 
sql=BIGINT], __C1=GridSqlType [type=19, scale=0, precision=2147483647, 
displaySize=2147483647, sql=OTHER]}, alias=null]], 
topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], extraSpaces=null, 
parts=null]
class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query.
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:847)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:870)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:454)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:184)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1065)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:572)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:971)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
at 
org.apache.ignite.examples.datagrid.CacheQueryFailures.runQuery(CacheQueryFailures.java:120)
at 
org.apache.ignite.examples.datagrid.CacheQueryFailures.main(CacheQueryFailures.java:83)
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: org.h2.jdbc.JdbcSQLException: Шестнадцатиричная строка содержит 
нечетное количество символов: "1"
Hexadecimal string with odd number of characters: "1"; SQL statement:
SELECT
COUNT(LONGCOL) __C0,
SHORTCOL __C1
FROM "cache_0001".ALLTYPES
WHERE SHORTCOL > ?1
GROUP BY SHORTCOL [90003-175]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
at org.h2.message.DbException.get(DbException.java:172)
at org.h2.message.DbException.get(DbException.java:149)
at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:944)
at org.h2.value.Value.convertTo(Value.java:847)
at org.h2.table.Table.compareTypeSave(Table.java:1068)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.compareValues(GridH2IndexBase.java:143)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:125)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex$ComparableRow.compareTo(GridH2TreeIndex.java:433)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex$ComparableRow.compareTo(GridH2TreeIndex.java:415)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$AbstractIter.cmp(GridOffHeapSnapTreeMap.java:3454)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$AbstractIter.pushFirst(GridOffHeapSnapTreeMap.java:3492)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$AbstractIter.(GridOffHeapSnapTreeMap.java:3440)
at 

[jira] [Created] (IGNITE-3396) Aggregation query with where clase failed

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-3396:
-

 Summary: Aggregation query with where clase failed
 Key: IGNITE-3396
 URL: https://issues.apache.org/jira/browse/IGNITE-3396
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: Sergey Kozlov
Priority: Critical


1. Extract everything from attached zip file into examples directory
2. Run {{CacheQueryFailures query3}}. It fails:
{noformat}
[14:52:52] Ignite node started OK (id=2821d4cc)
[14:52:52] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=3.5GB]
>>> initialize 300 keys
>>> run query3, type: SqlFieldsQuery, query SELECT COUNT(longCol), shortCol 
>>> FROM AllTypes WHERE shortCol > ? GROUP BY shortCol
>>> Query: SqlFieldsQuery [sql=SELECT COUNT(longCol), shortCol FROM AllTypes 
>>> WHERE shortCol > ? GROUP BY shortCol, args=[1], collocated=false]
[14:52:52,517][ERROR][main][GridMapQueryExecutor] Failed to execute local 
query: GridQueryRequest [reqId=1, pageSize=1024, space=cache_0001, 
qrys=[GridCacheSqlQuery [qry=SELECT
COUNT(LONGCOL) __C0,
SHORTCOL __C1
FROM "cache_0001".ALLTYPES
WHERE SHORTCOL > ?1
GROUP BY SHORTCOL, params=[1], paramIdxs=[0], paramsSize=1, 
cols={__C0=GridSqlType [type=5, scale=0, precision=19, displaySize=20, 
sql=BIGINT], __C1=GridSqlType [type=19, scale=0, precision=2147483647, 
displaySize=2147483647, sql=OTHER]}, alias=null]], 
topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], extraSpaces=null, 
parts=null]
class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query.
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:847)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:870)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:454)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:184)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1065)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:572)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:971)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
at 
org.apache.ignite.examples.datagrid.CacheQueryFailures.runQuery(CacheQueryFailures.java:120)
at 
org.apache.ignite.examples.datagrid.CacheQueryFailures.main(CacheQueryFailures.java:83)
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: org.h2.jdbc.JdbcSQLException: Шестнадцатиричная строка содержит 
нечетное количество символов: "1"
Hexadecimal string with odd number of characters: "1"; SQL statement:
SELECT
COUNT(LONGCOL) __C0,
SHORTCOL __C1
FROM "cache_0001".ALLTYPES
WHERE SHORTCOL > ?1
GROUP BY SHORTCOL [90003-175]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
at org.h2.message.DbException.get(DbException.java:172)
at org.h2.message.DbException.get(DbException.java:149)
at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:944)
at org.h2.value.Value.convertTo(Value.java:847)
at org.h2.table.Table.compareTypeSave(Table.java:1068)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.compareValues(GridH2IndexBase.java:143)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:125)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex$ComparableRow.compareTo(GridH2TreeIndex.java:433)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex$ComparableRow.compareTo(GridH2TreeIndex.java:415)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$AbstractIter.cmp(GridOffHeapSnapTreeMap.java:3454)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$AbstractIter.pushFirst(GridOffHeapSnapTreeMap.java:3492)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$AbstractIter.(GridOffHeapSnapTreeMap.java:3440)
at 

Re: IGNITE-3337

[Andrey Novikov]

Hi Saikat!

I’ve just reviewed and merged your pull request.

Thank you for your contribution!

—
Andrey

On Wed, Jun 29, 2016 at 3:25 AM, Saikat Maitra 
wrote:

> Hello Andrey,
>
> I have updated the PR. Please review and share feedback.
>
> https://github.com/apache/ignite/pull/816
>
> Regards
> Saikat
>
> On Thu, Jun 23, 2016 at 8:41 PM, Saikat Maitra 
> wrote:
>
> > Thank you Andrey
> >
> > I will update the PR accordingly.
> >
> > Regards
> > Saikat
> >
> > On Thu, Jun 23, 2016 at 12:33 PM, Andrey Novikov 
> > wrote:
> >
> >> Saint,
> >>
> >> I've reviewed your PR and left comments in the ticket.
> >>
> >>
> >> On Tue, Jun 21, 2016 at 1:14 AM, Saikat Maitra  >
> >> wrote:
> >>
> >> > Hi Alexey , Sergey
> >> >
> >> > Thank you for your time and reviewing the PR. I agree we can deprecate
> >> > cacheName for metadata command. I have updated the files and request
> >> you to
> >> > review the changes.
> >> >
> >> > Also can you please share where the docs are hosted and I can then
> >> update
> >> > the rest api doc.
> >> >
> >> > Regards
> >> > Saikat
> >> >
> >> > On Mon, Jun 20, 2016 at 3:08 PM, Sergey Kozlov 
> >> > wrote:
> >> >
> >> > > Hi Saikat and Alexey.
> >> > >
> >> > > I think that the solution suggested by Alexey is simple one.
> Actually
> >> > > null-named cache is widely used for now and we can't remove it (or
> at
> >> > least
> >> > > we should re-think the approach for such caches). On the other hand
> >> the
> >> > > size of metadata returned by REST command even for dozen caches is
> not
> >> > > large and can be filtered (iterated) on the client side. So I
> suppose
> >> the
> >> > > ticket should be updated according suggested approach.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On Mon, Jun 20, 2016 at 12:28 PM, Alexey Kuznetsov <
> >> > > akuznet...@gridgain.com>
> >> > > wrote:
> >> > >
> >> > > > Hi, Saikat
> >> > > >
> >> > > > I reviewed you PR and I think we should deprecate "cacheName"
> >> > parameter
> >> > > > in metadata command.
> >> > > >
> >> > > > In current implementation when "cacheName" was not specified that
> >> means
> >> > > to
> >> > > > get "default" cache (with name=null)
> >> > > > And now it will be impossible to take metadata for such cache.
> >> > > >
> >> > > > But I think for this command there is a little sense to extract
> >> > metadata
> >> > > > for single cache,
> >> > > >  because any way on server side they will be extracted for all
> >> caches.
> >> > > > See:
> >> > > >
> >> > >
> >> >
> >>
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager#sqlMetadata
> >> > > > line 999.
> >> > > >
> >> > > > Also for performance reason it is much faster to get all metadata
> at
> >> > > once.
> >> > > >
> >> > > > So, I suggest - to deprecate "cacheName" parameter and fix
> >> > documentation.
> >> > > >
> >> > > > Thoughts?
> >> > > >
> >> > > >
> >> > > > On Sun, Jun 19, 2016 at 10:42 PM, Saikat Maitra <
> >> > saikat.mai...@gmail.com
> >> > > >
> >> > > > wrote:
> >> > > >
> >> > > > > Hello,
> >> > > > >
> >> > > > > I have raised the PR[1] for the following Jira ticket[2].
> >> > > > >
> >> > > > > Please review and let me know any feedback
> >> > > > >
> >> > > > > Regards
> >> > > > > Saikat
> >> > > > >
> >> > > > > [1] https://github.com/apache/ignite/pull/816
> >> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-3337
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Alexey Kuznetsov
> >> > > > GridGain Systems
> >> > > > www.gridgain.com
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Sergey Kozlov
> >> > > GridGain Systems
> >> > > www.gridgain.com
> >> > >
> >> >
> >>
> >
> >
>

[GitHub] ignite pull request #816: IGNITE-3337 REST HTTP: metadata command returns al...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3395) .NET: TestPutGetAsyncMultithreaded failure

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3395:
--

 Summary: .NET: TestPutGetAsyncMultithreaded failure
 Key: IGNITE-3395
 URL: https://issues.apache.org/jira/browse/IGNITE-3395
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.7


In PR 835
http://149.202.210.143:8111/viewLog.html?buildId=273385



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

[GitHub] ignite pull request #840: IGNITE-3329 .NET: Fix TestDeployNodeSingleton test...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-3329 .NET: Fix TestDeployNodeSingleton test failures



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

$ git pull https://github.com/ptupitsyn/ignite ignite-3329

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

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


commit eb0fdd1bd9ba1344881b897c865409c92c1a6fb0
Author: Pavel Tupitsyn 
Date:   2016-06-29T09:41:43Z

IGNITE-3329 .NET: TestDeployNodeSingleton fails sporadically

commit 4052374b3c2f5c7944de163470be583838f24903
Author: Pavel Tupitsyn 
Date:   2016-06-29T10:12:01Z

cleanup

commit 6ebfafeb8e4e732589b531719028994193623a0f
Author: Pavel Tupitsyn 
Date:   2016-06-29T10:17:19Z

Fix callback NPE




---
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 #836: IGNITE-3371 .NET: Configure PlatformAffinityFuncti...

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

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


---
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: Fwd: TC access

[Anton Vinogradov]

Alexey,

I've fixed adress.

Seems, you have good vision how to describe TeamCity usage, could you pleae
create it?


On Wed, Jun 29, 2016 at 10:56 AM, Alexey Kuznetsov 
wrote:

> Anton,
>
> I noticed that wiki page
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation
> refers to TC by IP and not by name http://ci.ignite.apache.org
>
> And I also agree with Dima - we could have a special paragraph on that page
> about TC.
> In current version info about TC is spread all over that page.
> IMHO it will be very informative to have a special TC paragraph.
>
>
>
> On Wed, Jun 29, 2016 at 2:11 PM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Dmitriy,
> >
> > TeamCity usage is a part of contribution process.
> > The only reason for contributor to use TeamCity is to check pull-request.
> > Thats why TeamCity usage explained at " Create GitHub pull-request
> > -> Creation" section.
> >
> >
> > On Wed, Jun 29, 2016 at 12:46 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > wrote:
> >
> > > Anton, I think the documentation for TeamCity if well-belied and hardly
> > > noticeable. Do you mind creating a separate section for it, so everyone
> > > will know how their PR will be tested?
> > >
> > > On Tue, Jun 28, 2016 at 12:25 AM, Anton Vinogradov <
> > > avinogra...@gridgain.com
> > > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > 1) Testing at TeamCity already documented here:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation
> > > > 2) We cannot trigger every pullrequest testing automaticaly because
> it
> > > > takes ~1.5 hours to test only one, but we have more than 50 commits
> per
> > > day
> > > > at active pullrequests.
> > > > We have automatical testing only for master and release branches.
> > > >
> > > > On Tue, Jun 28, 2016 at 9:03 AM, mabiao  wrote:
> > > >
> > > > > I wonder if we could make the continuous integration test be
> > triggered
> > > > > automatically?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -- 原始邮件 --
> > > > > 发件人: "Dmitriy Setrakyan";;
> > > > > 发送时间: 2016年6月28日(星期二) 中午1:08
> > > > > 收件人: "dev";
> > > > >
> > > > > 主题: Fwd: TC access
> > > > >
> > > > >
> > > > >
> > > > > Anton, do you mind documenting this for posterity?
> > > > >
> > > > > -- Forwarded message --
> > > > > From: Alexey Kuznetsov 
> > > > > Date: Mon, Jun 27, 2016 at 10:07 PM
> > > > > Subject: Re: TC access
> > > > > To: u...@ignite.apache.org
> > > > >
> > > > >
> > > > > Hmmm,...
> > > > >
> > > > > Seems NO. I searched over web site and wiki and not found anything.
> > > > > We could ask Anton as the most experienced person to add
> appropriate
> > > page
> > > > > to wiki.
> > > > >
> > > > > On Tue, Jun 28, 2016 at 12:02 PM, Dmitriy Setrakyan <
> > > > > dsetrak...@gridgain.com
> > > > > > wrote:
> > > > >
> > > > > > Alexey, is this documented?
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Jun 27, 2016, at 9:33 PM, Alexey Kuznetsov <
> > > akuznet...@gridgain.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > Alexandre,
> > > > > >
> > > > > > If you need to test your PR with existing tests just:
> > > > > >  1. Go to http://ci.ignite.apache.org
> > > > > >  2. Register if needed /  Loging.
> > > > > >  3. Select appropriate test / all tests and run them with
> > specifying
> > > > > > number of your PR.
> > > > > >
> > > > > > If you are going to add new tests you need admin privileges for
> > that.
> > > > > > I think Anton can help with this.
> > > > > >
> > > > > >
> > > > > > On Tue, Jun 28, 2016 at 2:04 AM, Alexandre Boudnik <
> > > > > > alexander.boud...@gmail.com> wrote:
> > > > > >
> > > > > >> I don't need access to TC console, I need to have my pull
> requests
> > > > > tested.
> > > > > >> Take care,
> > > > > >> Alexandre "Sasha" Boudnik
> > > > > >>
> > > > > >> call me via Google Voice:
> > > > > >> 1(405) BUDNIKA
> > > > > >> 1(405) 283-6452
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> On Mon, Jun 27, 2016 at 2:07 PM, Dmitriy Setrakyan
> > > > > >>  wrote:
> > > > > >> > I just realized that I don’t have a link either. Anton, do you
> > > mind
> > > > > >> adding
> > > > > >> > the link to TC to the community dropdown on the website?
> > > > > >> >
> > > > > >> > On Mon, Jun 27, 2016 at 10:28 AM, Alexandre Boudnik
> > > > > >> >  wrote:
> > > > > >> >>
> > > > > >> >> Hello,
> > > > > >> >>
> > > > > >> >> In order to use Ignite's TeamCity, could you provide myself
> > with
> > > > > >> access to
> > > > > >> >> it?
> > > > > >> >>
> > > > > >> >> Take care,
> > > > > >> >> Alexandre "Sasha" Boudnik
> > > > > >> >>
> > > > > >> >> call me via Google Voice:
> > > > > >> >> 1(405) BUDNIKA
> > > > > >> >> 1(405) 283-6452
> 

Re: Fwd: TC access

[Alexey Kuznetsov]

Anton,

I noticed that wiki page
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation
refers to TC by IP and not by name http://ci.ignite.apache.org

And I also agree with Dima - we could have a special paragraph on that page
about TC.
In current version info about TC is spread all over that page.
IMHO it will be very informative to have a special TC paragraph.



On Wed, Jun 29, 2016 at 2:11 PM, Anton Vinogradov 
wrote:

> Dmitriy,
>
> TeamCity usage is a part of contribution process.
> The only reason for contributor to use TeamCity is to check pull-request.
> Thats why TeamCity usage explained at " Create GitHub pull-request
> -> Creation" section.
>
>
> On Wed, Jun 29, 2016 at 12:46 AM, Dmitriy Setrakyan  >
> wrote:
>
> > Anton, I think the documentation for TeamCity if well-belied and hardly
> > noticeable. Do you mind creating a separate section for it, so everyone
> > will know how their PR will be tested?
> >
> > On Tue, Jun 28, 2016 at 12:25 AM, Anton Vinogradov <
> > avinogra...@gridgain.com
> > > wrote:
> >
> > > Hi All,
> > >
> > > 1) Testing at TeamCity already documented here:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation
> > > 2) We cannot trigger every pullrequest testing automaticaly because it
> > > takes ~1.5 hours to test only one, but we have more than 50 commits per
> > day
> > > at active pullrequests.
> > > We have automatical testing only for master and release branches.
> > >
> > > On Tue, Jun 28, 2016 at 9:03 AM, mabiao  wrote:
> > >
> > > > I wonder if we could make the continuous integration test be
> triggered
> > > > automatically?
> > > >
> > > >
> > > >
> > > >
> > > > -- 原始邮件 --
> > > > 发件人: "Dmitriy Setrakyan";;
> > > > 发送时间: 2016年6月28日(星期二) 中午1:08
> > > > 收件人: "dev";
> > > >
> > > > 主题: Fwd: TC access
> > > >
> > > >
> > > >
> > > > Anton, do you mind documenting this for posterity?
> > > >
> > > > -- Forwarded message --
> > > > From: Alexey Kuznetsov 
> > > > Date: Mon, Jun 27, 2016 at 10:07 PM
> > > > Subject: Re: TC access
> > > > To: u...@ignite.apache.org
> > > >
> > > >
> > > > Hmmm,...
> > > >
> > > > Seems NO. I searched over web site and wiki and not found anything.
> > > > We could ask Anton as the most experienced person to add appropriate
> > page
> > > > to wiki.
> > > >
> > > > On Tue, Jun 28, 2016 at 12:02 PM, Dmitriy Setrakyan <
> > > > dsetrak...@gridgain.com
> > > > > wrote:
> > > >
> > > > > Alexey, is this documented?
> > > > >
> > > > >
> > > > >
> > > > > On Jun 27, 2016, at 9:33 PM, Alexey Kuznetsov <
> > akuznet...@gridgain.com
> > > >
> > > > > wrote:
> > > > >
> > > > > Alexandre,
> > > > >
> > > > > If you need to test your PR with existing tests just:
> > > > >  1. Go to http://ci.ignite.apache.org
> > > > >  2. Register if needed /  Loging.
> > > > >  3. Select appropriate test / all tests and run them with
> specifying
> > > > > number of your PR.
> > > > >
> > > > > If you are going to add new tests you need admin privileges for
> that.
> > > > > I think Anton can help with this.
> > > > >
> > > > >
> > > > > On Tue, Jun 28, 2016 at 2:04 AM, Alexandre Boudnik <
> > > > > alexander.boud...@gmail.com> wrote:
> > > > >
> > > > >> I don't need access to TC console, I need to have my pull requests
> > > > tested.
> > > > >> Take care,
> > > > >> Alexandre "Sasha" Boudnik
> > > > >>
> > > > >> call me via Google Voice:
> > > > >> 1(405) BUDNIKA
> > > > >> 1(405) 283-6452
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Mon, Jun 27, 2016 at 2:07 PM, Dmitriy Setrakyan
> > > > >>  wrote:
> > > > >> > I just realized that I don’t have a link either. Anton, do you
> > mind
> > > > >> adding
> > > > >> > the link to TC to the community dropdown on the website?
> > > > >> >
> > > > >> > On Mon, Jun 27, 2016 at 10:28 AM, Alexandre Boudnik
> > > > >> >  wrote:
> > > > >> >>
> > > > >> >> Hello,
> > > > >> >>
> > > > >> >> In order to use Ignite's TeamCity, could you provide myself
> with
> > > > >> access to
> > > > >> >> it?
> > > > >> >>
> > > > >> >> Take care,
> > > > >> >> Alexandre "Sasha" Boudnik
> > > > >> >>
> > > > >> >> call me via Google Voice:
> > > > >> >> 1(405) BUDNIKA
> > > > >> >> 1(405) 283-6452
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Alexey Kuznetsov
> > > > > GridGain Systems
> > > > > www.gridgain.com
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: Fwd: TC access

[Anton Vinogradov]

Dmitriy,

TeamCity usage is a part of contribution process.
The only reason for contributor to use TeamCity is to check pull-request.
Thats why TeamCity usage explained at " Create GitHub pull-request
-> Creation" section.


On Wed, Jun 29, 2016 at 12:46 AM, Dmitriy Setrakyan 
wrote:

> Anton, I think the documentation for TeamCity if well-belied and hardly
> noticeable. Do you mind creating a separate section for it, so everyone
> will know how their PR will be tested?
>
> On Tue, Jun 28, 2016 at 12:25 AM, Anton Vinogradov <
> avinogra...@gridgain.com
> > wrote:
>
> > Hi All,
> >
> > 1) Testing at TeamCity already documented here:
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation
> > 2) We cannot trigger every pullrequest testing automaticaly because it
> > takes ~1.5 hours to test only one, but we have more than 50 commits per
> day
> > at active pullrequests.
> > We have automatical testing only for master and release branches.
> >
> > On Tue, Jun 28, 2016 at 9:03 AM, mabiao  wrote:
> >
> > > I wonder if we could make the continuous integration test be triggered
> > > automatically?
> > >
> > >
> > >
> > >
> > > -- 原始邮件 --
> > > 发件人: "Dmitriy Setrakyan";;
> > > 发送时间: 2016年6月28日(星期二) 中午1:08
> > > 收件人: "dev";
> > >
> > > 主题: Fwd: TC access
> > >
> > >
> > >
> > > Anton, do you mind documenting this for posterity?
> > >
> > > -- Forwarded message --
> > > From: Alexey Kuznetsov 
> > > Date: Mon, Jun 27, 2016 at 10:07 PM
> > > Subject: Re: TC access
> > > To: u...@ignite.apache.org
> > >
> > >
> > > Hmmm,...
> > >
> > > Seems NO. I searched over web site and wiki and not found anything.
> > > We could ask Anton as the most experienced person to add appropriate
> page
> > > to wiki.
> > >
> > > On Tue, Jun 28, 2016 at 12:02 PM, Dmitriy Setrakyan <
> > > dsetrak...@gridgain.com
> > > > wrote:
> > >
> > > > Alexey, is this documented?
> > > >
> > > >
> > > >
> > > > On Jun 27, 2016, at 9:33 PM, Alexey Kuznetsov <
> akuznet...@gridgain.com
> > >
> > > > wrote:
> > > >
> > > > Alexandre,
> > > >
> > > > If you need to test your PR with existing tests just:
> > > >  1. Go to http://ci.ignite.apache.org
> > > >  2. Register if needed /  Loging.
> > > >  3. Select appropriate test / all tests and run them with specifying
> > > > number of your PR.
> > > >
> > > > If you are going to add new tests you need admin privileges for that.
> > > > I think Anton can help with this.
> > > >
> > > >
> > > > On Tue, Jun 28, 2016 at 2:04 AM, Alexandre Boudnik <
> > > > alexander.boud...@gmail.com> wrote:
> > > >
> > > >> I don't need access to TC console, I need to have my pull requests
> > > tested.
> > > >> Take care,
> > > >> Alexandre "Sasha" Boudnik
> > > >>
> > > >> call me via Google Voice:
> > > >> 1(405) BUDNIKA
> > > >> 1(405) 283-6452
> > > >>
> > > >>
> > > >>
> > > >> On Mon, Jun 27, 2016 at 2:07 PM, Dmitriy Setrakyan
> > > >>  wrote:
> > > >> > I just realized that I don’t have a link either. Anton, do you
> mind
> > > >> adding
> > > >> > the link to TC to the community dropdown on the website?
> > > >> >
> > > >> > On Mon, Jun 27, 2016 at 10:28 AM, Alexandre Boudnik
> > > >> >  wrote:
> > > >> >>
> > > >> >> Hello,
> > > >> >>
> > > >> >> In order to use Ignite's TeamCity, could you provide myself with
> > > >> access to
> > > >> >> it?
> > > >> >>
> > > >> >> Take care,
> > > >> >> Alexandre "Sasha" Boudnik
> > > >> >>
> > > >> >> call me via Google Voice:
> > > >> >> 1(405) BUDNIKA
> > > >> >> 1(405) 283-6452
> > > >> >
> > > >> >
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>

[GitHub] ignite pull request #839: IGNITE-3391 add param tableName for queryEntity

[f7753]

GitHub user f7753 opened a pull request:

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

IGNITE-3391 add param tableName for queryEntity

Currently the SQL table name is always the same as class name. In some 
cases user may want to override this and use different name in queries.
`tableName ` property is added to `QueryEntity`.

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

$ git pull https://github.com/f7753/ignite tableName

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

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


commit b585a6a40063b5f07e5566f08b76438e7bc6dd96
Author: f7753 
Date:   2016-06-29T06:39:02Z

IGNITE-3391 add tableName for QueryEntity

commit ae90c494610b86ed4d5dc055c449da72fb130d4a
Author: f7753 
Date:   2016-06-29T06:46:23Z

IGNITE-3391 modified the L207




---
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-3394) Failed to load data from Oracle DB with type TIMESTAMP(6)

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3394:
-

 Summary: Failed to load data from Oracle DB with type TIMESTAMP(6)
 Key: IGNITE-3394
 URL: https://issues.apache.org/jira/browse/IGNITE-3394
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
 Fix For: 1.7






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