[jira] [Created] (IGNITE-5241) Redis hash table support

[Roman Shtykh (JIRA)]

Roman Shtykh created IGNITE-5241:


 Summary: Redis hash table support
 Key: IGNITE-5241
 URL: https://issues.apache.org/jira/browse/IGNITE-5241
 Project: Ignite
  Issue Type: New Feature
Reporter: Roman Shtykh
Assignee: Roman Shtykh






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5240) Web console: Invalid docker repository name in compose file

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-5240:
-

 Summary: Web console: Invalid docker repository name in compose 
file
 Key: IGNITE-5240
 URL: https://issues.apache.org/jira/browse/IGNITE-5240
 Project: Ignite
  Issue Type: Bug
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko


in docker/compose/docker-compose.yml



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5239) Web Console: Add an option to show full stack trace on Queries screen

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5239:


 Summary: Web Console: Add an option to show full stack trace on 
Queries screen
 Key: IGNITE-5239
 URL: https://issues.apache.org/jira/browse/IGNITE-5239
 Project: Ignite
  Issue Type: Task
  Components: UI, wizards
Affects Versions: 2.0
Reporter: Alexey Kuznetsov
 Fix For: 2.1


In some situations we need full stack trace to show real error like: 
{code}
Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on table 
"city" violates foreign key constraint "country_capital_fkey" on table "country"
  Detail: Key (id)=(3503) is still referenced from table "country".
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5238:
---

 Summary: Ignite Spark can't be used with Ignite REST
 Key: IGNITE-5238
 URL: https://issues.apache.org/jira/browse/IGNITE-5238
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Denis Magda
Priority: Blocker
 Fix For: 2.1


{{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
former imports some legacy version of Jackson library and the following 
exception is thrown from an IDEA in attempt to use Ignite+Spark application:

{code}
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
at 
org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
at 
org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
at 
org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
at 
org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
Jackson version: 2.8.8
at 
com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
at 
com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
at 
com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
at 
org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
at 
org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
... 11 more
{code}

To reproduce:
- Download this project and open in IntellijIdea: 
https://github.com/dmagda/IgniteSparkIoT
- Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
imported.
- Start a cluster node with IgniteNodeStartup
- Start SparkStreamerStartup and you will get the error above.

Looks like the Ignite REST module has to be upgraded to the recent Jackson 
version.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5237) JDBC Driver: support client info

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-5237:


 Summary: JDBC Driver: support client info
 Key: IGNITE-5237
 URL: https://issues.apache.org/jira/browse/IGNITE-5237
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5236) JDBC Driver: implement Connection.isValid througn PING message

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-5236:


 Summary: JDBC Driver: implement Connection.isValid througn PING 
message
 Key: IGNITE-5236
 URL: https://issues.apache.org/jira/browse/IGNITE-5236
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5235) JDBC Driver: impelemnt prepared statement

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-5235:


 Summary: JDBC Driver: impelemnt prepared statement
 Key: IGNITE-5235
 URL: https://issues.apache.org/jira/browse/IGNITE-5235
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5234) JDBC Driver: support connection and query timeout

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-5234:


 Summary: JDBC Driver: support connection and query timeout
 Key: IGNITE-5234
 URL: https://issues.apache.org/jira/browse/IGNITE-5234
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5233) JDBC Driver: implement metadata support

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-5233:


 Summary: JDBC Driver: implement metadata support 
 Key: IGNITE-5233
 URL: https://issues.apache.org/jira/browse/IGNITE-5233
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1960: Ignite 4763 review

[agura]

GitHub user agura opened a pull request:

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

Ignite 4763 review



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

$ git pull https://github.com/agura/incubator-ignite ignite-4763-review

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

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


commit 106994c1381e25598d498feac2a71dcb3b5f0df4
Author: NSAmelchev 
Date:   2017-04-26T13:17:19Z

doSetRollbackOnly method to be implemented in the SpringTransactionManager

commit 47f78550f36bf455b628f9610713da7dab0405a4
Author: NSAmelchev 
Date:   2017-04-27T08:24:19Z

Refactoring

commit 8dabb73a520a8dc26e57581de1bf78becda44336
Author: NSAmelchev 
Date:   2017-04-27T08:34:44Z

one-line javadoc

commit 302ef223a63598c451f3ca4ad7c899009cfe032f
Author: NSAmelchev 
Date:   2017-04-27T08:36:17Z

one-line javadoc doSetRollbackOnly

commit 7f5636ca2fc95e797a215d59442301b726a022c8
Author: NSAmelchev 
Date:   2017-04-28T09:33:07Z

add testParticipatingInExistingTransactions

commit f6cbeaac6478dc607b17ce6bb0b14cbf7d3e5532
Author: NSAmelchev 
Date:   2017-04-28T10:36:33Z

Refactoring method

commit d10440d4e2ba09b24d6ea90ecff9addee2312548
Author: NSAmelchev 
Date:   2017-04-28T11:44:12Z

Java 7 compability fix

commit 3287cff8fc170b307a075b8a790857403c939f81
Author: agura 
Date:   2017-05-16T15:40:33Z

ignite-4763 Review




---
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 #1959: IGNITE-4831 fixed (Add an option to disable MBean...

[rfqu]

GitHub user rfqu opened a pull request:

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

IGNITE-4831 fixed (Add an option to disable MBeans).



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

$ git pull https://github.com/rfqu/ignite ignite-4831

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

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


commit d4fe48d417548739b60a4ccbd5c24fb3e85f6346
Author: rfqu 
Date:   2017-05-16T14:48:37Z

IGNITE-4831 fixed (Add an option to disable MBeans).




---
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 #1957: Ignite 4831

[rfqu]

Github user rfqu closed the pull request at:

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


---
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 #1958: Ignite 5052

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

Ignite 5052



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

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

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

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


commit aa48bab0848e776754638bce07097b16006cd548
Author: Alexander Paschenko 
Date:   2017-04-21T16:05:06Z

IGNITE-5052 CREATE TABLE first steps

commit 7f04ca5811e4680f75996b30a73c7987eec19a25
Author: Alexander Paschenko 
Date:   2017-04-24T17:20:22Z

IGNITE-5052 CREATE TABLE parsing contd

commit 9ba38c926420b4f6d822885cb595c69de8a518c1
Author: Alexander Paschenko 
Date:   2017-04-25T14:38:57Z

Merge remote-tracking branch 'apache/ignite-2.0' into ignite-5052

commit d6cdb6ab208e24c65e2bc5d6ea8c88344b3725d6
Author: Alexander Paschenko 
Date:   2017-04-25T15:11:37Z

IGNITE-5052 CREATE TABLE parsing contd

commit 0be9b0877031bafda674949b13db6b3492bd8fe8
Author: Alexander Paschenko 
Date:   2017-04-26T08:14:29Z

IGNITE-5052 Dynamic local CREATE TABLE

commit 6569d53e91ef698c7955939cbf3681ebaf68a6c2
Author: Alexander Paschenko 
Date:   2017-04-26T18:55:23Z

IGNITE-5052 CREATE/DROP TABLE + few tests

commit a7e409b5cea3513e9dcdc242fbde057a99ad84a4
Author: Alexander Paschenko 
Date:   2017-04-27T18:01:17Z

IGNITE-5052 GridSqlCreateTable.toSql

commit 7d3325e1809fe33cb183ef8de3559ee0b2e40048
Author: Alexander Paschenko 
Date:   2017-04-28T11:46:42Z

Merge remote-tracking branch 'apache/ignite-2.0' into ignite-5052

commit b740701d61f7728c78b117bb5edbc60f0cba46e9
Author: Alexander Paschenko 
Date:   2017-04-28T11:51:51Z

Post merge fix

commit e650908cbf3358de731c7da606b22606834dfa85
Author: devozerov 
Date:   2017-05-05T11:02:43Z

Merge branch 'master' into ignite-5052

commit afda2220361158434e0b2f86f6d8f21c0342babf
Author: Alexander Paschenko 
Date:   2017-05-10T10:54:50Z

Merge branch 'master' into ignite-5052

commit dc5f68b9224adcaf1bdde2a6e2606d33a5549993
Author: Alexander Paschenko 
Date:   2017-05-10T19:03:01Z

IGNITE-5052 Review fixes

commit 888eb168685f6e63541ef7c3b096e32cae54fd4d
Author: Alexander Paschenko 
Date:   2017-05-11T11:31:15Z

IGNITE-5052 Review fixes - contd

commit 9a26a678f554c550739d06fef6ab371afb4c46f6
Author: Alexander Paschenko 
Date:   2017-05-11T11:32:51Z

Merge remote-tracking branch 'apache/master' into ignite-5052

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryIndexing.java

commit 7f377c4de364907e27d143f1ae8263dcd3125db0
Author: devozerov 
Date:   2017-05-16T08:07:22Z

Merge branch 'master' into ignite-5052

commit 41e2f64cad6dfe33c28266281229b86b413e86a2
Author: devozerov 
Date:   2017-05-16T08:56:40Z

Minors.




---
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: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

[Alexey Kuznetsov]

Alexey Goncharuk,

I take a look at source code and noticed classes with names
like: GridCacheDatabaseSharedManager.java
As far as I remember we decided that "Grid" is a kind of "deprecated"
prefix?

What do you think? Does it make sense to rename?

On Tue, May 16, 2017 at 9:06 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Denis,
>
> Headers are updated, RAT check is passing now.
>
> 2017-05-16 2:37 GMT+03:00 Denis Magda :
>
> > The receipt of the software grant (the persistent store) was acknowledged
> > by Craig Russel.
> >
> > Now, we need to move on with this
> >
> > > In the meanwhile, I’ve prepared the IP Clearance page referring to the
> > template below but failed to commit the changes to ASF repo:
> > > http://incubator.apache.org/ip-clearance/ip-clearance-template.html
> > >
> > > *Roman S.*, *Cos*, could you help me with this by granting karma or
> > committing the form from under your account?
> >
> > Roman, Cos, could you help with this?
> >
> > *Alex G.*, please add Apache 2.0 copyrights to all source files that are
> > going to be donated. Presently there is no copyright at all.
> >
> > Everyone interested please spend some time exploring the store's docs and
> > sources shared in my previous email. If no one has any concerns I will
> > proceed with the donation formalities.
> >
> > —
> > Denis
> >
> > > On May 12, 2017, at 2:59 PM, Denis Magda  wrote:
> > >
> > > Folks,
> > >
> > > The repository with the donation is ready and available for review:
> > > https://github.com/agoncharuk/ignite/tree/pds-donate
> > >
> > > Big and main part of the sources is aggregated in “modules/pds”. The
> > rest, that connects Apache Ignite memory architecture and SQL engine is
> > under “core” and “indexing” modules. Alex Goncharuk should be able to
> point
> > to specific files or commits if required.
> > >
> > > Here is a description:
> > > * Persistent Store Overview: https://cwiki.apache.org/
> > confluence/display/IGNITE/Persistent+Store+Overview
> > > * Persistent Store Internal Design: https://cwiki.apache.org/
> > confluence/display/IGNITE/Persistent+Store+Internal+Design
> > >
> > > The SGA will be signed and sent on Monday.
> > >
> > > In the meanwhile, I’ve prepared the IP Clearance page referring to the
> > template below but failed to commit the changes to ASF repo:
> > > http://incubator.apache.org/ip-clearance/ip-clearance-template.html
> > >
> > > *Roman S.*, *Cos*, could you help me with this by granting karma or
> > committing the form from under your account?
> > >
> > > —
> > > Denis
> > >
> > >> On Apr 25, 2017, at 9:56 AM, Konstantin Boudnik 
> > wrote:
> > >>
> > >> While no one is suggesting an IP trap laid out in the non-SGA'ed code
> > >> in this particular case, we don't want to setup a precedent like this.
> > >>
> > >> From the overall ASF perspective I +1 what Roman has just said.
> > >>
> > >> Thanks,
> > >> --
> > >> Take care,
> > >> Konstantin (Cos) Boudnik
> > >>
> > >>
> > >> On Wed, Apr 19, 2017 at 11:41 PM, Roman Shaposhnik <
> > ro...@shaposhnik.org> wrote:
> > >>> On Wed, Apr 19, 2017 at 6:21 PM, Dmitriy Setrakyan
> > >>>  wrote:
> >  On Wed, Apr 19, 2017 at 6:00 PM, Konstantin Boudnik  >
> > wrote:
> > 
> > > On Tue, Apr 18, 2017 at 11:54PM, Dmitriy Setrakyan wrote:
> > >>
> > >> Would a standard SGA suffice here?
> > >>
> > >> I believe that ASF guidelines suggest that a discussion should
> > happen
> > >> first. Once the community gets enough information, we will move to
> > a PMC
> > >> vote. I was under the impression that once the PMC vote passes,
> > then the
> > >> SGA should be provided. Or does GridGain need to provide a signed
> > SGA
> > > right
> > >> away?
> > >
> > > That reminds me of that Pelosi's self-inflicted conundrum of "In
> > order
> > > to see the bill, we should pass the bill" ;)
> > >
> > 
> >  Haha :)
> > 
> >  SGA != code. In my view, the code should be provided to the
> community
> > for a
> >  review. But I am struggling to see why should an SGA be signed prior
> > to the
> >  community accepting the donation.
> > >>>
> > >>> There's no such thing as SGA without a reference to a code base.
> > >>>
> > >>> Also, as I explained -- as a community member I would refuse to look
> > >>> at the code base that doesn't have a proper licensing attached to it.
> > >>> SGA established this kind of proper licensing.
> > >>>
> > >>> Now, SGA is deinetly not the only way to do so, but it is the easiest
> > >>> and since you'd have to do it anyway the most convenient for the
> > >>> community.
> > >>>
> > >>> Thanks,
> > >>> Roman.
> > >
> >
> >
>



-- 
Alexey Kuznetsov

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

[Alexey Goncharuk]

Denis,

Headers are updated, RAT check is passing now.

2017-05-16 2:37 GMT+03:00 Denis Magda :

> The receipt of the software grant (the persistent store) was acknowledged
> by Craig Russel.
>
> Now, we need to move on with this
>
> > In the meanwhile, I’ve prepared the IP Clearance page referring to the
> template below but failed to commit the changes to ASF repo:
> > http://incubator.apache.org/ip-clearance/ip-clearance-template.html
> >
> > *Roman S.*, *Cos*, could you help me with this by granting karma or
> committing the form from under your account?
>
> Roman, Cos, could you help with this?
>
> *Alex G.*, please add Apache 2.0 copyrights to all source files that are
> going to be donated. Presently there is no copyright at all.
>
> Everyone interested please spend some time exploring the store's docs and
> sources shared in my previous email. If no one has any concerns I will
> proceed with the donation formalities.
>
> —
> Denis
>
> > On May 12, 2017, at 2:59 PM, Denis Magda  wrote:
> >
> > Folks,
> >
> > The repository with the donation is ready and available for review:
> > https://github.com/agoncharuk/ignite/tree/pds-donate
> >
> > Big and main part of the sources is aggregated in “modules/pds”. The
> rest, that connects Apache Ignite memory architecture and SQL engine is
> under “core” and “indexing” modules. Alex Goncharuk should be able to point
> to specific files or commits if required.
> >
> > Here is a description:
> > * Persistent Store Overview: https://cwiki.apache.org/
> confluence/display/IGNITE/Persistent+Store+Overview
> > * Persistent Store Internal Design: https://cwiki.apache.org/
> confluence/display/IGNITE/Persistent+Store+Internal+Design
> >
> > The SGA will be signed and sent on Monday.
> >
> > In the meanwhile, I’ve prepared the IP Clearance page referring to the
> template below but failed to commit the changes to ASF repo:
> > http://incubator.apache.org/ip-clearance/ip-clearance-template.html
> >
> > *Roman S.*, *Cos*, could you help me with this by granting karma or
> committing the form from under your account?
> >
> > —
> > Denis
> >
> >> On Apr 25, 2017, at 9:56 AM, Konstantin Boudnik 
> wrote:
> >>
> >> While no one is suggesting an IP trap laid out in the non-SGA'ed code
> >> in this particular case, we don't want to setup a precedent like this.
> >>
> >> From the overall ASF perspective I +1 what Roman has just said.
> >>
> >> Thanks,
> >> --
> >> Take care,
> >> Konstantin (Cos) Boudnik
> >>
> >>
> >> On Wed, Apr 19, 2017 at 11:41 PM, Roman Shaposhnik <
> ro...@shaposhnik.org> wrote:
> >>> On Wed, Apr 19, 2017 at 6:21 PM, Dmitriy Setrakyan
> >>>  wrote:
>  On Wed, Apr 19, 2017 at 6:00 PM, Konstantin Boudnik 
> wrote:
> 
> > On Tue, Apr 18, 2017 at 11:54PM, Dmitriy Setrakyan wrote:
> >>
> >> Would a standard SGA suffice here?
> >>
> >> I believe that ASF guidelines suggest that a discussion should
> happen
> >> first. Once the community gets enough information, we will move to
> a PMC
> >> vote. I was under the impression that once the PMC vote passes,
> then the
> >> SGA should be provided. Or does GridGain need to provide a signed
> SGA
> > right
> >> away?
> >
> > That reminds me of that Pelosi's self-inflicted conundrum of "In
> order
> > to see the bill, we should pass the bill" ;)
> >
> 
>  Haha :)
> 
>  SGA != code. In my view, the code should be provided to the community
> for a
>  review. But I am struggling to see why should an SGA be signed prior
> to the
>  community accepting the donation.
> >>>
> >>> There's no such thing as SGA without a reference to a code base.
> >>>
> >>> Also, as I explained -- as a community member I would refuse to look
> >>> at the code base that doesn't have a proper licensing attached to it.
> >>> SGA established this kind of proper licensing.
> >>>
> >>> Now, SGA is deinetly not the only way to do so, but it is the easiest
> >>> and since you'd have to do it anyway the most convenient for the
> >>> community.
> >>>
> >>> Thanks,
> >>> Roman.
> >
>
>

Re: IGNITE-1084 is ready for review

[Semyon Boikov]

Hi Vadim,

I see that testNaturalIdCache still fails for
HibernateL2CacheTransactionalSelfTest, need investigate and find root cause
of failure.

Thanks

On Wed, May 10, 2017 at 5:03 PM, Вадим Опольский 
wrote:

> Hello guys!
>
> Semen, Sergey is issue https://issues.apache.org/jira/browse/IGNITE-1084 
> resolved
> ?
>
> Vadim Opolski
>
> 2017-04-19 14:06 GMT+03:00 Semyon Boikov :
>
>> Vadim,
>>
>> I found that real cause of IGNITE-1084 is IGNITE-4760, so suggested test
>> fix in pull/1828 is not correct. I added new comments in IGNITE-4760,
>> please take a look.
>>
>> Thanks,
>> Semyon
>>
>> On Wed, Apr 19, 2017 at 12:17 PM, Вадим Опольский 
>> wrote:
>>
>>> Hello guys!
>>>
>>> The issue IGNITE-1084 https://issues.apache.org/jira/browse/IGNITE-1794 
>>> fixed
>>> originally by Milap Wadhwa.
>>>
>>> I reassigned it on myself because she didn't make improvements from
>>> Anton Vinogradov's comments. Also I just finished another issue with
>>> hibernate's test.
>>>
>>> Review it please - https://github.com/apache/ignite/pull/1828
>>>
>>> Vadim Opolski
>>>
>>
>>
>

[GitHub] ignite pull request #1957: Ignite 4831

[rfqu]

GitHub user rfqu opened a pull request:

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

Ignite 4831



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

$ git pull https://github.com/rfqu/ignite ignite-4831

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

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


commit 8123b84a9b7d5322455dc67187b2d2f6673f61ab
Author: rfqu 
Date:   2017-05-15T16:19:32Z

IGNITE-4831 fixed (Add an option to disable MBeans). Option 
IGNITE_DISABLE_MBEANS added.

commit 710b5af2e589881430e31ebcafe43a201d204323
Author: rfqu 
Date:   2017-05-16T13:34:38Z

Mistakenly changed GridMBeanSelfTest.java restored.
Test against IGNITE_DISABLE_MBEANS added with its own name.




---
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 #1943: Ignite-4938, teamcity run on 2.0 run configs

[dspavlov]

Github user dspavlov closed the pull request at:

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


---
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 #1956: Ignite 4938 & IGNITE-4947: Fix AI 2.0 TC suites

[dspavlov]

GitHub user dspavlov opened a pull request:

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

Ignite 4938 & IGNITE-4947: Fix AI 2.0 TC suites

Ignite 4938 & IGNITE-4947: Fix AI 2.0 TC suites

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

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

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

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


commit faa8681ab35e2332a7b16210492468495eb9518e
Author: Alexander Paschenko 
Date:   2017-04-10T16:47:17Z

IGNITE-4938 De-pub of OptimizedMarshaller - take 1

commit a3686db055a55c87484ebad04e37f13ad06f93ce
Author: Alexander Paschenko 
Date:   2017-04-11T11:43:48Z

Merge branch 'master' into ignite-4938

commit 7942d585fde3fd11964f479b0442caa2ba0459d1
Author: Alexander Paschenko 
Date:   2017-04-11T16:10:37Z

IGNITE-4938 De-pub of OptimizedMarshaller - take 2

commit 1115ca5f81dc1a729cc16bcffd6ad5697b82e319
Author: Alexander Paschenko 
Date:   2017-04-12T00:44:42Z

IGNITE-4938 OptimizedMarshaller de-pub take 3 - removed redundant test 
suites

commit c89cc392f6e9f3008707a532422e10ba12fe44f1
Author: Alexey Goncharuk 
Date:   2017-04-14T15:00:51Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-4938

Conflicts:
examples/config/filesystem/example-igfs.xml
modules/clients/src/test/config/jdbc-config.xml
modules/core/src/main/java/org/apache/ignite/IgniteSystemProperties.java
modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java

modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryClassDescriptor.java

modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryContext.java

modules/core/src/main/java/org/apache/ignite/internal/client/marshaller/optimized/GridClientOptimizedMarshaller.java

modules/core/src/main/java/org/apache/ignite/internal/client/marshaller/optimized/GridClientZipOptimizedMarshaller.java

modules/core/src/main/java/org/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor.java

modules/core/src/main/java/org/apache/ignite/internal/marshaller/optimized/OptimizedMarshaller.java

modules/core/src/main/java/org/apache/ignite/internal/marshaller/optimized/package-info.java
modules/core/src/main/java/org/apache/ignite/marshaller/Marshaller.java

modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java

modules/core/src/main/java/org/apache/ignite/marshaller/optimized/package-info.java
modules/core/src/main/resources/META-INF/classnames.properties
modules/core/src/test/config/example-cache.xml
modules/core/src/test/config/igfs-loopback.xml
modules/core/src/test/config/igfs-shmem.xml
modules/core/src/test/config/spring-start-nodes-attr.xml
modules/core/src/test/config/spring-start-nodes.xml
modules/core/src/test/config/websession/example-cache-base.xml

modules/core/src/test/java/org/apache/ignite/IgniteExternalizableAbstractTest.java

modules/core/src/test/java/org/apache/ignite/cache/store/jdbc/CacheJdbcPojoStoreOptimizedMarshallerSelfTest.java
modules/core/src/test/java/org/apache/ignite/igfs/IgfsPathSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/GridLifecycleAwareSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/managers/GridManagerStopSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/marshaller/optimized/package-info.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/CacheStartupInDeploymentModesTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/GridCacheEntryMemorySizeSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/GridCacheStoreManagerDeserializationTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/GridCacheVersionSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/CacheAffinityEarlyTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/CacheGetFutureHangsSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/IgniteCacheCreatePutMultiNodeSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/IgniteCacheCreatePutTest.java

[GitHub] ignite pull request #1955: IGNITE-5100 don`t remove active exchange events f...

[zstan]

GitHub user zstan opened a pull request:

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

IGNITE-5100 don`t remove active exchange events from exchange list



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

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

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

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


commit f8157297707b30d6230e666752db3419b0a34b9f
Author: Evgeny Stanilovskiy 
Date:   2017-05-16T13:04:18Z

IGNITE-5100 don`t remove active exchange events from exchange list




---
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 #1954: ignite-gg-12199 added new variable CLEAN_WORK_DIR...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

ignite-gg-12199 added new variable CLEAN_WORK_DIR in config files



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

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

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

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


commit 6c8c3cc5ad8e2c3e5c85a0ba4447978d185f2ec3
Author: oleg-ostanin 
Date:   2017-05-16T12:36:17Z

ignite-gg-12199 added new variable CLEAN_WORK_DIR in config files




---
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 #1953: IGNITE-5208: Fixed sigfault on concurrent map acc...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-5208: Fixed sigfault on concurrent map access.



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

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

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

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


commit 1cdd7926c92a552ef434326aa6bd0f785949e363
Author: Igor Sapego 
Date:   2017-05-16T11:55:43Z

IGNITE-5208: Fixed sigfault on concurrent map access




---
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: IGNITE-4447 ready for review

[Semyon Boikov]

Hi Vadim,

Did you check test pass on TeamCity in this suite, could you please provide
link for related TeamCity run?

Thanks

On Tue, May 16, 2017 at 1:35 PM, Вадим Опольский 
wrote:

> Hi guys!
>
> IgniteCache150ClientsTest.java was removed from
> IgniteClientTestSuite.java to IgniteCacheTestSuite.java. Single test suite
> was deleted.
>
> Review please this fix - https://github.com/apache/ignite/pull/1952
>
> Vadim Opolskii
>
>
>
> 2017-05-15 11:38 GMT+03:00 Вадим Опольский :
>
> > Hi guys!
> >
> > Vladimir, is issue https://issues.apache.org/jira/browse/IGNITE-4447
> > actual now?
> >
> > Which tests do u mean? Detail please.
> >
> > Vadim
> >
>

[GitHub] ignite pull request #1948: IGNITE-2190:

[nizhikov]

Github user nizhikov closed the pull request at:

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


---
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.
---

IGNITE-5227: StackOverflowError in GridCacheMapEntry#checkOwnerChanged()

[Mikhail Cherkasov]

Hi all,

I'll take IGNITE-5227 as a first ticket if you don't mind.


-- 
Thanks,
Mikhail.

Re: contributor permissions

[Mikhail Cherkasov]

Thank you!

On Tue, May 16, 2017 at 1:59 PM, Pavel Tupitsyn 
wrote:

> Hi Mikhail,
>
> I've added you to the Jira project, welcome to the Ignite community!
>
> On Tue, May 16, 2017 at 1:56 PM, Mikhail Cherkasov <
> mcherka...@gridgain.com>
> wrote:
>
> > Hi all,
> >
> > Could you please provide me a contributor permissions?
> > My jira account: mcherkasov
> >
> > --
> > Thanks,
> > Mikhail.
> >
>



-- 
Thanks,
Mikhail.

Re: contributor permissions

[Pavel Tupitsyn]

Hi Mikhail,

I've added you to the Jira project, welcome to the Ignite community!

On Tue, May 16, 2017 at 1:56 PM, Mikhail Cherkasov 
wrote:

> Hi all,
>
> Could you please provide me a contributor permissions?
> My jira account: mcherkasov
>
> --
> Thanks,
> Mikhail.
>

contributor permissions

[Mikhail Cherkasov]

Hi all,

Could you please provide me a contributor permissions?
My jira account: mcherkasov

-- 
Thanks,
Mikhail.

Re: Data compression in Ignite 2.0

[Vyacheslav Daradur]

Hi guys,

I've prepared the PR to show my idea.
https://github.com/apache/ignite/pull/1951/files

About querying - I've just copied existing tests and have annotated the
testing data.
https://github.com/apache/ignite/pull/1951/files#diff-c19a9df4058141d059bb577e75244764

It means fields which will be marked by @BinaryCompression will be
compressed at marshalling via BinaryMarshaller.

This solution has no effect on existing data or project architecture.

I'll be glad to see your thougths.


2017-05-15 19:18 GMT+03:00 Vyacheslav Daradur :

> Dmitriy,
>
> I have ready prototype. I want to show it.
> It is always easier to discuss on example.
>
> 2017-05-15 19:02 GMT+03:00 Dmitriy Setrakyan :
>
>> Vyacheslav,
>>
>> I think it is a bit premature to provide a PR without getting a community
>> consensus on the dev list. Please allow some time for the community to
>> respond.
>>
>> D.
>>
>> On Mon, May 15, 2017 at 6:36 AM, Vyacheslav Daradur 
>> wrote:
>>
>> > I created the ticket: https://issues.apache.org/jira/browse/IGNITE-5226
>> >
>> > I'll prepare a PR with described solution in couple of days.
>> >
>> > 2017-05-15 15:05 GMT+03:00 Vyacheslav Daradur :
>> >
>> > > Hi, Igniters!
>> > >
>> > > Apache 2.0 is released.
>> > >
>> > > Let's continue the discussion about a compression design.
>> > >
>> > > At the moment, I found only one solution which is compatible with
>> > querying
>> > > and indexing, this is per-objects-field compression.
>> > > Per-fields compression means that metadata (a header) of an object
>> won't
>> > > be compressed, only serialized values of an object fields (in bytes
>> array
>> > > form) will be compressed.
>> > >
>> > > This solution have some contentious issues:
>> > > - small values, like primitives and short arrays - there isn't sense
>> to
>> > > compress them;
>> > > - there is no possible to use compression with java-predefined types;
>> > >
>> > > We can provide an annotation, @IgniteCompression - for example, which
>> can
>> > > be used by users for marking fields to compress.
>> > >
>> > > Any thoughts?
>> > >
>> > > Maybe someone already have ready design?
>> > >
>> > > 2017-04-10 11:06 GMT+03:00 Vyacheslav Daradur :
>> > >
>> > >> Alexey,
>> > >>
>> > >> Yes, I've read it.
>> > >>
>> > >> Ok, let's discuss about public API design.
>> > >>
>> > >> I think we need to add some a configure entity to CacheConfiguration,
>> > >> which will contain the Compressor interface implementation and some
>> > usefull
>> > >> parameters.
>> > >> Or maybe to provide a BinaryMarshaller decorator, which will be
>> compress
>> > >> data after marshalling.
>> > >>
>> > >>
>> > >> 2017-04-10 10:40 GMT+03:00 Alexey Kuznetsov :
>> > >>
>> > >>> Vyacheslav,
>> > >>>
>> > >>> Did you read initial discussion [1] about compression?
>> > >>> As far as I remember we agreed to add only some "top-level" API in
>> > order
>> > >>> to
>> > >>> provide a way for
>> > >>> Ignite users to inject some sort of custom compression.
>> > >>>
>> > >>>
>> > >>> [1]
>> > >>> http://apache-ignite-developers.2346864.n4.nabble.com/Data-c
>> > >>> ompression-in-Ignite-2-0-td10099.html
>> > >>>
>> > >>> On Mon, Apr 10, 2017 at 2:19 PM, daradurvs 
>> > wrote:
>> > >>>
>> > >>> > Hi Igniters!
>> > >>> >
>> > >>> > I am interested in this task.
>> > >>> > Provide some kind of pluggable compression SPI support
>> > >>> > 
>> > >>> >
>> > >>> > I developed a solution on BinaryMarshaller-level, but reviewer has
>> > >>> rejected
>> > >>> > it.
>> > >>> >
>> > >>> > Let's continue discussion of task goals and solution design.
>> > >>> > As I understood that, the main goal of this task is to store data
>> in
>> > >>> > compressed form.
>> > >>> > This is what I need from Ignite as its user. Compression provides
>> > >>> economy
>> > >>> > on
>> > >>> > servers.
>> > >>> > We can store more data on same servers at the cost of increasing
>> CPU
>> > >>> > utilization.
>> > >>> >
>> > >>> > I'm researching a possibility of implementation of compression at
>> the
>> > >>> > cache-level.
>> > >>> >
>> > >>> > Any thoughts?
>> > >>> >
>> > >>> > --
>> > >>> > Best regards,
>> > >>> > Vyacheslav
>> > >>> >
>> > >>> >
>> > >>> >
>> > >>> >
>> > >>> > --
>> > >>> > View this message in context: http://apache-ignite-
>> > >>> > developers.2346864.n4.nabble.com/Data-compression-in-
>> > >>> > Ignite-2-0-tp10099p16317.html
>> > >>> > Sent from the Apache Ignite Developers mailing list archive at
>> > >>> Nabble.com.
>> > >>> >
>> > >>>
>> > >>>
>> > >>>
>> > >>> --
>> > >>> Alexey Kuznetsov
>> > >>>
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Best Regards, Vyacheslav
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > > Best Regards, Vyacheslav
>> > >
>> >
>> >
>> >
>> > --
>> > Best Regards, Vyacheslav
>> >
>>
>
>
>
> --
> Best Regards, Vyacheslav

[jira] [Created] (IGNITE-5232) GridDhtPartitionDemander.requestPartitions invokes sendMessages consequently, which lead to significant increase of node start time on large clusters with ssl

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-5232:
-

 Summary: GridDhtPartitionDemander.requestPartitions invokes 
sendMessages consequently, which lead to significant increase of node start 
time on large clusters with ssl
 Key: IGNITE-5232
 URL: https://issues.apache.org/jira/browse/IGNITE-5232
 Project: Ignite
  Issue Type: Bug
Reporter: Evgenii Zhuravlev
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1952: IGNITE-4447

[vadopolski]

GitHub user vadopolski opened a pull request:

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

IGNITE-4447

Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java.

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

$ git pull https://github.com/vadopolski/ignite ignite-4447

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

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


commit 6e5f83233b5501bdb6a3bb03eb53f3be8871f786
Author: vopolski <2w3e4r5t>
Date:   2017-04-20T15:07:48Z

updating

commit f9d64f1e58b794caee47e584aa32ec18246fe434
Author: vopolski <2w3e4r5t>
Date:   2017-05-16T10:05:49Z

IGNITE-4447
Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java.

commit 185d5f9e685f6b0ec7ccf7bafa027dd46bfc156a
Author: vopolski <2w3e4r5t>
Date:   2017-05-16T10:28:54Z

IGNITE-4447
Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java.




---
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 #1951: IGNITE-5226

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-5226



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

$ git pull https://github.com/daradurvs/ignite ignite-5226

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

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


commit 9df73f0808f9e45afc56622c0412472e3269763f
Author: Vyacheslav Daradur 
Date:   2017-05-15T16:15:21Z

ignite-5226: prototype

commit 868d3a89413b11593f1c4689b6a516f69c2c2d4a
Author: Vyacheslav Daradur 
Date:   2017-05-16T10:24:39Z

ignite-5226: minor refactoring




---
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 #1950: IGNITE-4447

[vadopolski]

Github user vadopolski closed the pull request at:

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


---
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-5231) Web Console: Add support for Ignite 2.0 cluster on Queries screen

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-5231:
--

 Summary: Web Console: Add support for Ignite 2.0 cluster on 
Queries screen
 Key: IGNITE-5231
 URL: https://issues.apache.org/jira/browse/IGNITE-5231
 Project: Ignite
  Issue Type: Bug
  Components: UI, wizards
Affects Versions: 2.0
Reporter: Andrey Novikov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Minimize amount of inner classes, predicates, tuples, etc

[Vyacheslav Daradur]

Vladimir, thank you for this suggestion.
As newcomer in the Ignite I agree with you, sometimes it is very hard to
understand huge classes which contain sets of inner classes.

>> 1) Inner classes (both static and non-static)
Completelly agree, especially classes which will be serialized.

>> 2) Usage of generic tuples
Why or in what cases?

>> Tuples and closures should be replaced with concrete classes, specific
to your case.
Can you give an example?

2017-05-16 13:01 GMT+03:00 Vladimir Ozerov :

> Igniters,
>
> Ignite is known to be complex product. Partially this complexity comes from
> ... complex problems we are trying to resolve. But partially it comes from
> how we write our code. I noticed several anti-patterns which makes our code
> hard to manage:
>
> 1) Inner classes (both static and non-static)
> 2) Usage of generic tuples
> 3) Usage of many classes from our "lang"package - closures, predicates,
> etc..
>
> When combined these anti-patterns makes our classes huge, leaky in terms of
> abstractions, hard to follow and refactor. I would like to propose to
> restrict usages of these constructs as much as possible in non-test code.
> Classes should be top-level by default, unless "inner" semantics are
> absolutely necessary or saves a lot of code. Tuples and closures should be
> replaced with concrete classes, specific to your case.
>
> Thoughts?
>
> Vladimir.
>



-- 
Best Regards, Vyacheslav

[GitHub] ignite pull request #1950: IGNITE-4447

[vadopolski]

GitHub user vadopolski opened a pull request:

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

IGNITE-4447

Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java.

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

$ git pull https://github.com/vadopolski/ignite ignite-4447

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

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


commit 6e5f83233b5501bdb6a3bb03eb53f3be8871f786
Author: vopolski <2w3e4r5t>
Date:   2017-04-20T15:07:48Z

updating

commit f9d64f1e58b794caee47e584aa32ec18246fe434
Author: vopolski <2w3e4r5t>
Date:   2017-05-16T10:05:49Z

IGNITE-4447
Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java.




---
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.
---

Minimize amount of inner classes, predicates, tuples, etc

[Vladimir Ozerov]

Igniters,

Ignite is known to be complex product. Partially this complexity comes from
... complex problems we are trying to resolve. But partially it comes from
how we write our code. I noticed several anti-patterns which makes our code
hard to manage:

1) Inner classes (both static and non-static)
2) Usage of generic tuples
3) Usage of many classes from our "lang"package - closures, predicates,
etc..

When combined these anti-patterns makes our classes huge, leaky in terms of
abstractions, hard to follow and refactor. I would like to propose to
restrict usages of these constructs as much as possible in non-test code.
Classes should be top-level by default, unless "inner" semantics are
absolutely necessary or saves a lot of code. Tuples and closures should be
replaced with concrete classes, specific to your case.

Thoughts?

Vladimir.

[GitHub] ignite pull request #1942: IGNITE-5225: Fixed bug in TcpCommunicationSpi.

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
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 #1949: Ignite 1.8.7.b1

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite 1.8.7.b1



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

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

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

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


commit e01aee0b1bbdb8ff5583728e539df165029f682d
Author: nikolay_tikhonov 
Date:   2017-03-31T17:19:52Z

Fixed SSL issue.

Signed-off-by: nikolay_tikhonov 

commit ead9f2a595b91821b1b16627dd8d752897c24c03
Author: dkarachentsev 
Date:   2017-04-03T11:46:54Z

Merge branch 'ignite-1.8.4-p1' into ignite-1.8.6

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

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

Fixed typo.
(cherry picked from commit 3b84f34)

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

master Updated version.
(cherry picked from commit 5469626)

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

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

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

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

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

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

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

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

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

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

(cherry picked from commit b7ab273)

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

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

(cherry picked from commit 443ac9a)

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

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

(backport from 1.9.2)

(cherry picked from commit 220db882b466c03eadd148b3a19a0bf70d82d4a6)

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

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

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

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

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

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

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

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

(cherry picked from commit 0f7ef74)

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

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

(Backport from master)

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

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

Backport from master.

(cherry picked from commit 76485fc)

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

ignite-1977 - fixed IgniteSemaphore fault 

[GitHub] ignite pull request #1945: IGNITE-4831 fixed (Add an option to disable MBean...

[rfqu]

Github user rfqu closed the pull request at:

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


---
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-5230) Web Console: SVG icons integration

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-5230:


 Summary: Web Console: SVG icons integration
 Key: IGNITE-5230
 URL: https://issues.apache.org/jira/browse/IGNITE-5230
 Project: Ignite
  Issue Type: Task
  Components: wizards
Reporter: Ilya Borisov
Assignee: Ilya Borisov
Priority: Minor


We need a common way to use SVG icons that:
1. Does not require extra styles.
2. Allows for CSS styling of icons, especially icon color.
3. Easy to add new icons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Store data from Python in multiple caches using Redis or Memcached client in Apache ignite

[Valentin Kulichenko]

To my knowledge, Memcached does not allow to do this.

-Val

On Mon, May 15, 2017 at 9:27 PM, Roman Shtykh 
wrote:

> Denis, yes, I would like to enable switching caches via "CONFIG SET
> parameter value".I created https://issues.apache.org/
> jira/browse/IGNITE-5229 for this, and will discuss it in a separate
> thread.
> Roman
>
>
>
>
> On Tuesday, May 16, 2017 8:45 AM, Denis Magda 
> wrote:
>
>
>  Hi, see below
>
> > On May 15, 2017, at 7:32 AM, rishi007bansod 
> wrote:
> >
> > Examples at following link displays how data is stored in default
> > caches(single cache) only in Apache Ignite:
> >
> > https://apacheignite.readme.io/docs/redis#python
> > 
> >
> According to the docs there is no way to store data in multiple caches for
> now.
>
> *Roman*, do you have any plans to remove the limitation in the nearest
> releases?
>
> > https://apacheignite.readme.io/v1.8/docs/memcached-support
> > 
> >
>
> *Val*, is this achievable with Memcached client? I can’t find a hint how
> to do this.
>
> > I want to store data in multiple caches(with different cache names) in
> > Apache Ignite from Python either using redis client or using memcache
> > client. How can I do this? Also, are SQL queries supported when we use
> > Memcached or redis client for caching data in Ignite from Python.
> >
>
> If you want to use SQL queries from Python then I would suggest connecting
> to the cluster with ODBC driver:
> https://apacheignite.readme.io/docs/odbc-driver
>
> For instance, this is how it works from PHP and the same can be easily
> done from Python side:
> https://apacheignite-mix.readme.io/docs/php-pdo
>
> —
> Denis
>
> >
> >
> > --
> > View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Store-data-from-Python-in-
> multiple-caches-using-Redis-or-Memcached-client-in-Apache-
> ignite-tp17660.html
> > Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
>
>
>
>

Re: ignite-5097 is ready for review (BinaryMarshaller should write ints in "varint" encoding where it makes sense)

[Vyacheslav Daradur]

Denis,

It changes format of serialized data. (arrays, Collection, Map, BigDecimal,
String, Enum)

Data which will have been serialized before this improvement won't be able
to be deserialized after and vice versa.

2017-05-16 2:52 GMT+03:00 Denis Magda :

> As I see the discussion is happening in JIRA.
>
> BTW, can we do this improvement without breaking compatibility with 2.0?
>
> —
> Denis
>
> > On May 15, 2017, at 5:08 AM, Vyacheslav Daradur 
> wrote:
> >
> > Any thoughts about implemented solution?
> >
> > 2017-05-04 13:26 GMT+03:00 Vyacheslav Daradur :
> >
> >> Hi Igniteres!
> >>
> >> Java part is ready for review.
> >>
> >> BinaryMarshaller should write ints in "varint" encoding where it makes
> >> sense 
> >> ci.tests 
> >> PR 
> >>
> >>
> >> --
> >> Best Regards, Vyacheslav
> >>
> >
> >
> >
> > --
> > Best Regards, Vyacheslav
>
>


-- 
Best Regards, Vyacheslav