date:20151225

Pavel Konstantinov created IGNITE-2291:
--

 Summary: Sql query dialog has incorrect position
 Key: IGNITE-2291
 URL: https://issues.apache.org/jira/browse/IGNITE-2291
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Dmitriyff
Priority: Trivial


I think it should appear at the center of the screen



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

[jira] [Created] (IGNITE-2290) Section title has no 'hand' mouse point

Pavel Konstantinov created IGNITE-2290:
--

 Summary: Section title has no 'hand' mouse point 
 Key: IGNITE-2290
 URL: https://issues.apache.org/jira/browse/IGNITE-2290
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Dmitriyff
Priority: Trivial






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

[jira] [Created] (IGNITE-2289) Eviction policy doesn't work with OFFHEAP_VALUES mode

2015-12-25 Thread Valentin Kulichenko (JIRA)

Valentin Kulichenko created IGNITE-2289:
---

 Summary: Eviction policy doesn't work with OFFHEAP_VALUES mode
 Key: IGNITE-2289
 URL: https://issues.apache.org/jira/browse/IGNITE-2289
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko
 Fix For: 1.6


For issue description and the test refer to this discussion: 
http://apache-ignite-users.70518.x6.nabble.com/Eviction-for-OFFHEAP-TIERED-vs-OFFHEAP-VALUES-td2302.html



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

Re: about apache ignite's document localization(Simplified Chinese)

2015-12-25 Thread Dmitriy Setrakyan

I don’t believe that the Semaphore made it in. As far as MQTT and Twitter
streamers, I think we are missing the documentation.

Whoever contributed or reviewed these features, can you please comment?

D.

On Fri, Dec 25, 2015 at 4:26 AM, 李玉珏@163 <18624049...@163.com> wrote:

> Hi：
>
> In addition, I saw release note,
> https://github.com/apache/ignite/blob/ignite-1.5/RELEASE_NOTES.txt:
>
> * Added IgniteSemaphore data structure.
> * Added MQTT Streamer.
> * Added Twitter Streamer.
>
> I did not see the relevant documents on the three items mentioned above.
> Is there no such document or I can't find it?
>
> 在 15/12/25 00:33, Dmitriy Setrakyan 写道:
>
>> Thanks, Yujue Li!
>>
>>
>> Thanks for pointing out the 1.5 OSGI issue. It turns out that we had it
>> documented, but didn’t make it public. I just pushed it live and you
>> should
>> see the OSGI docs.
>>
>> I still think we should document the deadlock-free transaction feature,
>> which was released in 1.5. Other than that, I do not anticipate any
>> changes
>> to 1.5 documentation.
>>
>> D.
>>
>> On Thu, Dec 24, 2015 at 4:08 AM, 李玉珏@163 <18624049...@163.com> wrote:
>>
>> Hi Igniters:
>>>
>>> As of today, after 2 months of hard work, the translation of the 1.4
>>> version of Ignite has been completed.
>>> I would like to know a question, the 1.5 version is about to release,
>>> whether the document has been frozen? I see that the OSGi support section
>>> is still empty.
>>>
>>> 在 15/12/5 04:01, Dmitriy Setrakyan 写道:
>>>
>>> Thanks, Yujue Li, for your contribution! We really appreciate the work
 you

 are doing. I have added the link to the Chinese documentation to our
 website.

 I have also noticed that the documentation is for 1.4 version. Would it
 be
 possible to upgrade it to 1.5? All the documentation changes are
 recorded
 in GitHub:

 https://github.com/apacheignite/documentation/tree/v1.4
 https://github.com/apacheignite/documentation/tree/v1.5

 D.

 On Thu, Dec 3, 2015 at 5:10 AM, 李玉珏@163 <18624049...@163.com> wrote:

 Hi：

> As of today, the InteractiveSQL and Streaming parts have been
> translated
> to complete, the relevant page has been updated to zybuluo.com, the
> address is: https://www.zybuluo.com/liyuj/note/230739.
>
> In addition, I have the Markdown of the source file to the GitHub, the
> address is: https://github.com/liyuj/ignite-doc-cn.git.Because zybuluo
> is
> a real-time backup of cloud services, so the source file on the GitHub
> only
> played a role in the backup.
>
> 在 15/12/1 01:38, Dmitriy Setrakyan 写道:
>
> Thanks Yujue Li! I will add the link to this documentation on our
> website.
>
> Please keep us posted on your progress.
>>
>> On Mon, Nov 30, 2015 at 4:17 AM, 李玉珏@163 <18624049...@163.com> wrote:
>>
>> Hi：
>>
>> As of today, the data grid has been translated and completed.
>>>
>>> I tried to put the HTML on the GIT repository, but the effect was not
>>> good. As a temporary solution, I'm going to put the HTM on the
>>> www.zybuluo.com site, and I also use the site to provide the tools
>>> for
>>> translation.
>>>
>>> By my English level, the depth of understanding of the Ignite, the
>>> quality
>>> of the original text, the translation will inevitably have a
>>> mistake, I
>>> also welcome the Chinese and Ignite proficient people can make
>>> recommendations, but on the whole, I have confidence in the quality
>>> of
>>> translation. I have already generated a directory page, the first
>>> three
>>> parts, the address is: https://www.zybuluo.com/liyuj/note/230739. If
>>> it
>>> feels like, I hope to provide a link on the website, as an unofficial
>>> translation of the official manual recommended to the developer, if
>>> you
>>> think the time is not appropriate, and so on and so on all the work
>>> is
>>> completed and then recommended.
>>>
>>> About markdown source file hosting warehouse, because a lot of people
>>> have
>>> GitHub account, then I will migrate to GitHub, and then open.
>>>
>>> 在 15/11/18 06:51, Dmitriy Setrakyan 写道:
>>>
>>> Thanks Yujue Li! We really appreciate the work you are doing.
>>>
>>> As far as permissions go, is it possible to add users to the project,
>>>
 much
 in the same way as in GitHub? Another way to suggest documentation
 fixes
 could be to file issues in the oschina git (looks like it supports
 issues
 in the same way as GitHub).

 D.

 On Tue, Nov 17, 2015 at 4:47 AM, 李玉珏@163 <18624049...@163.com>
 wrote:

 Hi：

 I had hoped that I would finish the translation work, because the

> workload
> is not particularly great.
>
>

[GitHub] ignite pull request: IGNITE-2285 .Net: Add ICache.GetDataStreamer

GitHub user ptupitsyn opened a pull request:

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

IGNITE-2285 .Net: Add ICache.GetDataStreamer



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

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

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

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


commit 54fc8818bab7078e4a3bbe3764b2b064f4092061
Author: Pavel Tupitsyn 
Date:   2015-12-25T15:11:37Z

IGNITE-2285 .Net: Add ICache.GetDataStreamer




---
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-2288) F.first(Collection) should use index-based lookup for Lists.

Vladimir Ozerov created IGNITE-2288:
---

 Summary: F.first(Collection) should use index-based lookup for 
Lists.
 Key: IGNITE-2288
 URL: https://issues.apache.org/jira/browse/IGNITE-2288
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.6


There are lots of places in code where F.first(Collection) is used. Quite often 
passed collection is a List. 
Instead of gettting iterator, we should do "get(0)" in these cases. This will 
allow us to prevent iterator creation.



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

[jira] [Created] (IGNITE-2287) Generate some POJO store example if downloaded project contains caches with store + metadata

Alexey Kuznetsov created IGNITE-2287:


 Summary: Generate some POJO store example if downloaded project 
contains caches with store + metadata
 Key: IGNITE-2287
 URL: https://issues.apache.org/jira/browse/IGNITE-2287
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


It will be useful to have example that will demonstrate how to load data from 
DB into cache via POJO store



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

Caches statistics on/off on the fly

2015-12-25 Thread Alexey Kuznetsov

Igniters,

We have an old issue [1] with no progress for a long time.

This issue on Alexey Goncharuk, for a long time...
Alex, does it make sense to give a chance to other developers to fix this
one?

Thoughts?


*[1] Cache manager should switch cache statisticsEnabled property globaly*
*https://issues.apache.org/jira/browse/IGNITE-369
*

-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-2286) Improve Metadata load from cache

Alexey Kuznetsov created IGNITE-2286:


 Summary: Improve Metadata load from cache
 Key: IGNITE-2286
 URL: https://issues.apache.org/jira/browse/IGNITE-2286
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
 Fix For: 1.6


# Add option "Generate primitives in POJO for not null columns"+ tooltip with 
description
# Add option "Use Java builtin types as Key class" + tooltip with description 
when KeyClass generated and when it will be better to use java builtin types




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

[jira] [Created] (IGNITE-2285) .Net: Add ICache.GetDataStreamer

2015-12-25 Thread Pavel Tupitsyn (JIRA)

Pavel Tupitsyn created IGNITE-2285:
--

 Summary: .Net: Add ICache.GetDataStreamer
 Key: IGNITE-2285
 URL: https://issues.apache.org/jira/browse/IGNITE-2285
 Project: Ignite
  Issue Type: Improvement
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


Currently we have IIgnite.GetDataStreamer, where user has to specify cache name 
and generic arguments.

ICache.GetDataStreamer will infer both cache name and generic types for the 
user.



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

Re: [VOTE] Apache Ignite 1.5.0.final

2015-12-25 Thread Alexey Kuznetsov

+1 (NOT binding)

On Fri, Dec 25, 2015 at 9:12 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> +1 (binding)
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-2284) Improve Metadata and Caches screen integration

Alexey Kuznetsov created IGNITE-2284:


 Summary: Improve Metadata and Caches screen integration
 Key: IGNITE-2284
 URL: https://issues.apache.org/jira/browse/IGNITE-2284
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Priority: Minor


# Add "name" to "Data source bean" labels
# Auto generate name for POJO Store datasource bean name (cacheName + Ds).
# Auto select H2 dialect
# If on metadata page cache is selected and this cache has no store configured 
we need to show dialog with cache POJO store configuration on user click "Save" 
button




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

Re: [VOTE] Apache Ignite 1.5.0.final

2015-12-25 Thread Alexey Goncharuk

+1 (binding)

[jira] [Created] (IGNITE-2283) Improve download on Summary page

Alexey Kuznetsov created IGNITE-2283:


 Summary: Improve download on Summary page
 Key: IGNITE-2283
 URL: https://issues.apache.org/jira/browse/IGNITE-2283
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Priority: Minor


# Add "project" to download button and "Project structure" link that will show 
popup with project structure description
# Change "On this page" to be more accurate with description about page
# rename "factory" package to "config"
# Add more info into README.txt in jdbc-drivers folder
# Describe project structure in root README.txt
# Generated pom.xml should be configured as code java 7, source java 7
# Add in more info links to documentation




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

[GitHub] ignite pull request: IGNITE-1413 .Net: Get rid of set -> map conve...

GitHub user ptupitsyn opened a pull request:

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

IGNITE-1413 .Net: Get rid of set -> map conversion in 
PlatformDotNetCacheStore.writeAll



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

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

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

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


commit 38e36bd720a2082e400947b5352c9405fad00c6d
Author: Pavel Tupitsyn 
Date:   2015-12-25T13:46:22Z

IGNITE-1413 .Net: Get rid of set -> map conversion in 
PlatformDotNetCacheStore.writeAll




---
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-2282) Check that generated Docker file is valid and could be used by users

Alexey Kuznetsov created IGNITE-2282:


 Summary: Check that generated Docker file is valid and could be 
used by users
 Key: IGNITE-2282
 URL: https://issues.apache.org/jira/browse/IGNITE-2282
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Assignee: Pavel Konstantinov






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

Re: [VOTE] Apache Ignite 1.5.0.final

2015-12-25 Thread Anton Vinogradov

+1 (binding)

On Fri, Dec 25, 2015 at 4:19 PM, Nikolay Tikhonov 
wrote:

> +1 (binding)
>
> On Fri, Dec 25, 2015 at 4:00 PM, Anton Vinogradov  wrote:
>
> > Dear Sirs!
> >
> > We have uploaded release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc1/
> >
> > This is very important release containing initial versions of Ignite.NET
> > and Ignite C++ and many other important features.
> >
> > Tag name is
> > 1.5.0.final-rc1
> >
> > 1.5.0 changes:
> > * Ignite.NET: Initial Release.
> > * Ignite C++: Initial Release.
> > * Massive performance improvements for cache operations and SQL.
> > * Added new binary cache object marshalling implementation.
> > * Added IgniteSemaphore data structure.
> > * Added MQTT Streamer.
> > * Added Twitter Streamer.
> > * Added Ignite Sink (integration with Apache Flume).
> > * Fixed optimistic serializable transactions: implemented "deadlock-free"
> > locking algorithm.
> > * Fixed failover for continuous queries.
> > * Fixed compilation and runtime errors under OpenJDK and IBM JDK.
> > * Fixed Integer.size limitation for cache.
> > * Fixed and improved cache types configuration.
> > * Fixed cache rebalancing.
> > * Many stability and fault-tolerance fixes.
> > * Added example to demonstrate the usage of EntryProcessor.
> >
> > Complete list of closed issues:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.5%20AND%20status%20%3D%20closed
> >
> > DEVNOTES
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.5.0.final-rc1
> >
> > RELEASENOTES
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.5.0.final-rc1
> >
> > Please start voting.
> >
> > +1 - to accept Apache Ignite 1.5.0.final
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite 1.5.0.final (explain why)
> >
> > This vote will go for 72 hours.
> >
>

Re: [VOTE] Apache Ignite 1.5.0.final

2015-12-25 Thread Nikolay Tikhonov

+1 (binding)

On Fri, Dec 25, 2015 at 4:00 PM, Anton Vinogradov  wrote:

> Dear Sirs!
>
> We have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc1/
>
> This is very important release containing initial versions of Ignite.NET
> and Ignite C++ and many other important features.
>
> Tag name is
> 1.5.0.final-rc1
>
> 1.5.0 changes:
> * Ignite.NET: Initial Release.
> * Ignite C++: Initial Release.
> * Massive performance improvements for cache operations and SQL.
> * Added new binary cache object marshalling implementation.
> * Added IgniteSemaphore data structure.
> * Added MQTT Streamer.
> * Added Twitter Streamer.
> * Added Ignite Sink (integration with Apache Flume).
> * Fixed optimistic serializable transactions: implemented "deadlock-free"
> locking algorithm.
> * Fixed failover for continuous queries.
> * Fixed compilation and runtime errors under OpenJDK and IBM JDK.
> * Fixed Integer.size limitation for cache.
> * Fixed and improved cache types configuration.
> * Fixed cache rebalancing.
> * Many stability and fault-tolerance fixes.
> * Added example to demonstrate the usage of EntryProcessor.
>
> Complete list of closed issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.5%20AND%20status%20%3D%20closed
>
> DEVNOTES
>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.5.0.final-rc1
>
> RELEASENOTES
>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.5.0.final-rc1
>
> Please start voting.
>
> +1 - to accept Apache Ignite 1.5.0.final
> 0 - don't care either way
> -1 - DO NOT accept Apache Ignite 1.5.0.final (explain why)
>
> This vote will go for 72 hours.
>

[GitHub] ignite pull request: IGNITE-2166 .NET: Add toBuilder() method on B...

GitHub user ptupitsyn opened a pull request:

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

IGNITE-2166 .NET: Add toBuilder() method on BinaryObject interface.



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

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

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

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


commit a95fd8feeff825059f037102d233e03019f381b4
Author: Pavel Tupitsyn 
Date:   2015-12-25T13:05:01Z

IGNITE-2166 .NET: Add toBuilder() method on BinaryObject interface.

commit 7f6d34eb343f3401b158b6840a3a362640834d12
Author: Pavel Tupitsyn 
Date:   2015-12-25T13:09:27Z

Tests updated




---
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: Ignite 2218b

2015-12-25 Thread iveselovskiy

GitHub user iveselovskiy opened a pull request:

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

Ignite 2218b



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

$ git pull https://github.com/iveselovskiy/ignite ignite-2218b

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

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


commit b24d4aaec86624863729ce97ad2ebf08380fe717
Author: iveselovskiy 
Date:   2015-12-25T13:01:21Z

IGNITE-2218: new implementation.

commit a4d2a1812bdfff4de1075150355098db448175eb
Author: iveselovskiy 
Date:   2015-12-25T13:02:04Z

Merge branch 'ignite-1.5' of https://github.com/apache/ignite into 
ignite-2218b




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

[VOTE] Apache Ignite 1.5.0.final

2015-12-25 Thread Anton Vinogradov

Dear Sirs!

We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc1/

This is very important release containing initial versions of Ignite.NET
and Ignite C++ and many other important features.

Tag name is
1.5.0.final-rc1

Complete list of closed issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.5%20AND%20status%20%3D%20closed

DEVNOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.5.0.final-rc1

RELEASENOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.5.0.final-rc1

Please start voting.

+1 - to accept Apache Ignite 1.5.0.final
0 - don't care either way
-1 - DO NOT accept Apache Ignite 1.5.0.final (explain why)

This vote will go for 72 hours.

Re: about apache ignite's document localization(Simplified Chinese)

2015-12-25 Thread 李玉珏


Hi：

In addition, I saw release note, 
https://github.com/apache/ignite/blob/ignite-1.5/RELEASE_NOTES.txt:


* Added IgniteSemaphore data structure.
* Added MQTT Streamer.
* Added Twitter Streamer.

I did not see the relevant documents on the three items mentioned above. 
Is there no such document or I can't find it?


在 15/12/25 00:33, Dmitriy Setrakyan 写道:

Thanks, Yujue Li!

Thanks for pointing out the 1.5 OSGI issue. It turns out that we had it
documented, but didn’t make it public. I just pushed it live and you should
see the OSGI docs.

I still think we should document the deadlock-free transaction feature,
which was released in 1.5. Other than that, I do not anticipate any changes
to 1.5 documentation.

D.

On Thu, Dec 24, 2015 at 4:08 AM, 李玉珏@163 <18624049...@163.com> wrote:


Hi Igniters:

As of today, after 2 months of hard work, the translation of the 1.4
version of Ignite has been completed.
I would like to know a question, the 1.5 version is about to release,
whether the document has been frozen? I see that the OSGi support section
is still empty.

在 15/12/5 04:01, Dmitriy Setrakyan 写道:


Thanks, Yujue Li, for your contribution! We really appreciate the work you

are doing. I have added the link to the Chinese documentation to our
website.

I have also noticed that the documentation is for 1.4 version. Would it be
possible to upgrade it to 1.5? All the documentation changes are recorded
in GitHub:

https://github.com/apacheignite/documentation/tree/v1.4
https://github.com/apacheignite/documentation/tree/v1.5

D.

On Thu, Dec 3, 2015 at 5:10 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi：

As of today, the InteractiveSQL and Streaming parts have been translated
to complete, the relevant page has been updated to zybuluo.com, the
address is: https://www.zybuluo.com/liyuj/note/230739.

In addition, I have the Markdown of the source file to the GitHub, the
address is: https://github.com/liyuj/ignite-doc-cn.git.Because zybuluo
is
a real-time backup of cloud services, so the source file on the GitHub
only
played a role in the backup.

在 15/12/1 01:38, Dmitriy Setrakyan 写道:

Thanks Yujue Li! I will add the link to this documentation on our
website.


Please keep us posted on your progress.

On Mon, Nov 30, 2015 at 4:17 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi：


As of today, the data grid has been translated and completed.

I tried to put the HTML on the GIT repository, but the effect was not
good. As a temporary solution, I'm going to put the HTM on the
www.zybuluo.com site, and I also use the site to provide the tools for
translation.

By my English level, the depth of understanding of the Ignite, the
quality
of the original text, the translation will inevitably have a mistake, I
also welcome the Chinese and Ignite proficient people can make
recommendations, but on the whole, I have confidence in the quality of
translation. I have already generated a directory page, the first three
parts, the address is: https://www.zybuluo.com/liyuj/note/230739. If
it
feels like, I hope to provide a link on the website, as an unofficial
translation of the official manual recommended to the developer, if you
think the time is not appropriate, and so on and so on all the work is
completed and then recommended.

About markdown source file hosting warehouse, because a lot of people
have
GitHub account, then I will migrate to GitHub, and then open.

在 15/11/18 06:51, Dmitriy Setrakyan 写道:

Thanks Yujue Li! We really appreciate the work you are doing.

As far as permissions go, is it possible to add users to the project,

much
in the same way as in GitHub? Another way to suggest documentation
fixes
could be to file issues in the oschina git (looks like it supports
issues
in the same way as GitHub).

D.

On Tue, Nov 17, 2015 at 4:47 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi：

I had hoped that I would finish the translation work, because the

workload
is not particularly great.

The reason to put the code on git.oschina.net, in addition to some
of
my
personal information (such as blogs) are placed on the oschina.net,
the
main reason is that I want to put the final HTML on there,
configuration
management functions are secondary. In fact, from the function of the
code
host, git.oschina.net is not as good as github.

I do not exclude everyone's cooperation, nor selfish, mainly in the
private communication with Mr. Jiang, there are differences in
working
methods.I do this is part time, so I hope to avoid too much extra
workload.

Since there are a lot of people in the community are interested in
this,
I
intend to let go of the project fork permissions, in addition to
those
who
want to participate in this project to join the developer list.

在 15/11/17 06:18, Dmitriy Setrakyan 写道:

I just got confirmation from oschina (it just took a while). My
username
is

“diset”, can you please add me to the project?


D.

On Mon, Nov 16, 2015 at 1:38 PM, Dmitriy Setrakyan <
dsetrak...@apache.org
wrote:

In general, it would be great i

[GitHub] ignite pull request: IGNITE-1419 .Net: Add optional "raw" flag to ...

GitHub user ptupitsyn opened a pull request:

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

IGNITE-1419 .Net: Add optional "raw" flag to binary type configuration.



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

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

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

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


commit edc0bd67f1003b50fde74ee3d8160909a2eb4a8c
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:35:24Z

IGNITE-1419 .Net: Add optional "raw" flag to binary type configuration.

commit 34f5662919caa2099847a1e26ac0833bad4abfad
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:41:40Z

wip Java

commit 4b87360e458607b44a5b1d9139ef9b0e05f0e570
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:45:36Z

wip

commit 1882ada2a6e34975a47e47fc5a060c4d9b32cb0d
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:46:51Z

wip

commit 28483646ab1cf0ba11f93dbf0b773d6c062de467
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:05:09Z

wip

commit c6dfc28fdae9d3a1cf3c8ec940183638ae0f8231
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:40:45Z

wip

commit 1e664132f4ccc1c240523637dc3392e1609c4aa6
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:50:01Z

wip

commit 3d75004d3969aab625c90b42a5af9a94834488e4
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:58:05Z

wip

commit 8f35db028f3c30f7d6b80744cda81e337a69e23a
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:06:08Z

wip

commit 802b5ad69230fd288734b6e5406cb29e9ad2a577
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:08:42Z

wip

commit 03f60ac14eecf9889543119fbd347d137d7d6ad2
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:09:59Z

wip

commit 375f57058665b15f2ab405cbbef5cab26662140e
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:21:00Z

wip test

commit 1c7958075ff71b75260b239902f4f00cb3ae3861
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:41:24Z

Test works

commit 876d1132517e63accbb4cc6118ae9cdc296bd85b
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:45:14Z

wip tests

commit 8f9c671291540f679b47e46146f3efcb0936963e
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:48:49Z

wip tests

commit 07e03db0134b632ee52bca23bf4a2977dd33a18c
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:49:51Z

wip tests

commit f7c1ddda8cda98a7c2ac38f742419de940d87686
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:51:51Z

wip

commit cb9ef1bbe6255907392dd6326327f728b368fd61
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:54:47Z

Fix npe in collections




---
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: IGNITE-1419 .Net: Add optional "raw" flag to ...

Github user ptupitsyn closed the pull request at:

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


---
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: IGNITE-1419 .Net: Add optional "raw" flag to ...

GitHub user ptupitsyn opened a pull request:

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

IGNITE-1419 .Net: Add optional "raw" flag to binary type configuration.



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

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

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

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


commit 49c298866b7c113aa62af4fe0587d6d39edd9f50
Author: sboikov 
Date:   2015-12-24T12:52:59Z

ignite-1.5 Fixed test.

commit 18c413c41b51994fb2eeaaebf4cf727049db0c8b
Author: vozerov-gridgain 
Date:   2015-12-25T06:48:28Z

IGNITE-2257: Fixed BinaryContext serialization.

commit edc0bd67f1003b50fde74ee3d8160909a2eb4a8c
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:35:24Z

IGNITE-1419 .Net: Add optional "raw" flag to binary type configuration.

commit 34f5662919caa2099847a1e26ac0833bad4abfad
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:41:40Z

wip Java

commit 4b87360e458607b44a5b1d9139ef9b0e05f0e570
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:45:36Z

wip

commit 1882ada2a6e34975a47e47fc5a060c4d9b32cb0d
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:46:51Z

wip

commit 28483646ab1cf0ba11f93dbf0b773d6c062de467
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:05:09Z

wip

commit c6dfc28fdae9d3a1cf3c8ec940183638ae0f8231
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:40:45Z

wip

commit 1e664132f4ccc1c240523637dc3392e1609c4aa6
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:50:01Z

wip

commit 3d75004d3969aab625c90b42a5af9a94834488e4
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:58:05Z

wip

commit 8f35db028f3c30f7d6b80744cda81e337a69e23a
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:06:08Z

wip

commit 802b5ad69230fd288734b6e5406cb29e9ad2a577
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:08:42Z

wip

commit 03f60ac14eecf9889543119fbd347d137d7d6ad2
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:09:59Z

wip

commit 375f57058665b15f2ab405cbbef5cab26662140e
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:21:00Z

wip test

commit 1c7958075ff71b75260b239902f4f00cb3ae3861
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:41:24Z

Test works

commit 876d1132517e63accbb4cc6118ae9cdc296bd85b
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:45:14Z

wip tests

commit 8f9c671291540f679b47e46146f3efcb0936963e
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:48:49Z

wip tests

commit 07e03db0134b632ee52bca23bf4a2977dd33a18c
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:49:51Z

wip tests

commit f7c1ddda8cda98a7c2ac38f742419de940d87686
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:51:51Z

wip

commit cb9ef1bbe6255907392dd6326327f728b368fd61
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:54:47Z

Fix npe in collections




---
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-1993: JDBC discovery uses non-standard SQL when creating table (not compatible with Oracle)

2015-12-25 Thread Denis Magda

Hi Nigel,

Is there any chance you apply review notes and complete the following 
contribution?
https://issues.apache.org/jira/browse/IGNITE-1993

Merry xmas & happy new year to you!
Denis

Re: Abandoned ticket: Implement IgniteStormStreamer to stream data from Apache Storm

2015-12-25 Thread Denis Magda

HI Chandresh,

Do you have any progress on the ticket or do you need any assistance?
 
Regards,
Denis

> On 14 дек. 2015 г., at 13:41, chandresh pancholi 
>  wrote:
> 
> Sure,
> Will try to finish this by end of this month.
> On Dec 14, 2015 3:59 PM, "Denis Magda"  wrote:
> 
>> Hi Chandresh,
>> 
>> Is there any chance you complete the ticket from the subj during this
>> month?
>> https://issues.apache.org/jira/browse/IGNITE-429
>> 
>> If you're too busy for know don't you mind if someone else from the
>> community pick it up and complete? We want to see the feature as a part of
>> the nearest releases.
>> 
>> --
>> Denis
>>

[jira] [Created] (IGNITE-2281) We need to save content in tables on focus lost and not force user to click "disk" icon

Alexey Kuznetsov created IGNITE-2281:


 Summary: We need to save content in tables on focus lost and not 
force user to click "disk" icon
 Key: IGNITE-2281
 URL: https://issues.apache.org/jira/browse/IGNITE-2281
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov






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

[jira] [Created] (IGNITE-2280) In case of one cluster/cache/metadata they should be selected by default

Alexey Kuznetsov created IGNITE-2280:


 Summary: In case of one cluster/cache/metadata they should be 
selected by default
 Key: IGNITE-2280
 URL: https://issues.apache.org/jira/browse/IGNITE-2280
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


For better user experience we need to pre-select cluster/cache/metadata where 
it make sense.



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

[jira] [Created] (IGNITE-2279) Add more space on top margin for XML/java preview

Alexey Kuznetsov created IGNITE-2279:


 Summary: Add more space on top margin for XML/java preview
 Key: IGNITE-2279
 URL: https://issues.apache.org/jira/browse/IGNITE-2279
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Priority: Minor






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

[jira] [Created] (IGNITE-2278) Rework all tooltips - add bullets where multilines text

Alexey Kuznetsov created IGNITE-2278:


 Summary: Rework all tooltips - add bullets where multilines text
 Key: IGNITE-2278
 URL: https://issues.apache.org/jira/browse/IGNITE-2278
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


We need to add bullets in tooltips where it make sense for better usability.



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

[jira] [Created] (IGNITE-2277) Add demo description to load metadata dialog

Alexey Kuznetsov created IGNITE-2277:


 Summary: Add demo description to load metadata dialog
 Key: IGNITE-2277
 URL: https://issues.apache.org/jira/browse/IGNITE-2277
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


When start demo selected we need to show on dialog what demo is.



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

[jira] [Created] (IGNITE-2276) Remove --test-drive from agent, agent readme, console UI dialogs

Alexey Kuznetsov created IGNITE-2276:


 Summary: Remove --test-drive from agent, agent readme, console UI 
dialogs
 Key: IGNITE-2276
 URL: https://issues.apache.org/jira/browse/IGNITE-2276
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Assignee: Andrey Novikov
Priority: Minor


As we now can start test drive directly from web console lets remove 
--test-drive options from agent, agent readme and from load metadata / sql 
dialogs.

Rename in web console test drive to "start demo"

Fix agent start sql demo from web console + add cancel button + add timeouts + 
add show proper error message in case of error.




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

Re: 1.5.final

2015-12-25 Thread Dmitriy Setrakyan

On Thu, Dec 24, 2015 at 11:23 PM, Sergey Kozlov 
wrote:

> Hi
>
> Last issue has been fixed and we started to prepare the release
> Apache Ignite 1.5
>

Great news! Thanks, everyone, for the effort put in. Looking forward to the
final release.


>
>
> On Thu, Dec 24, 2015 at 8:12 PM, Sergey Kozlov 
> wrote:
>
> > Yes, sure.
> >
> > On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >> If the examples work well with BinaryMarshaller, I think we can push
> this
> >> ticket to 1.6. Thoughts?
> >>
> >> On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov 
> >> wrote:
> >>
> >> > It is the way to test optimized marshaller.
> >> > The binary marshaller is a new feature and not very well tested yet
> thus
> >> > optimized marshalling shouldn't be broken for any cases
> >> >
> >> > On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan <
> >> dsetrak...@apache.org>
> >> > wrote:
> >> >
> >> > > I am seeing that IGNITE-2266 is about Optimized marshaller, not the
> >> > latest
> >> > > Binary marshaling which should be used by default. Any reason we
> care
> >> > about
> >> > > Optimized marshaller for the examples?
> >> > >
> >> > > D.
> >> > >
> >> > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk <
> >> > > alexey.goncha...@gmail.com> wrote:
> >> > >
> >> > > > Igniters,
> >> > > >
> >> > > > Another issue has been reported related to unexpected exception in
> >> > > examples
> >> > > > when optimized marshaller is used:
> >> > > > https://issues.apache.org/jira/browse/IGNITE-2266
> >> > > >
> >> > > > I will try to fix this before 2257 is fixed to fit in 1.5, however
> >> I do
> >> > > not
> >> > > > think it is a blocker for the release.
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Sergey Kozlov
> >>
> >> >
> >>
> >
> >
> >
> > --
> > Sergey Kozlov
> >
> >
>
>
> --
> Sergey Kozlov
>

[jira] [Created] (IGNITE-2275) Hadoop: restore external code execution.

Vladimir Ozerov created IGNITE-2275:
---

 Summary: Hadoop: restore external code execution.
 Key: IGNITE-2275
 URL: https://issues.apache.org/jira/browse/IGNITE-2275
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.6


Several major problems with internal job execution were revealed:
1) Native code cannot run normally.
2) Excessive permgen allocations
3) We must use some dirty hacks to prevent classloader leaks (see mocked 
classes in HadoopClassLoader).

External execution must help us with it. 

The problem is that it never worked properly. We must restore it and then test 
very thoroughly.



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

[jira] [Created] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.

Vladimir Ozerov created IGNITE-2274:
---

 Summary: Avoid ArrayList creation for a single element when 
possible.
 Key: IGNITE-2274
 URL: https://issues.apache.org/jira/browse/IGNITE-2274
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.6


Profiling shown lots of ArrayList allocations. Investigation shown the 
following usual pattern in our code:
1) Create empty ArrayList.
2) Then add a single element to it at some point. When this addition happens, 
ArrayList allocates Object[10] array. 

But in lots cases we know in advance that particular senario will contain only 
single entry in this collection.

Need to fix places where it is trivial to detect and handle.



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

[jira] [Created] (IGNITE-2273) Arrays.asList() should not be used to 1- and 2- elements.

Vladimir Ozerov created IGNITE-2273:
---

 Summary: Arrays.asList() should not be used to 1- and 2- elements.
 Key: IGNITE-2273
 URL: https://issues.apache.org/jira/browse/IGNITE-2273
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.6


There are several places in code where Arrays.asList is used as follows:
1) For a single element. These places should be replaced with 
Collections.singleton() to avoid unnecessary array allocations.
2) For two elements. Here we should create our own "doubled-singleton" 
implementation.

Some of these places are located on hot code paths (e.g. cache PUT).



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

[jira] [Created] (IGNITE-2272) visorcmd: it seems that we show incorrect value for 'Heap memory maximum'

Pavel Konstantinov created IGNITE-2272:
--

 Summary: visorcmd: it seems that we show incorrect value for 'Heap 
memory maximum'
 Key: IGNITE-2272
 URL: https://issues.apache.org/jira/browse/IGNITE-2272
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


I'm started node with JVM opts '-Xms1g -Xmx1400m' but 'node' command displays 
incorrect data for -Xmx 
{code}
| Heap memory initialized | 1gb
| Heap memory used| 1,024mb
| Heap memory committed   | 1gb
| Heap memory maximum | 1gb
{code}



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

[jira] [Created] (IGNITE-2271) visorcmd: mlist shows strange value for cache

Pavel Konstantinov created IGNITE-2271:
--

 Summary: visorcmd: mlist shows strange value for  cache
 Key: IGNITE-2271
 URL: https://issues.apache.org/jira/browse/IGNITE-2271
 Project: Ignite
  Issue Type: Bug
  Components: UI
Reporter: Pavel Konstantinov
Priority: Trivial


{code}
visor> mlist
+===+
| Name | Value  |
+===+
| c0   | -519a5764-b9cf-4b10-8a45-e434d7e0c9b9 |
{code}



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

[jira] [Created] (IGNITE-2270) GridDhtTxLocalAdapter: isConcurrentHashMap8 really needed there?