Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

2023-11-06 Thread

Hi,

Can the following PR be included in the scope of 2.16.0 version?

https://issues.apache.org/jira/browse/IGNITE-10268

https://issues.apache.org/jira/browse/IGNITE-18038

https://issues.apache.org/jira/browse/IGNITE-18572

https://issues.apache.org/jira/browse/IGNITE-19436


在 2023/11/6 16:21, Nikita Amelchev 写道:

Igniters,

I have cut the release branch: 'ignite-2.16'. Please, cherry-pick new
issues if needed.

The 2.16 scope is frozen. Unresolved not-blocking issues will be moved
on the code freeze stage.

Code freeze is planned for November 13, 2023. Please, feel free to
write if some issues are critical to be in the 2.16.

ср, 25 окт. 2023 г. в 15:00, Nikita Amelchev:

Hello Igniters,

I have created the 2.16 release page [1].

Also, I propose to cut the release branch on the scope freeze day
(November 6, 2023).

[1]https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16

вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov:

+1, fully support Nikita to be RM


пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn:


Sounds good, new JDK support seems to be in demand.

On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov  wrote:


+1

On Sun, Oct 22, 2023 at 12:29 PM Nikita Amelchev
wrote:


Dear Ignite Community!

I suggest starting Apache Ignite 2.16 release activities.

We've accumulated a hundred resolved [1] issues with new features and
bug fixes which are waiting for their release date. For example:

Calcite engine: added hints, became more stable, covered with

diagnostic

tools;
Cluster Management API (IEP-81);
Realtime CDC (IEP-104, ready to be merged);
Fixes to support JDK 14-21;
Several critical issues;
etc.

I want to propose myself to be the release manager of the planning

release.

I propose the following timeline:

Scope Freeze: November 6, 2023
Code Freeze: November 13, 2022
Voting Date: November 20, 2022
Release Date: November 27, 2022

WDYT?

[1]


https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority


--
Best wishes,
Amelchev Nikita




--
Best wishes,
Amelchev Nikita




Re: Documents about C++/C#/.NET

2019-10-21 Thread

Hi Ilya,

Many simple problems, I have submitted suggest edits, and most of them 
have been accepted.


But for example, the following page:

https://apacheignite-net.readme.io/docs/eviction-policies

I believe that many of the contents are outdated and many links are invalid.

A lot of content on this page needs to be re edited. I think it is more 
appropriate for the original author to do this work, because he knows 
more about this aspect.


在 2019/10/21 下午8:00, Ilya Kasnacheev 写道:

Hello!

I think it is a good idea to refer to Java documentation on same topic and
keed duplication of content to minimum.

Please to not hesitate to suggest edits for main Ignite documentation on
readme.io!

Thank you for your effort!

Regards,




Documents about C++/C#/.NET

2019-10-19 Thread

Hi community,

I am currently working on translating the documents of C++/ C#/.NET into 
chinese.


At present, it is found that this part of the document has a lot of 
expired content, or even mistakes.


Because the Java version is still developing rapidly, it is obviously a 
heavy workload to maintain the consistency of multiple sets of documents.


So for the C++/.NET version of documents, I have following improvement 
schemes:


In addition to the necessary differences in installation and deployment, 
for the same part of technology and concept, reduce unnecessary 
description and focus on sample code.


What's the community's opinion?



Website link update

2019-03-01 Thread
Hi,

As for Ignite's chinese document, it was previously located on a cloud 
note-taking page with the address of:

https://www.zybuluo.com/liyuj/note/230739

Because of the limited functionality and user experience, it has been migrated 
to the following address:

https://liyuj.gitee.io

The new site has a much better look and experience than it used to be.


Can someone help me modify the link on ignite. apache. org?
Thank you very much.

On Multiple Endpoints Mode of JDBC Driver

2019-02-26 Thread
Hi,

Does have load balancing function in Multiple Endpoints mode of JDBC driver?For 
example, "jdbc: ignite: thin://192.168.0.50:101, 192.188.5.40:101, 
192.168.10.230:101"
If not, will one node become the bottleneck of the whole system?


Re: About readme.io's latest docs

2018-12-12 Thread

Hi,

Does anyone in the community can help to export all the latest documents 
for me?


thanks very much.

在 2018/7/10 下午3:26, Dmitry Pavlov 写道:

Great, thanks for letting me know.

вт, 10 июл. 2018 г. в 4:01, 李玉珏@163 <18624049...@163.com 
<mailto:18624049...@163.com>>:


I have received the attachments.

在 2018/7/10 上午6:23, Prachi Garg 写道:
> I already sent him the export, but the attachments were huge. I
think
> that's why the email reply was not received by the dev list.
>
> -P
>
> On Mon, Jul 9, 2018 at 2:33 PM, Dmitry Pavlov
mailto:dpavlov@gmail.com>> wrote:
>
>> Igniters, was this question solved? Is it possible to do such
export?
>>
>> пт, 1 июн. 2018 г. в 19:40, 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>>:
>>
>>> Prachi,
>>>
>>>
>>> Can you help to export all the latest version of all documents
to me?
>>> I am ready to make a synchronization of the chinese version of the
>>> document.
>>>
>>> thanks!
>>>
>>>
>>> 在 2017/11/24 下午1:33, Prachi Garg 写道:
>>>> Attached.
>>>>
>>>> On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>
>>>> <mailto:18624049...@163.com <mailto:18624049...@163.com>>> wrote:
>>>>
>>>>      Prachi,
>>>>
>>>>
>>>>      Can you help me to export all the latest version of all
documents
>>>>      to me?
>>>>      I am ready to make a synchronization of the chinese
version of the
>>>>      document.
>>>>
>>>>      thanks!
>>>>
>>>>      在 2017/8/17 上午2:05, Prachi Garg 写道:
>>>>>      Please see attached.
>>>>>
>>>>>      -P
>>>>>
>>>>>      On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda
mailto:dma...@gridgain.com>
>>>>>      <mailto:dma...@gridgain.com
<mailto:dma...@gridgain.com>>> wrote:
>>>>>
>>>>>          Hi!
>>>>>
>>>>>          Prachi is on vacation and will send you the latest
version as
>>>>>          soon as she is back to work.
>>>>>
>>>>>          —
>>>>>          Denis
>>>>>
>>>>>>          On Aug 7, 2017, at 5:33 AM, 李玉珏@163
<18624049...@163.com <mailto:18624049...@163.com>
>>>>>>          <mailto:18624049...@163.com
<mailto:18624049...@163.com>>> wrote:
>>>>>>
>>>>>>
>>>>>>          Prachi,
>>>>>>
>>>>>>
>>>>>>          Can you help me to export all the latest version
of all
>>>>>>          documents to me?
>>>>>>          I am ready to make a synchronization of the
chinese version
>>>>>>          of the document.
>>>>>>
>>>>>>          thanks!
>>>>>>
>>>>>>
>>>>>>          在 2017/5/13 上午12:48, Prachi Garg 写道:
>>>>>>>          See attached for cpp, .net and integrations
documentation.
>>>>>>>
>>>>>>>          -P
>>>>>>>
>>>>>>>          On Fri, May 12, 2017 at 9:47 AM, Prachi Garg
>>>>>>>          mailto:pg...@gridgain.com>
<mailto:pg...@gridgain.com <mailto:pg...@gridgain.com>>> wrote:
>>>>>>>
>>>>>>>              See attached for java, file-system, and tools
>>>>>>>              documentation.
>>>>>>>
>>>>>>>              -P
>>>>>>>
>>>>>>>              On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163
>>>>>>>              <18624049...@163.com
<mailto:18624049...@163.com> <mailto:18624049...@163.com
<mailto:18624049...@163.com>>>
>>> wrote:
>>>>>>>                  Prachi,
>>>>>>>
>>>>>>>
>>>>>>>                  Can you help me to expor

Re: About readme.io's latest docs

2018-12-10 Thread

Prachi,


Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the document.

thanks!


在 2018/6/2 上午4:38, Prachi Garg 写道:

Please see attached.

On Fri, Jun 1, 2018 at 9:22 AM, 李玉珏@163 <18624049...@163.com 
<mailto:18624049...@163.com>> wrote:


Prachi,


Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the
document.

thanks!


在 2017/11/24 下午1:33, Prachi Garg 写道:

Attached.

On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Prachi,


Can you help me to export all the latest version of all
documents to me?
I am ready to make a synchronization of the chinese version
of the document.

thanks!

在 2017/8/17 上午2:05, Prachi Garg 写道:

Please see attached.

-P

On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda
mailto:dma...@gridgain.com>> wrote:

Hi!

Prachi is on vacation and will send you the latest
version as soon as she is back to work.

—
Denis


    On Aug 7, 2017, at 5:33 AM, 李玉珏@163
<18624049...@163.com <mailto:18624049...@163.com>> wrote:


Prachi,


Can you help me to export all the latest version of all
documents to me?
I am ready to make a synchronization of the chinese
version of the document.

thanks!


在 2017/5/13 上午12:48, Prachi Garg 写道:

See attached for cpp, .net and integrations
documentation.

-P

On Fri, May 12, 2017 at 9:47 AM, Prachi Garg
mailto:pg...@gridgain.com>> wrote:

See attached for java, file-system, and tools
documentation.

-P

    On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163
<18624049...@163.com <mailto:18624049...@163.com>>
wrote:

Prachi,


Can you help me to export all the latest
version of all documents to me?
I am ready to make a synchronization of the
chinese version of the document.

thanks!


在 2017/3/18 04:54, Prachi Garg 写道:

Hi,

Please see attached.

    -P

On Fri, Mar 17, 2017 at 4:56 AM, 李玉珏@163
<18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Prachi,


Can you help me to export all the latest
version of all documents to me?
I am ready to make a synchronization of
the chinese version of the document.


在 2016/12/21 00:55, Prachi Garg 写道:

Hi,
I have attached the documentation for
Hadoop/Spark and Integrations.

        -Prachi

On Tue, Dec 20, 2016 at 6:50 AM, 李玉珏@163
<18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Hi,


Hadoop Accelerator,about MapR env's
install and config,is this part of
the document missing?


在 2016/12/19 11:24, Denis Magda 写道:

Hi,

Yes, the documentation is stable.
Prachi, could you help out with the
exporting?

—
Denis


On Dec 18, 2016, at 7:09 AM,
李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Prachi,

I would like to ask, 1.8 version
of the document, is now in a
stable state?
If it is stable, can you help me
to export the latest version of
all documents to me?
I am ready to make a
synchronization of the chinese
version of the document.

thanks!


在 2016/8/23 02:25, Prachi Garg 写道:

Hi,

I've attached the latest version
  

Re: Is there a partial document missing in the section of the data grid?

2018-08-09 Thread

Oh, sorry, found it.


在 2018/8/9 下午8:39, Ilya Kasnacheev 写道:

Hello!

I am able to find all of those under
https://apacheignite.readme.io/docs/cache-configuration subsection in
"Key-Value Data Grid" section.

Regards,






Is there a partial document missing in the section of the data grid?

2018-08-09 Thread

Hi,

Some pages are missing in the latest version of the data grid 
document,why?Is there anyone who can confirm it?


https://apacheignite.readme.io/v2.4/docs/cache-modes

https://apacheignite.readme.io/v2.4/docs/partition-loss-policies

https://apacheignite.readme.io/v2.4/docs/primary-and-backup-copies

https://apacheignite.readme.io/v2.4/docs/cache-groups




Re: About readme.io's latest docs

2018-07-09 Thread

I have received the attachments.

在 2018/7/10 上午6:23, Prachi Garg 写道:

I already sent him the export, but the attachments were huge. I think
that's why the email reply was not received by the dev list.

-P

On Mon, Jul 9, 2018 at 2:33 PM, Dmitry Pavlov  wrote:


Igniters, was this question solved? Is it possible to do such export?

пт, 1 июн. 2018 г. в 19:40, 李玉珏@163 <18624049...@163.com>:


Prachi,


Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the
document.

thanks!


在 2017/11/24 下午1:33, Prachi Garg 写道:

Attached.

On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>> wrote:

 Prachi,


 Can you help me to export all the latest version of all documents
 to me?
 I am ready to make a synchronization of the chinese version of the
 document.

 thanks!

 在 2017/8/17 上午2:05, Prachi Garg 写道:

 Please see attached.

 -P

 On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda mailto:dma...@gridgain.com>> wrote:

 Hi!

 Prachi is on vacation and will send you the latest version as
 soon as she is back to work.

 —
 Denis


 On Aug 7, 2017, at 5:33 AM, 李玉珏@163 <18624049...@163.com
 <mailto:18624049...@163.com>> wrote:


 Prachi,


 Can you help me to export all the latest version of all
 documents to me?
 I am ready to make a synchronization of the chinese version
 of the document.

 thanks!


 在 2017/5/13 上午12:48, Prachi Garg 写道:

 See attached for cpp, .net and integrations documentation.

 -P

 On Fri, May 12, 2017 at 9:47 AM, Prachi Garg
 mailto:pg...@gridgain.com>> wrote:

 See attached for java, file-system, and tools
 documentation.

 -P

     On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163
 <18624049...@163.com <mailto:18624049...@163.com>>

wrote:

 Prachi,


 Can you help me to export all the latest version of
 all documents to me?
 I am ready to make a synchronization of the chinese
 version of the document.

 thanks!


 在 2017/3/18 04:54, Prachi Garg 写道:

 Hi,

 Please see attached.

     -P

 On Fri, Mar 17, 2017 at 4:56 AM, 李玉珏@163
 <18624049...@163.com <mailto:18624049...@163.com>>
 wrote:

 Prachi,


 Can you help me to export all the latest
 version of all documents to me?
 I am ready to make a synchronization of the
 chinese version of the document.


 在 2016/12/21 00:55, Prachi Garg 写道:

 Hi,
 I have attached the documentation for
 Hadoop/Spark and Integrations.

     -Prachi

 On Tue, Dec 20, 2016 at 6:50 AM, 李玉珏@163
 <18624049...@163.com
 <mailto:18624049...@163.com>> wrote:

 Hi,


 Hadoop Accelerator,about MapR env's
 install and config,is this part of the
 document missing?


 在 2016/12/19 11:24, Denis Magda 写道:

 Hi,

 Yes, the documentation is stable.
 Prachi, could you help out with the
 exporting?

 —
     Denis


 On Dec 18, 2016, at 7:09 AM, 李玉珏@163
 <18624049...@163.com
 <mailto:18624049...@163.com>> wrote:

 Prachi,

 I would like to ask, 1.8 version of the
 document, is now in a stable state?
 If it is stable, can you help me to
 export the latest version of all
 documents to me?
 I am ready to make a synchronization of
 the chinese version of the document.

 thanks!


 在 2016/8/23 02:25, Prachi Garg 写道:

 Hi,

 I've attached the latest version of
 Ignite and Hadoop/Spark documentation.
 Let me know if this format is ok.

     -Prachi

 On Thu, Aug 18, 2016 at 10:40 PM,
 李玉珏@163<18624049...@163.com
 <mailto:18624049...@163.co

Re: About readme.io's latest docs

2018-06-01 Thread

Prachi,


Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the document.

thanks!


在 2017/11/24 下午1:33, Prachi Garg 写道:

Attached.

On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com 
<mailto:18624049...@163.com>> wrote:


Prachi,


Can you help me to export all the latest version of all documents
to me?
I am ready to make a synchronization of the chinese version of the
document.

thanks!

在 2017/8/17 上午2:05, Prachi Garg 写道:

Please see attached.

-P

On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda mailto:dma...@gridgain.com>> wrote:

Hi!

Prachi is on vacation and will send you the latest version as
soon as she is back to work.

—
Denis


On Aug 7, 2017, at 5:33 AM, 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>> wrote:


Prachi,


Can you help me to export all the latest version of all
documents to me?
I am ready to make a synchronization of the chinese version
of the document.

thanks!


在 2017/5/13 上午12:48, Prachi Garg 写道:

See attached for cpp, .net and integrations documentation.

-P

On Fri, May 12, 2017 at 9:47 AM, Prachi Garg
mailto:pg...@gridgain.com>> wrote:

See attached for java, file-system, and tools
documentation.

-P

    On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163
<18624049...@163.com <mailto:18624049...@163.com>> wrote:

Prachi,


Can you help me to export all the latest version of
all documents to me?
I am ready to make a synchronization of the chinese
version of the document.

thanks!


在 2017/3/18 04:54, Prachi Garg 写道:

Hi,

Please see attached.

-P

    On Fri, Mar 17, 2017 at 4:56 AM, 李玉珏@163
<18624049...@163.com <mailto:18624049...@163.com>>
wrote:

Prachi,


Can you help me to export all the latest
version of all documents to me?
I am ready to make a synchronization of the
chinese version of the document.


在 2016/12/21 00:55, Prachi Garg 写道:

Hi,
I have attached the documentation for
Hadoop/Spark and Integrations.

-Prachi

On Tue, Dec 20, 2016 at 6:50 AM, 李玉珏@163
<18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Hi,


Hadoop Accelerator,about MapR env's
install and config,is this part of the
document missing?


在 2016/12/19 11:24, Denis Magda 写道:

Hi,

Yes, the documentation is stable.
Prachi, could you help out with the
exporting?

—
    Denis


On Dec 18, 2016, at 7:09 AM, 李玉珏@163
<18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Prachi,

I would like to ask, 1.8 version of the
document, is now in a stable state?
If it is stable, can you help me to
export the latest version of all
documents to me?
I am ready to make a synchronization of
the chinese version of the document.

thanks!


在 2016/8/23 02:25, Prachi Garg 写道:

Hi,

I've attached the latest version of
Ignite and Hadoop/Spark documentation.
Let me know if this format is ok.

    -Prachi

On Thu, Aug 18, 2016 at 10:40 PM,
李玉珏@163<18624049...@163.com
<mailto:18624049...@163.com>>wrote:

Dmitriy,Prachi:

Can send me a copy of the latest
document? Including the core of
Ignite and the Hadoop/Spark parts,
after the release of the 1.7
version, I intend to do an update
on the document.


在 16/6/10 08:37, Prachi Garg 写道:


Fwd: Re: About readme.io's latest docs

2017-11-23 Thread

Hi,


If some body in community can help  to export all the latest version of 
documents in the readme.io to me?

I am ready to make a synchronization of the chinese version of the document.

thanks!

 转发的消息 
主题: Re: About readme.io's latest docs
日期: Wed, 16 Aug 2017 11:05:41 -0700
发件人:Prachi Garg 
收件人:Denis Magda 
抄送:     李玉珏@163 <18624049...@163.com>



Please see attached.

-P

On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda <mailto:dma...@gridgain.com>> wrote:


   Hi!

   Prachi is on vacation and will send you the latest version as soon
   as she is back to work.

   —
   Denis


On Aug 7, 2017, at 5:33 AM, 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>> wrote:


Prachi,


Can you help me to export all the latest version of all documents
to me?
I am ready to make a synchronization of the chinese version of the
document.

thanks!


在 2017/5/13 上午12:48, Prachi Garg 写道:

See attached for cpp, .net and integrations documentation.

-P

On Fri, May 12, 2017 at 9:47 AM, Prachi Garg mailto:pg...@gridgain.com>> wrote:

See attached for java, file-system, and tools documentation.

-P

        On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Prachi,


Can you help me to export all the latest version of all
documents to me?
I am ready to make a synchronization of the chinese
version of the document.

thanks!


在 2017/3/18 04:54, Prachi Garg 写道:

Hi,

Please see attached.

    -P

On Fri, Mar 17, 2017 at 4:56 AM, 李玉珏@163
<18624049...@163.com <mailto:18624049...@163.com>> wrote:

Prachi,


Can you help me to export all the latest version of
all documents to me?
I am ready to make a synchronization of the chinese
version of the document.


在 2016/12/21 00:55, Prachi Garg 写道:

Hi,
I have attached the documentation for Hadoop/Spark
and Integrations.

    -Prachi

On Tue, Dec 20, 2016 at 6:50 AM, 李玉珏@163
<18624049...@163.com <mailto:18624049...@163.com>>
wrote:

Hi,


Hadoop Accelerator,about MapR env's install and
config,is this part of the document missing?


在 2016/12/19 11:24, Denis Magda 写道:

Hi,

Yes, the documentation is stable. Prachi,
could you help out with the exporting?

—
    Denis


On Dec 18, 2016, at 7:09 AM, 李玉珏@163
<18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Prachi,

I would like to ask, 1.8 version of the
document, is now in a stable state?
If it is stable, can you help me to export
the latest version of all documents to me?
I am ready to make a synchronization of the
chinese version of the document.

thanks!


在 2016/8/23 02:25, Prachi Garg 写道:

Hi,

I've attached the latest version of Ignite
and Hadoop/Spark documentation. Let me know
if this format is ok.

        -Prachi

On Thu, Aug 18, 2016 at 10:40 PM,
李玉珏@163<18624049...@163.com
<mailto:18624049...@163.com>>wrote:

Dmitriy,Prachi:

Can send me a copy of the latest
document? Including the core of Ignite
and the Hadoop/Spark parts, after the
release of the 1.7 version, I intend to
do an update on the document.


在 16/6/10 08:37, Prachi Garg 写道:

Please see attached.

-Prachi

On Mon, Jun 6, 2016 at 3:16 PM, Dmitriy
Setrakyanmailto:dsetrak...@apache.org>>wrote:

Prachi, do you mind providing the
export for the Hadoop/Spark
        documentation?

On Fri, Jun 3, 2016 at 5:55 AM,
李玉珏@163<18624049...@163.com
<mailto:18624049...@163.com>>wrote:

Hi:

Thanks a 

about document missing

2017-09-08 Thread

Hi


The documentation below is missing in the 2.1.0 version. I hope someone 
in the community will help to confirm it:


https://apacheignite.readme.io/v2.0/docs/sliding-windows

https://apacheignite.readme.io/v2.0/docs/streaming-example



Re: [DISCUSSION] Urgent Ignite bug fix release

2017-09-06 Thread
Currently,the latest version is apache-ignite-fabric-2.1.0-bin.zip 
<http://mirrors.hust.edu.cn/apache//ignite/2.1.0/apache-ignite-fabric-2.1.0-bin.zip>.


and in 
http://www.gridgainsystems.com/nexus/content/repositories/external/org/apache/ignite/ignite-core/


the latest version is 2.1.4,

As I understand it, add 1 on the version number of 2.1.4, and then 
publish it to the ignite main website to ensure that both versions are 
consistent,is it ok?



在 2017/9/1 下午6:57, Anton Vinogradov 写道:

Hi,

Reasonable question, but I propose to keep 2.2 as a release version 
for this urgent release, since we never released X.Y.Z version before.


Let's discuss this at separate thread.
Could you please start it?


On Fri, Sep 1, 2017 at 4:49 AM, 李玉珏@163 <18624049...@163.com 
<mailto:18624049...@163.com>> wrote:


Since it's an urgent bugfix version, why can't the version number
be defined as 2.1.1 or 2.1.4?
After all, functionality has not increased and documents do not
require big changes.
If the version number is 2.1 series, there is no need to publish a
new version of the document.



在 2017/8/28 下午10:19, Anton Vinogradov 写道:

Igniters,

Seems 2.2 is a urgent bugfix release, so it should be based on
2.1,
In this case all other issues with fixVersion = 2.2 should be
moved to 2.3.

Currently, I see 835 issues with fixVersion = 2.2

Seems we should have only 4 issues with fixVersion = 2.2:
- Change default max memory size from 80% to 20% -
https://issues.apache.org/jira/browse/IGNITE-6182
<https://issues.apache.org/jira/browse/IGNITE-6182>
- Detecting low memory on ignite node startup -
https://issues.apache.org/jira/browse/IGNITE-6003
<https://issues.apache.org/jira/browse/IGNITE-6003>
- Backport of improvements to checkpoint algorithm -
https://issues.apache.org/jira/browse/IGNITE-??
<https://issues.apache.org/jira/browse/IGNITE-??>??
- ML profile is missing in 2.1 binary release -
https://issues.apache.org/jira/browse/IGNITE-6193
<https://issues.apache.org/jira/browse/IGNITE-6193>

Please correct me in case I've missed something.

Ivan,

Let's include to the release tickets with optimizations of
checkpointing

algorithm:

https://issues.apache.org/jira/browse/IGNITE-6178
<https://issues.apache.org/jira/browse/IGNITE-6178>
https://issues.apache.org/jira/browse/IGNITE-6033
<https://issues.apache.org/jira/browse/IGNITE-6033>
https://issues.apache.org/jira/browse/IGNITE-5961
<https://issues.apache.org/jira/browse/IGNITE-5961>
This will help users who are experiencing problems with
slow checkpoints.
Also, let's include
https://issues.apache.org/jira/browse/IGNITE-6183
<https://issues.apache.org/jira/browse/IGNITE-6183> to

soften "Ignite node crashed in the middle of checkpoint"
message as per
discussion <

http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-close-G-stop-name-true-Change-flag-cancel-to-false-td20473.html

<http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-close-G-stop-name-true-Change-flag-cancel-to-false-td20473.html>

.

All of these issues should have fixVersion 2.3.
Please create backport issue and link it to all necessary issues.

P.s. I've created branch ignite-2.2, currently it equals to
ignite-2.1.

On Mon, Aug 28, 2017 at 4:05 PM, Anton Vinogradov
mailto:avinogra...@gridgain.com>>
wrote:

Denis,

BTW, who is considered to be the release manager of
this release?

I'll do it.

On Mon, Aug 28, 2017 at 3:54 PM, Seliverstov Igor
mailto:gvvinbl...@gmail.com>>
wrote:

Ok, the check happens at the node start time or on
NODE_JOIN event

in general it looks like:

1) calculate expected used memory = heap max + system
cache max + all
custom policies max + default policy size and put it
into a node attribute

2) get total physycal memory, calculate expected safe
to be used memory
amount (leave 4 gb min or 20% of available memory for OS)

3) if expected used memory + expected used memory of
other nodes on the
host > than safe to be used memory amount, start
calculating suggestions

4) Each ignite instance needs at least 512mb heap +
40mb

Re: [DISCUSSION] Urgent Ignite bug fix release

2017-08-31 Thread
Since it's an urgent bugfix version, why can't the version number be 
defined as 2.1.1 or 2.1.4?
After all, functionality has not increased and documents do not require 
big changes.
If the version number is 2.1 series, there is no need to publish a new 
version of the document.



在 2017/8/28 下午10:19, Anton Vinogradov 写道:

Igniters,

Seems 2.2 is a urgent bugfix release, so it should be based on 2.1,
In this case all other issues with fixVersion = 2.2 should be moved to 2.3.

Currently, I see 835 issues with fixVersion = 2.2

Seems we should have only 4 issues with fixVersion = 2.2:
- Change default max memory size from 80% to 20% -
https://issues.apache.org/jira/browse/IGNITE-6182
- Detecting low memory on ignite node startup -
https://issues.apache.org/jira/browse/IGNITE-6003
- Backport of improvements to checkpoint algorithm -
https://issues.apache.org/jira/browse/IGNITE-
- ML profile is missing in 2.1 binary release -
https://issues.apache.org/jira/browse/IGNITE-6193

Please correct me in case I've missed something.

Ivan,

Let's include to the release tickets with optimizations of checkpointing

algorithm:

https://issues.apache.org/jira/browse/IGNITE-6178
https://issues.apache.org/jira/browse/IGNITE-6033
https://issues.apache.org/jira/browse/IGNITE-5961
This will help users who are experiencing problems with slow checkpoints.
Also, let's include https://issues.apache.org/jira/browse/IGNITE-6183 to

soften "Ignite node crashed in the middle of checkpoint" message as per
discussion <
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-close-G-stop-name-true-Change-flag-cancel-to-false-td20473.html

.

All of these issues should have fixVersion 2.3.
Please create backport issue and link it to all necessary issues.

P.s. I've created branch ignite-2.2, currently it equals to ignite-2.1.

On Mon, Aug 28, 2017 at 4:05 PM, Anton Vinogradov 
wrote:


Denis,


BTW, who is considered to be the release manager of this release?

I'll do it.

On Mon, Aug 28, 2017 at 3:54 PM, Seliverstov Igor 
wrote:


Ok, the check happens at the node start time or on NODE_JOIN event

in general it looks like:

1) calculate expected used memory = heap max + system cache max + all
custom policies max + default policy size and put it into a node attribute

2) get total physycal memory, calculate expected safe to be used memory
amount (leave 4 gb min or 20% of available memory for OS)

3) if expected used memory + expected used memory of other nodes on the
host > than safe to be used memory amount, start calculating suggestions

4) Each ignite instance needs at least 512mb heap + 40mb system cache +
100mb default polycy, if available memory is less we cannot suggest
anything reasonable, print warning, stop calculation.

5) check heap size (shouldn't exceed 30% of available memory (total_memory
- reserved for OS memory) * 30% for all JVMs, if it exeedes, suggest just
calculated value or 512MB minimal)

6) check if system cache size changed, suggest default value if it's so

7) in case 100 mb * policies count < available memory, suggest using
default policy with max size equals to remaining memory (available - heap
-
system cache)

8) calculate new size for each memory policy ( it's user defined size *
(remaining / (all_policies_size * nodes_cnt)); in proportion to
remaining memory, devided by nodes number on the host or 100 mb minimal)

9) print suggestions



2017-08-28 15:10 GMT+03:00 Dmitriy Setrakyan :


Igor, can you please describe the algorithm with all the thresholds?

On Mon, Aug 28, 2017 at 4:56 AM, Seliverstov Igor 
The suggestion here is based on initial settings, and it's so because

there

is no other nodes on the host in the example.

The algorithm tries to preserve the original ratio of memory policies
keeping numbers reasonable (for example after some thresshold it will
suggest not to use several memory policies if there is not enough of

memory

for all of them) and taking into consideration nodes count on the

host,

each jvm heap, needed memory for OS, etc

2017-08-28 14:38 GMT+03:00 Dmitriy Setrakyan :


Looks good, but why in the example provided are we suggesting 8GB? 2

nodes

with 8GB will completely exhaust the available memory. I would

suggest

6

or

7GB.

Also, why 100MB for default policy. Anything under 1GB seems too

small.

Can you please comment?

D.

On Mon, Aug 28, 2017 at 3:31 AM, Seliverstov Igor <

gvvinbl...@gmail.com>

wrote:


One more example of possible warning:

-
Excessive memory usage by Ignite node process (performance may

drop)

[requested=44613MB, available=15942MB].

Please tune the folowing settings as suggested:
   MemoryPolicyConfiguration.initialSize for bigPlc: 8102MB
   MemoryPolicyConfiguration.maxSize for bigPlc: 8102MB
   MemoryPolicyConfiguration.initialSize for dfltPlc: 100MB
   MemoryPolicyConfiguration.maxSize for dfltPlc: 100MB

Current settings:
   Java Heap  maxSize: 3543MB
   Java Heap initSi

Re: Ignite Durable Memory & Persistent Store introduction for developers

2017-08-31 Thread

I will help to translate into chinese.


在 2017/8/31 下午6:39, Alexey Dmitriev 写道:

Dmitry,
Both languages are preferable. :)
English has priority.

31 авг. 2017 г. 1:06 ПП пользователь "Dmitry Pavlov" 
написал:


Sure, I can blog about it, but timelines depend on free time. Which
language is preferred? Russian or English? Also I plan to extend existing
wiki pages with more details, and add new pages explaining Ignite to
newbies. This activity depends on interest of community and new questions
related to pages.

чт, 31 авг. 2017 г. в 3:53, Dmitriy Setrakyan :


Dmitriy, this is very useful! Any chance you can also blog about it?

On Wed, Aug 30, 2017 at 6:24 PM, Dmitry Pavlov 
wrote:


Hi Igniters,


I am glad to introduce two new wiki articles. These articles contain
high-level description of

- Ignite Durable Memory (
https://cwiki.apache.org/confluence/display/IGNITE/
Ignite+Durable+Memory+-+under+the+hood
)

- and Ignite Persistent Store (
https://cwiki.apache.org/confluence/display/IGNITE/
Ignite+Persistent+Store+-+under+the+hood
)

These articles cover basic principles and internal design. Pages may be
useful for new contributors during start of working with persistent

store

code base.


I would like to thank all contributors who helped me with my questions.
Their answers and support made it possible to start this description.


I will appreciate any feedback and questions. Suggestions and edits are
welcome, of course.


Sincerely,

Dmitriy Pavlov






Re: Policy for update third-party dependencies

2017-08-20 Thread
If the third party library is incompatible with the new version and the 
old version (such as lucene3.5.0-5.5.2), and the dependent version of 
Ignite is older, it may cause conflicts in the user's system.
For such scenarios, I think that updating third-party dependencies's 
major version is valuable.



在 2017/8/17 上午8:26, Denis Magda 写道:

I would respond why do we need to update? Some bug, new capabilities, security 
breach? Alexey K., please shed some light on this.

—
Denis


On Aug 16, 2017, at 5:12 PM, Dmitriy Setrakyan  wrote:

On Wed, Aug 16, 2017 at 5:02 PM, Denis Magda  wrote:


Honestly, I wouldn’t touch a dependency if it works like a charm and
nobody requested us to migrate to a new version.

Why do you need to update Apache Common coded?


Not sure I agree. Why not update it?




—
Denis


On Aug 16, 2017, at 10:36 AM, Alexey Kuznetsov 

wrote:

Done

https://issues.apache.org/jira/browse/IGNITE-6090

On Wed, Aug 16, 2017 at 8:01 PM, Dmitriy Setrakyan <

dsetrak...@apache.org>

wrote:


The answer is Yes, we should update. Jira ticket assigned to the next
release should be enough in my view.

D.

On Wed, Aug 16, 2017 at 2:38 AM, Alexey Kuznetsov <

akuznet...@apache.org>

wrote:


Hi, All!

Do we have any policy for updating third-party dependencies?

For example, I found that we are using very old  Apache Common codec

v.1.6

(released in 2011)
And latest is Apache Common codec v.1.10

Do we need to update to new versions from time to time?
And how?

Just create JIRA issue, update pom.xml and run all tests on TC - will

be

enough?

--
Alexey Kuznetsov




--
Alexey Kuznetsov







Re: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

2017-07-29 Thread

Anton,

http://repo.maven.apache.org/maven2/org/apache/ignite/ignite-core/2.1.0/

The timestamp for uploading the artifact is 2017-07-20 17:35, Is that 
correct?



在 2017/7/28 上午2:06, Anton Vinogradov 写道:

Done.

- Maven artifacts released
- Sources released
- Site updated
- Git tag added

On Thu, Jul 27, 2017 at 4:24 PM, Anton Vinogradov  wrote:


Igniters,

Apache Ignite 2.1.0 release (RC4) has been accepted.

7 "+1" votes received:

- Valentin Kulichenko (binding)
- Nikolai Tikhonov (binding)
- Alexey Kuznetsov (binding)
- Yakov Zhdanov (binding)
- Konstantin Boudnik (binding)
- Andrey Gura (binding)
- Denis Magda (binding)

Vote thread:

http://apache-ignite-developers.2346864.n4.nabble.
com/VOTE-Apache-Ignite-2-1-0-RC4-td19969.html

Ignite 2.1.0 will be released soon. Woohoo!






Re: Replace Cron4J with Quartz for ignite-schedule module.

2017-06-21 Thread
Hi,


There is also an alternative that the community can consider using the 
scheduling functionality in the spring-context module, for the following 
reasons:
1.quartz is a very heavy framework, and most functions we don't need;
2., we already have spring dependencies in our project without introducing new 
dependencies;
3.spring is also Apache 2.0 license;
4.spring's scheduler supports standard CRON, and cron4j does not support 
standard CRON;
5.spring's code quality is very good, maintainability is good, and the quality 
of quartz code is not very good.
On 06/21/2017 13:26,Alexey Kuznetsov wrote:
Hi!

1) Cron4J is very old:
  Latest Cron4j 2.2.5 released: *28-Dec-2011 *
  Latest Quarz 2.3.0 released: *20-Apr-2017*

2) Not very friendly license:
  CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
  Quartz is freely usable, licensed under the *Apache 2.0* license.

So, if we replace Cron4J  with Quartz we can move *ignite-schedule* module
 from lgpl profile to main distribution.

Any objections?

If no, I will create JIRA issue and implement this change.

-- 
Alexey Kuznetsov


Re: Upgrade dependency to outdated Lucene 3.5.0

2017-05-23 Thread
Lucene6 requires JDK8 and later versions, and I think it might be 
reasonable to update to the Lucene5.5.4 version.



在 2017/5/23 22:07, Andrey Mashenkov 写道:

Hi Igniters,

Ignite-indexing module has outdated dependency to apache-lucene-3.5.0,
however, actual version of lucene for now is 6.5.1. Here is a ticket [1].

Store format version of 3.x is deprecated in 4.x and does not supported at
all
in higher versions, that cause difficulties to integrate with ignite on
user side.

Apache Lucene 6.x seems doen't support <=4.x index format,
but 5.x index format can be used via additional jar with old codecs.

Also, I've found GridLuceneIndex stores index in offheap via old approach
and
page memory is not supported, so it can't be persisted (looking forward to
PDS).

Seems, we will not break any compatibility if we upgrade lucene version in
2.1,
until (or together with) Ignite full-text-search component supports page
memory and PDS merged to ignite.
I think we should upgrade to latest 6.x version, as it will much harder to
do it later.


Is there any cons\pros to upgrade lucene dependency up to latest 6.x
version?


[1] https://issues.apache.org/jira/browse/IGNITE-3562






Re: About thread problem of service execution in Ignite Service Grid

2017-03-14 Thread
This problem occurs in a stand-alone development environment, as well as 
multiple node deployment environment.
I think it is reasonable to say that no matter where the service is 
accessed, it is a different thread, which will ensure consistent behavior.


在 2017/3/13 23:52, Valentin Kulichenko 写道:

Why would you use a thread local in a service? What design you think is
reasonable?

-Val

On Mon, Mar 13, 2017 at 2:03 PM, 李玉珏@163 <18624049...@163.com> wrote:


Hi,

When in service grid service execution, if the local node deployment
services, will directly call the local deployment service, otherwise it
will find the service in the grid.

The local service, and the caller will use the same thread, in this case,
the two threads‘s state is different, that is to say, the same call, have
different behavior in different scene, I think the design is not reasonable.

For example, a thread local variable is defined, and according to the
above description, the value of the same variable may be different for
different scenarios.








About thread problem of service execution in Ignite Service Grid

2017-03-13 Thread

Hi,

When in service grid service execution, if the local node deployment 
services, will directly call the local deployment service, otherwise it 
will find the service in the grid.


The local service, and the caller will use the same thread, in this 
case, the two threads‘s state is different, that is to say, the same 
call, have different behavior in different scene, I think the design is 
not reasonable.


For example, a thread local variable is defined, and according to the 
above description, the value of the same variable may be different for 
different scenarios.





Re: IGNITE-3727: why did not merge into the 1.8 version?

2017-02-14 Thread

Semen,


Can this issue be merged into version 1.9?


在 2016/12/13 16:18, Semyon Boikov 写道:

Hi,

We had a lot of more priority issues so I somehow missed IGNITE-3732. As a
workaround it is possible to create special thread pool and when message is
sent to local node execute message listener there instead of
IgniteMessaging usage.

Thanks

On Sun, Dec 11, 2016 at 5:56 AM, Denis Magda  wrote:


Alright, looks like I confused it with some other task initially.

The ticket you’re talking about is still under review and looks abandoned
https://issues.apache.org/jira/browse/IGNITE-3727 <
https://issues.apache.org/jira/browse/IGNITE-3727>

Dmitriy G., Sam, is the ticket ready for the merge?

—
Denis


On Dec 10, 2016, at 6:29 PM, 李玉珏@163 <18624049...@163.com> wrote:

Denis,

I found  the branch 3727:

https://github.com/gridgain/apache-ignite/tree/ignite-3727-2

But it appear that the code is not merged into the master?

for example, IgniteMessagingImpl.java,the related code is still an old

version,8 months ago.


在 2016/12/10 22:56, Denis Magda 写道:

Hi,

It was released in 1.8. I’ve just checked git logs.

How did you come up with such a conclusion? Something doesn't work on

your side?

—
Denis


On Dec 10, 2016, at 5:39 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi:


IGNITE-3727,this issue has been fixed and tested in september,why did

not merge into the 1.8 version?









Re: about lucene version dependent on ignite-indexing module

2017-01-26 Thread

Sergi,

In the Ignite technology system, is not only the ignite-indexing module 
depends on the Lucene?


From the API point of view, Lucene should be transparent to developers, 
but for some of the data format generated, it should be incompatible.



在 2017/1/26 19:07, Sergi Vladykin 写道:

I'm not a big Lucene expert, but such a major upgrade can be a breaking
change for some users. I'd suggest to do it in 2.0.

Sergi

2017-01-26 10:16 GMT+03:00 李玉珏@163 <18624049...@163.com>:


If the new version is not available, we can only use the 3.5.0 version,
because the major version of the incompatibility, we have to discuss this
problem.

Is this version used because of technical limitations? If there is no
limit, our team can look at, assess the workload and time to see if this
problem can be solved, and then pick this ticket.

在 2017/1/26 07:29, Denis Magda 写道:


Hi,

Here is a ticket for that.
https://issues.apache.org/jira/browse/IGNITE-3562 <
https://issues.apache.org/jira/browse/IGNITE-3562>

As a temporary solution can you exclude the new version from your maven
file?

Sergi, Igniters,

Is there any technical reason why we’re still on this ancient version? I
do remember we discussed this so far but didn’t manage to find the
discussion.

—
Denis

On Jan 24, 2017, at 5:30 PM, 李玉珏  wrote:

Community,


Ignite's ignite-indexing module relies on the lucene, the current
version is dependent on 3.5.0, this version is too old, I would like to
ask, can the version of the lucene upgrade to 6.x?


Lucene is not compatible with the large version, but the coordinates of
the maven is the same, which gives us trouble.









Re: about lucene version dependent on ignite-indexing module

2017-01-25 Thread
If the new version is not available, we can only use the 3.5.0 version, 
because the major version of the incompatibility, we have to discuss 
this problem.


Is this version used because of technical limitations? If there is no 
limit, our team can look at, assess the workload and time to see if this 
problem can be solved, and then pick this ticket.


在 2017/1/26 07:29, Denis Magda 写道:

Hi,

Here is a ticket for that.
https://issues.apache.org/jira/browse/IGNITE-3562 
<https://issues.apache.org/jira/browse/IGNITE-3562>

As a temporary solution can you exclude the new version from your maven file?

Sergi, Igniters,

Is there any technical reason why we’re still on this ancient version? I do 
remember we discussed this so far but didn’t manage to find the discussion.

—
Denis


On Jan 24, 2017, at 5:30 PM, 李玉珏  wrote:

Community,


Ignite's ignite-indexing module relies on the lucene, the current version is 
dependent on 3.5.0, this version is too old, I would like to ask, can the 
version of the lucene upgrade to 6.x?


Lucene is not compatible with the large version, but the coordinates of the 
maven is the same, which gives us trouble.








about lucene version dependent on ignite-indexing module

2017-01-24 Thread
Community,


Ignite's ignite-indexing module relies on the lucene, the current version is 
dependent on 3.5.0, this version is too old, I would like to ask, can the 
version of the lucene upgrade to 6.x?


Lucene is not compatible with the large version, but the coordinates of the 
maven is the same, which gives us trouble.



Re: Blogs updates: 1.8 release, Redis, Microservices and more

2017-01-19 Thread

great!


在 2017/1/19 10:24, Denis Magda 写道:

Community,

Some of us published new blog posts this month. Please go ahead and enjoy:
https://ignite.apache.org/blogs.html 

—
Denis





Re: About RoundRobinLoadBalancingSpi

2016-12-29 Thread

Val,

Javadoc also need to be modified.


在 2016/12/29 00:08, Valentin Kulichenko 写道:

Hi,

Thanks for pointing this out. I fixed the documentation.

-Val

On Tue, Dec 27, 2016 at 7:50 PM, 李玉珏  wrote:


Hi,


In RoundRobinLoadBalancingSpi,according to the description of the
document,per-task mode is the default configuration and should fit most of
the use cases as it provides a fairly well-distributed split and also
ensures that jobs within a single task are spread out across nodes to the
maximum.


But from the source code, global mode is the default value.
I want to ask,does this belong to the document description issue, or is a
bug?





About RoundRobinLoadBalancingSpi

2016-12-27 Thread
Hi,


In RoundRobinLoadBalancingSpi,according to the description of the 
document,per-task mode is the default configuration and should fit most of the 
use cases as it provides a fairly well-distributed split and also ensures that 
jobs within a single task are spread out across nodes to the maximum.


But from the source code, global mode is the default value.
I want to ask,does this belong to the document description issue, or is a bug?

Re: Document issue

2016-12-23 Thread
I was translating chinese documents, but I didn't use AWS or Google 
compute, I just thought the document was a little weird.



在 2016/12/23 17:59, Nikolai Tikhonov 写道:

Denis,
Yes, you are right. The pages contains the latest information about cloud
images.

If you have problem with deployment, could you point on step which wrong?



On Thu, Dec 22, 2016 at 8:39 PM, Denis Magda  wrote:


Hi,

Do be honest I don’t see any issue there. Apache Ignite images for AWS and
GCE run inside of a docker container. So the latest docker related commands
look valid for me. Nick, please confirm.

—
Denis


On Dec 22, 2016, at 8:10 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi,

The following two pages of documents, more errors, I hope the community

can be a comprehensive review, and then fix it.

https://apacheignite.readme.io/docs/aws-deployment

https://apacheignite.readme.io/docs/google-compute-deployment


For example, under the two page, are all about docker information.









Document issue

2016-12-22 Thread

Hi,

The following two pages of documents, more errors, I hope the community 
can be a comprehensive review, and then fix it.


https://apacheignite.readme.io/docs/aws-deployment

https://apacheignite.readme.io/docs/google-compute-deployment


For example, under the two page, are all about docker information.




Re: Make async API great again

2016-12-20 Thread

+1


在 2016/12/20 18:05, Pavel Tupitsyn 写道:

Huge +1 on this. Current API is very confusing.

On Tue, Dec 20, 2016 at 11:56 AM, Vladimir Ozerov 
wrote:


Igniters,

We have complaints about design of our async API, and upcoming Ignite 2.0
release is a good candidate to fix it.

Problems:

1) API is verbose and error prone:

Ignite asyncCache = cache.withAsync();
asyncCache.get(key);
IgniteFuture fut = asyncCache.future();

2) Hard to reason which methods support async execution and which are not.
@IgniteAsyncSupported is not user friendly because it forces users to read
JavaDocs thoroughly.

3) No control on where IgniteFuture.listen() and IgniteFuture.chain()
methods are executed. User can easily inadvertently add some code which
will lead to starvation. E.g.:

IgniteFuture fut = asyncCache.future();
fut.listen((fut) -> { cache.put(...); }); // Starvation because callback
might be executed in sys pool.

4) We have incorrect IO optimization: if message is to be send to local
node, it will be executed synchronously. See GridIoManager.send() method.
This is wrong, because it breaks pool semantics. E.g. cache operations must
be executed in sys pool, but can be executed in public pool.

I propose to fix all that problems in Apache Ignite 2.0:

1) Let's have simple and straightforward API:
IgniteFuture fut = cache.getAsync(key);

2) Fix local node "optimization" in GridIoManager - messages should not be
processed synchronously.

3) User continuations must never be executed synchronously, always delegate
them to public pool by default (or may be to Java FJP?).

4) Allow users to specify thread pool for their continuations:
IgniteFuture.listen(Closure, ExecutorService);
IgniteFufure.chain(Closure, ExecutorService);

See Akka "Dispatcher" [1] as example of similar concept.

Thoughts?

[1] http://doc.akka.io/docs/akka/current/scala/dispatchers.html

Vladimir.






Re: IGNITE-3727: why did not merge into the 1.8 version?

2016-12-14 Thread

Semen Boikov,

This issue is very important to our development environment, we have now 
used other techniques to replace.
I very much hope that this patch can be merged into the next version, 
very grateful!



在 2016/12/13 16:18, Semyon Boikov 写道:

Hi,

We had a lot of more priority issues so I somehow missed IGNITE-3732. As a
workaround it is possible to create special thread pool and when message is
sent to local node execute message listener there instead of
IgniteMessaging usage.

Thanks

On Sun, Dec 11, 2016 at 5:56 AM, Denis Magda  wrote:


Alright, looks like I confused it with some other task initially.

The ticket you’re talking about is still under review and looks abandoned
https://issues.apache.org/jira/browse/IGNITE-3727 <
https://issues.apache.org/jira/browse/IGNITE-3727>

Dmitriy G., Sam, is the ticket ready for the merge?

—
Denis


On Dec 10, 2016, at 6:29 PM, 李玉珏@163 <18624049...@163.com> wrote:

Denis,

I found  the branch 3727:

https://github.com/gridgain/apache-ignite/tree/ignite-3727-2

But it appear that the code is not merged into the master?

for example, IgniteMessagingImpl.java,the related code is still an old

version,8 months ago.


在 2016/12/10 22:56, Denis Magda 写道:

Hi,

It was released in 1.8. I’ve just checked git logs.

How did you come up with such a conclusion? Something doesn't work on

your side?

—
Denis


On Dec 10, 2016, at 5:39 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi:


IGNITE-3727,this issue has been fixed and tested in september,why did

not merge into the 1.8 version?









Re: IGNITE-3727: why did not merge into the 1.8 version?

2016-12-10 Thread

Denis,

I found  the branch 3727:

https://github.com/gridgain/apache-ignite/tree/ignite-3727-2

But it appear that the code is not merged into the master?

for example, IgniteMessagingImpl.java,the related code is still an old 
version,8 months ago.



在 2016/12/10 22:56, Denis Magda 写道:

Hi,

It was released in 1.8. I’ve just checked git logs.

How did you come up with such a conclusion? Something doesn't work on your side?

—
Denis


On Dec 10, 2016, at 5:39 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi:


IGNITE-3727,this issue has been fixed and tested in september,why did not merge 
into the 1.8 version?






IGNITE-3727: why did not merge into the 1.8 version?

2016-12-10 Thread

Hi:


IGNITE-3727,this issue has been fixed and tested in september,why did 
not merge into the 1.8 version?





Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

2016-12-10 Thread

Hi:


http://repo.maven.apache.org/maven2/org/apache/ignite

the site above, not updated?


在 2016/12/9 22:06, Sergey Kozlov 写道:

Hi

Maven repository has been released.

https://repository.apache.org/content/repositories/releases/org/apache/ignite/

On Fri, Dec 9, 2016 at 4:41 PM, 李玉珏@163 <18624049...@163.com> wrote:


maven repo is not updated?



在 2016/12/9 21:37, Ксения Рыбакова 写道:


Hi,

Update notifier for 1.7.0 shows that version is up to date. Could anybody
fix it please?

+--+

Ignite ver. 1.7.0#20160801-sha1:383273e3f6
6f702de2482466dce954d570a8ccf2
+---
---+


...

[16:32:54,180][INFO ][main][GridDiscoveryManager] Topology snapshot
[ver=1,
servers=1, clients=0, CPUs=4, heap=1.0GB]
[16:33:03,833][INFO ][ignite-update-notifier-timer][GridUpdateNotifier]
Your version is up to date.

--
Thanks,
Ksenia

On Fri, Dec 9, 2016 at 4:14 PM, Pavel Tupitsyn 
wrote:

I've updated the site, there were commented parts on Download page from

Denis, so that was easy :)
Main and News pages also updated.

Just a reminder - any committer can update the site, just modify files in
SVN, and changes will appear online:
https://svn.apache.org/repos/asf/ignite/site/trunk

On Fri, Dec 9, 2016 at 1:07 PM, Vladimir Ozerov 
wrote:

Denis,

Release has been propagated to mirrors, so you can go ahead with site
update.

Vladimir.

On Fri, Dec 9, 2016 at 1:28 AM, Denis Magda  wrote:

Great, thanks!

Released all the docs (Java, .NET, C++, etc.) and update the site
partially.

I can’t go ahead and update the downloads page [1] on the site because


the


binaries and sources haven’t been uploaded yet. I get 404 error every


time


I try to download one of the below.
http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip <
http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip>
http://apache.osuosl.org/ignite/1.8.0/apache-ignite-


fabric-1.8.0-bin.zip
<


http://apache.osuosl.org/ignite/1.8.0/apache-ignite-


fabric-1.8.0-bin.zip
http://apache.osuosl.org/ignite/1.8.0/apache-ignite-
hadoop-1.8.0-bin.zip
<


http://apache.osuosl.org/ignite/1.8.0/apache-ignite-


hadoop-1.8.0-bin.zip

Sergey K., will you handle this?

In addition, we need to update our cloud images. Nick, please dedicate
some time tomorrow for this.
https://issues.apache.org/jira/browse/IGNITE-4402 <
https://issues.apache.org/jira/browse/IGNITE-4402>

[1] https://ignite.apache.org/download.cgi <https://ignite.apache.org/
download.cgi>

—
Denis

On Dec 8, 2016, at 12:08 PM, Sergey Kozlov 
wrote:
Hi

I've completed release procedure in SVN and maven repository.

https://dist.apache.org/repos/dist/release/ignite/1.8.0/
https://svn.apache.org/repos/asf/ignite/site/trunk/releases/1.8.0/

Who could update the sites (https://ignite.apache.org and
https://apacheignite.readme.io) ?


On Thu, Dec 8, 2016 at 9:26 PM, Vladimir Ozerov <


voze...@gridgain.com>

wrote:

Igniters,

Apache Ignite 1.8.0 release (RC1) has been accepted.

11 "+1" votes received:

- Alexey Kuzentsov (binding)
- Anton Vinogradov (binding)
- Denis Magda (binding)
- Nikolai Tikhonov (binding)
- Roman Shtykh (binding)
- Sergi Vladykin (binding)
- Yakov Zhdanov (binding)
- Andrey Gura
- Pavel Tupitsyn
- Saikat Maitra
- Vladisav Jelisavcic

Vote thread:

*http://apache-ignite-developers.2346864.n4.nabble.
com/VOTE-Apache-Ignite-1-8-0-RC1-td12754.html
<http://apache-ignite-developers.2346864.n4.nabble.
com/VOTE-Apache-Ignite-1-8-0-RC1-td12754.html>*

Ignite 1.8.0 will be released soon. Woohoo!

Vladimir.



--
Sergey Kozlov
GridGain Systems
www.gridgain.com




--
Vladimir Ozerov
Senior Software Architect
GridGain Systems
www.gridgain.com
*+7 (960) 283 98 40*













Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

2016-12-09 Thread

maven repo is not updated?


在 2016/12/9 21:37, Ксения Рыбакова 写道:

Hi,

Update notifier for 1.7.0 shows that version is up to date. Could anybody
fix it please?


+--+
Ignite ver. 1.7.0#20160801-sha1:383273e3f66f702de2482466dce954d570a8ccf2
+--+

...
[16:32:54,180][INFO ][main][GridDiscoveryManager] Topology snapshot [ver=1,
servers=1, clients=0, CPUs=4, heap=1.0GB]
[16:33:03,833][INFO ][ignite-update-notifier-timer][GridUpdateNotifier]
Your version is up to date.

--
Thanks,
Ksenia

On Fri, Dec 9, 2016 at 4:14 PM, Pavel Tupitsyn  wrote:


I've updated the site, there were commented parts on Download page from
Denis, so that was easy :)
Main and News pages also updated.

Just a reminder - any committer can update the site, just modify files in
SVN, and changes will appear online:
https://svn.apache.org/repos/asf/ignite/site/trunk

On Fri, Dec 9, 2016 at 1:07 PM, Vladimir Ozerov 
wrote:


Denis,

Release has been propagated to mirrors, so you can go ahead with site
update.

Vladimir.

On Fri, Dec 9, 2016 at 1:28 AM, Denis Magda  wrote:


Great, thanks!

Released all the docs (Java, .NET, C++, etc.) and update the site
partially.

I can’t go ahead and update the downloads page [1] on the site because

the

binaries and sources haven’t been uploaded yet. I get 404 error every

time

I try to download one of the below.
http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip <
http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip>
http://apache.osuosl.org/ignite/1.8.0/apache-ignite-

fabric-1.8.0-bin.zip

<

http://apache.osuosl.org/ignite/1.8.0/apache-ignite-

fabric-1.8.0-bin.zip

http://apache.osuosl.org/ignite/1.8.0/apache-ignite-

hadoop-1.8.0-bin.zip

<

http://apache.osuosl.org/ignite/1.8.0/apache-ignite-

hadoop-1.8.0-bin.zip


Sergey K., will you handle this?

In addition, we need to update our cloud images. Nick, please dedicate
some time tomorrow for this.
https://issues.apache.org/jira/browse/IGNITE-4402 <
https://issues.apache.org/jira/browse/IGNITE-4402>

[1] https://ignite.apache.org/download.cgi 

—
Denis


On Dec 8, 2016, at 12:08 PM, Sergey Kozlov 

wrote:

Hi

I've completed release procedure in SVN and maven repository.

https://dist.apache.org/repos/dist/release/ignite/1.8.0/
https://svn.apache.org/repos/asf/ignite/site/trunk/releases/1.8.0/

Who could update the sites (https://ignite.apache.org and
https://apacheignite.readme.io) ?


On Thu, Dec 8, 2016 at 9:26 PM, Vladimir Ozerov <

voze...@gridgain.com>

wrote:


Igniters,

Apache Ignite 1.8.0 release (RC1) has been accepted.

11 "+1" votes received:

- Alexey Kuzentsov (binding)
- Anton Vinogradov (binding)
- Denis Magda (binding)
- Nikolai Tikhonov (binding)
- Roman Shtykh (binding)
- Sergi Vladykin (binding)
- Yakov Zhdanov (binding)
- Andrey Gura
- Pavel Tupitsyn
- Saikat Maitra
- Vladisav Jelisavcic

Vote thread:

*http://apache-ignite-developers.2346864.n4.nabble.
com/VOTE-Apache-Ignite-1-8-0-RC1-td12754.html
*

Ignite 1.8.0 will be released soon. Woohoo!

Vladimir.




--
Sergey Kozlov
GridGain Systems
www.gridgain.com




--
Vladimir Ozerov
Senior Software Architect
GridGain Systems
www.gridgain.com
*+7 (960) 283 98 40*









Re: New page on the website!

2016-10-30 Thread

Example part of this page, tab can not be switched,Firefox 49.


在 2016/10/29 02:28, Dmitriy Setrakyan 写道:

Thanks, Prachi! Very useful description of RDMS integration functionality
provided by the Ignite Web Console management.

On Fri, Oct 28, 2016 at 10:34 AM, Prachi Garg  wrote:


Hello Igniters,

Check out the new page on the Ignite website -
https://ignite.apache.org/features/rdbmsintegration.html to learn how
Ignite can seamlessly integrate with underlying data stores, and
automatically generate domain model POJOs as well as XML and Java
configurations.

-Prachi






Re: about isolated ignite clusters on the same set of machines

2016-09-20 Thread

Hi:

I know,thanks!


在 16/9/20 23:07, Yakov Zhdanov 写道:

This
overrides 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder#setMulticastGroup

--Yakov

2016-09-20 17:43 GMT+03:00 李玉珏@163 <18624049...@163.com>:


Hi:

what is the java api?

在 16/9/20 22:03, Yakov Zhdanov 写道:

Hi!

When I need to isolate clusters in the same network I pass
-DIGNITE_OVERRIDE_MCAST_GRP=x.x.x.x to java process starting node or
-J-DIGNITE_OVERRIDE_MCAST_GRP=x.x.x.x as ignite.sh parameter.



--Yakov

2016-09-20 16:52 GMT+03:00 李玉珏@163 <18624049...@163.com>:

Guys:

in our network, we want to isolate some of the machine to build cluster
for testing, I looked at the following document,also do the test, but
found
that this document may not be correct:

https://apacheignite.readme.io/v1.7/docs/cluster-config#isol
ated-ignite-clusters-on-the-same-set-of-machin

If the addresses property of TcpDiscoveryVmIpFinder is set to 127.0.0.1,
multiple ignite nodes started in the same machine,is the isolation of
cluster, has nothing to do with the localPort attribute, if do not set
the
addresses property, even if the localPort property of TcpDiscoverySpi and
TcpCommunicationSpi are diff, also belong to the same cluster.


The way I think is to set the IP address list for the addresses property,
but it doesn't look elegant, does anyone in the community know the right,
or elegant way?











Re: about isolated ignite clusters on the same set of machines

2016-09-20 Thread

Community,

https://apacheignite.readme.io/v1.7/docs/cluster-config#isol
ated-ignite-clusters-on-the-same-set-of-machin

|The above document should be a problem, may cause misleading to the 
developer, whether someone should fix it? In addition, can the API of 
DiscoverySpi be optimized to facilitate the support of cluster isolation 
within a network? I think this is very useful for development and testing.|


在 16/9/20 23:07, Yakov Zhdanov 写道:

This
overrides 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder#setMulticastGroup

--Yakov

2016-09-20 17:43 GMT+03:00 李玉珏@163 <18624049...@163.com>:


Hi:

what is the java api?

在 16/9/20 22:03, Yakov Zhdanov 写道:

Hi!

When I need to isolate clusters in the same network I pass
-DIGNITE_OVERRIDE_MCAST_GRP=x.x.x.x to java process starting node or
-J-DIGNITE_OVERRIDE_MCAST_GRP=x.x.x.x as ignite.sh parameter.



--Yakov

2016-09-20 16:52 GMT+03:00 李玉珏@163 <18624049...@163.com>:

Guys:

in our network, we want to isolate some of the machine to build cluster
for testing, I looked at the following document,also do the test, but
found
that this document may not be correct:

https://apacheignite.readme.io/v1.7/docs/cluster-config#isol
ated-ignite-clusters-on-the-same-set-of-machin

If the addresses property of TcpDiscoveryVmIpFinder is set to 127.0.0.1,
multiple ignite nodes started in the same machine,is the isolation of
cluster, has nothing to do with the localPort attribute, if do not set
the
addresses property, even if the localPort property of TcpDiscoverySpi and
TcpCommunicationSpi are diff, also belong to the same cluster.


The way I think is to set the IP address list for the addresses property,
but it doesn't look elegant, does anyone in the community know the right,
or elegant way?








Re: about isolated ignite clusters on the same set of machines

2016-09-20 Thread

Hi:

what is the java api?

在 16/9/20 22:03, Yakov Zhdanov 写道:

Hi!

When I need to isolate clusters in the same network I pass
-DIGNITE_OVERRIDE_MCAST_GRP=x.x.x.x to java process starting node or
-J-DIGNITE_OVERRIDE_MCAST_GRP=x.x.x.x as ignite.sh parameter.



--Yakov

2016-09-20 16:52 GMT+03:00 李玉珏@163 <18624049...@163.com>:


Guys:

in our network, we want to isolate some of the machine to build cluster
for testing, I looked at the following document,also do the test, but found
that this document may not be correct:

https://apacheignite.readme.io/v1.7/docs/cluster-config#isol
ated-ignite-clusters-on-the-same-set-of-machin

If the addresses property of TcpDiscoveryVmIpFinder is set to 127.0.0.1,
multiple ignite nodes started in the same machine,is the isolation of
cluster, has nothing to do with the localPort attribute, if do not set the
addresses property, even if the localPort property of TcpDiscoverySpi and
TcpCommunicationSpi are diff, also belong to the same cluster.


The way I think is to set the IP address list for the addresses property,
but it doesn't look elegant, does anyone in the community know the right,
or elegant way?








about isolated ignite clusters on the same set of machines

2016-09-20 Thread

Guys:

in our network, we want to isolate some of the machine to build cluster 
for testing, I looked at the following document,also do the test, but 
found that this document may not be correct:


https://apacheignite.readme.io/v1.7/docs/cluster-config#isolated-ignite-clusters-on-the-same-set-of-machin

If the addresses property of TcpDiscoveryVmIpFinder is set to 127.0.0.1, 
multiple ignite nodes started in the same machine,is the isolation of 
cluster, has nothing to do with the localPort attribute, if do not set 
the addresses property, even if the localPort property of 
TcpDiscoverySpi and TcpCommunicationSpi are diff, also belong to the 
same cluster.



The way I think is to set the IP address list for the addresses 
property, but it doesn't look elegant, does anyone in the community know 
the right, or elegant way?





Re: Maintaining documentation consistency on readme.io

2016-09-03 Thread

Prachi:

https://apacheignite.readme.io/v1.6/docs/aop-based-grid-enabling

this doc is missing in the 1.7 version.


在 16/8/26 02:50, Prachi Garg 写道:

Right!


On Thu, Aug 25, 2016 at 10:28 AM, Dmitriy Setrakyan 
wrote:


Got it. So essentially you are proposing to make the changes for the
existing version, but hide the new pages, until the next version is
released, right?

On Thu, Aug 25, 2016 at 10:24 AM, Prachi Garg  wrote:


Changes to the existing pages will still have to be copied manually; but
since we are not maintaining two versions (current and future) at the

same

time, it may be a lesser overhead. Once a new version is released, we
hardly go back to the previous versions to fix anything.

-P

On Wed, Aug 24, 2016 at 9:42 PM, Dmitriy Setrakyan <

dsetrak...@apache.org>

wrote:


Prarchi, great idea. We should follow it.

However, this addresses only new content. What about changes to the
existing pages?

D.

On Wed, Aug 24, 2016 at 5:15 PM, Denis Magda 

wrote:

Prachi,

This is an excellent idea!

Would you mind adding a new page to this [1] section?

After the page is ready we also need to leave a reference to it under

this

[2] section.

[1] https://cwiki.apache.org/confluence/display/IGNITE/

Development+Process



[2] https://cwiki.apache.org/confluence/display/IGNITE/How+
to+Contribute#HowtoContribute-Documentation&examples <
https://cwiki.apache.org/confluence/display/IGNITE/How+
to+Contribute#HowtoContribute-Documentation&examples>

—
Denis


On Aug 24, 2016, at 10:58 AM, Prachi Garg 

wrote:

Igniters,

Since readme.io does not automatically copy the changes from the

current

version to the subsequent version, I have the following suggestion:

Create the document for future releases within the document for the

current

version, and keep the pages hidden. After the new release, create

the

new

version for the document and unhide the pages.

This way we don't have to manually copy the document between the

two

versions.

Thoughts?

-Prachi







about ComputeJob's capacity planning

2016-08-24 Thread

Igniters:


how to estimate the ComputeJob capacity planning?
In our business, in accordance with the present calculation rules, may 
produce up to 30 million ComputeJobs, so it is easy to cause out of 
memory, then in the end how much memory is reasonable?





about ignite.messge() async mode

2016-08-18 Thread

Hi;


ignite.message() method cannot work in async mode,withAsync() method is 
invalid,is it ok or is a bug?





Re: [RESULT] [VOTE] Apache Ignite 1.7.0 Release (RC1)

2016-08-05 Thread

http://ignite.apache.org/download.cgi#binaries

Date is wrong。


在 16/8/6 03:10, Pavel Tupitsyn 写道:

Sergey, it does, as I said in my email. Please recheck.

https://apacheignite-cpp.readme.io/ and https://apacheignite-net.readme.io/
also point to 1.7.

On Fri, Aug 5, 2016 at 10:04 PM, Sergey Kozlov  wrote:


Also apacheignite.readme.io should points out on 1.7.0

On Fri, Aug 5, 2016 at 7:37 PM, Alexey Kuznetsov 
wrote:


As far as I remember we also should update version in master to next
version. 1.8 I think.

5 Авг 2016 г. 23:23 пользователь "Pavel Tupitsyn" 
написал:


Ignite 1.7.0 successfully released to

https://dist.apache.org/repos/dist/release/ignite/1.7.0/

Maven repository, NuGet, ignite.apache.org site, readme.io pages also
updated.

On Fri, Aug 5, 2016 at 6:22 PM, Pavel Tupitsyn 
wrote:


Hello!

Apache Ignite 1.7.0 release (RC1) has been accepted.

7 "+1" votes received.

Here are the votes received:

- Vladimir Ozerov (binding)
- Nikolay Tikhonov (binding)
- Sergi Vladykin (binding)
- Denis Magda (binding)
- Valentin Kulichenko (binding)
- Alexey Kuznetsov
- Andrey Novikov

Here is the link to vote thread -
http://apache-ignite-developers.2346864.n4.nabble.
com/VOTE-Apache-Ignite-1-7-0-RC1-td10333.html

Ignite 1.7.0 will be released soon.

Thanks!

Pavel.




--
Sergey Kozlov
GridGain Systems
www.gridgain.com






Re: Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties

2016-05-26 Thread
The official release of the binary package and maven dependency is no 
problem.

Your maven dependent version is not correct.

you can look at:

http://repo1.maven.org/maven2/org/apache/ignite/ignite-indexing/1.6.0/ignite-indexing-1.6.0.pom

com.h2databaseh21.3.175compile

在 16/5/26 16:55, Ken Cheng 写道:

Hi All,

I ran into above issue. here is the error stack


Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:1487)
~[ignite-indexing-1.6.0.jar:1.6.0]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:171)
~[ignite-core-1.6.0.jar:1.6.0]
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1549)
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:869)
~[ignite-core-1.6.0.jar:1.6.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1736)
~[ignite-core-1.6.0.jar:1.6.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:549)
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
~[ignite-spring-1.6.0.jar:1.6.0]
at
org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
~[ignite-spring-1.6.0.jar:1.6.0]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
... 21 common frames omitted
Caused by: java.lang.ClassNotFoundException: org.h2.constant.SysProperties
at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[na:1.8.0_77]
at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_77]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
~[na:1.8.0_77]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_77]


I am using v1.6.0


 org.apache.ignite
 ignite-core
 ${ignite.version}


 org.apache.ignite
 ignite-spring
 ${ignite.version}


 org.apache.ignite
 ignite-indexing
 ${ignite.version}



below is the dependency tree

[INFO] +- org.apache.ignite:ignite-core:jar:1.6.0:compile
[INFO] |  +- javax.cache:cache-api:jar:1.0.0:compile
[INFO] |  \- org.gridgain:ignite-shmem:jar:1.0.0:compile
[INFO] +- org.apache.ignite:ignite-spring:jar:1.6.0:compile
[INFO] |  +- org.springframework:spring-core:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-aop:jar:4.2.6.RELEASE:compile
[INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
[INFO] |  +- org.springframework:spring-beans:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-context:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-expression:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-tx:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-jdbc:jar:4.2.6.RELEASE:compile
[INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \- org.apache.ignite:ignite-indexing:jar:1.6.0:compile
[INFO]+- commons-codec:commons-codec:jar:1.6:compile
[INFO]+- org.apache.lucene:lucene-core:jar:3.5.0:compile
[INFO]\- com.h2database:h2:jar:1.4.191:compile





I check there is no* org/h2/constant/SysProperties, on the contrary *
*there is *org.h2.engine.SysProperties


Seems it's a bug? if so, I am going log a jira.



Thanks,
kcheng






Re: Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties

2016-05-26 Thread

Ignite, may only use the 1.3.175 version of H2 database.


在 16/5/26 16:55, Ken Cheng 写道:

Hi All,

I ran into above issue. here is the error stack


Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:1487)
~[ignite-indexing-1.6.0.jar:1.6.0]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:171)
~[ignite-core-1.6.0.jar:1.6.0]
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1549)
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:869)
~[ignite-core-1.6.0.jar:1.6.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1736)
~[ignite-core-1.6.0.jar:1.6.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:549)
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
~[ignite-spring-1.6.0.jar:1.6.0]
at
org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
~[ignite-spring-1.6.0.jar:1.6.0]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
... 21 common frames omitted
Caused by: java.lang.ClassNotFoundException: org.h2.constant.SysProperties
at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[na:1.8.0_77]
at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_77]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
~[na:1.8.0_77]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_77]


I am using v1.6.0


 org.apache.ignite
 ignite-core
 ${ignite.version}


 org.apache.ignite
 ignite-spring
 ${ignite.version}


 org.apache.ignite
 ignite-indexing
 ${ignite.version}



below is the dependency tree

[INFO] +- org.apache.ignite:ignite-core:jar:1.6.0:compile
[INFO] |  +- javax.cache:cache-api:jar:1.0.0:compile
[INFO] |  \- org.gridgain:ignite-shmem:jar:1.0.0:compile
[INFO] +- org.apache.ignite:ignite-spring:jar:1.6.0:compile
[INFO] |  +- org.springframework:spring-core:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-aop:jar:4.2.6.RELEASE:compile
[INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
[INFO] |  +- org.springframework:spring-beans:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-context:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-expression:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-tx:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-jdbc:jar:4.2.6.RELEASE:compile
[INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \- org.apache.ignite:ignite-indexing:jar:1.6.0:compile
[INFO]+- commons-codec:commons-codec:jar:1.6:compile
[INFO]+- org.apache.lucene:lucene-core:jar:3.5.0:compile
[INFO]\- com.h2database:h2:jar:1.4.191:compile





I check there is no* org/h2/constant/SysProperties, on the contrary *
*there is *org.h2.engine.SysProperties


Seems it's a bug? if so, I am going log a jira.



Thanks,
kcheng






About web console and web agent

2016-05-24 Thread

Hi:

I would like to ask, Web Console and Web Agent module,how to 
install,config and use? Are the documents related is OK?



在 16/5/18 00:23, Alexey Kuznetsov 写道:

First version of Web Console merged to ignite-1.6.

On Tue, May 17, 2016 at 9:31 PM, Pavel Tupitsyn 
wrote:


All done from .NET side as well.

On Tue, May 17, 2016 at 5:28 PM, Denis Magda  wrote:


Hi,

Reviewed and merged IGNITE-2394 (Cache loading from storage is called on
client nodes).
Finalized and merged IGNITE-3098 (UTF-16 surrogate pairs are not properly
serialized by BinaryMarshaller).

These are last things from my side for 1.6.

—
Denis


On May 17, 2016, at 11:09 AM, Pavel Tupitsyn 

wrote:

Hi,

Please note that documentation tickets do not hold the release

(IGNITE-3101

and subtasks).
Other than that, in .NET, recently emerged 'IGNITE-3139 UTF surrogates'

is

expected to be merged today.

Pavel.


On Tue, May 17, 2016 at 10:20 AM, Semyon Boikov 
wrote:


In 1.6 we implemented 'late affinity assignment' mode (see
https://issues.apache.org/jira/browse/IGNITE-324 and
IgniteConfiguration.isLateAffinityAssignment)

On Mon, May 16, 2016 at 7:03 PM, Alexey Kuznetsov <

akuznet...@gridgain.com

wrote:


https://issues.apache.org/jira/browse/IGNITE-2832
"CacheJdbcPojoStoreFactory.dataSource property should be replaced

with

Factory"
Reviewed by Semen and merged into ignite-1.6


On Mon, May 16, 2016 at 10:56 PM, Igor Sapego 
wrote:


Hi, here is a list of major C++ features included in 1.6:

* ODBC driver for Ignite (IGNITE-1786)
* Transactions API for CPP client (IGNITE-2805)
* Simplified Autotools build process (IGNITE-2823)
* Date and Timestamp types implementation (IGNITE-)

Best Regards,
Igor

On Fri, May 13, 2016 at 4:10 PM, Artem Shutak 
I've finished with IGNITE-2959 Ignite JTA and WebSphere Application

Server

8.5.5  and has

been

merged to 1.6.

Also, I'm going to finish the following issues before 1.6 relase

(they

all

almost done/under review/waiting for TC):
[1] IGNITE-3056 Service implementation class is required even if

it's

not

expected to be deployed on current node

[2] IGNITE-2921 ScanQueries over local partitions are not optimal

[3] IGNITE-2899 BinaryObject is deserialized before getting passed

to

CacheInterceptor <

https://issues.apache.org/jira/browse/IGNITE-2899>

Thanks,
-- Artem --

On Fri, May 13, 2016 at 5:26 AM, Dmitriy Setrakyan <

dsetrak...@apache.org>

wrote:


On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov <

akuznet...@gridgain.com

wrote:


Also I already implemented "CacheJdbcPojoStoreFactory.dataSource

property

should be replaced with Factory"
https://issues.apache.org/jira/browse/IGNITE-2832

And I think it will be cool to merge into ignite-1.6
But I need a review.

Val, could you take a look? You may compare branch ignite-2832

with

master.
To my knowledge, Val is traveling this weekend, so it would be

nice

if

someone else could pick it up.



On Thu, May 12, 2016 at 10:26 PM, Alexey Kuznetsov <
akuznet...@gridgain.com>
wrote:


I'm going to merge Ignite Web Console into ignite-1.6

https://issues.apache.org/jira/browse/IGNITE-843

On Thu, May 12, 2016 at 9:30 PM, Igor Sapego <

isap...@gridgain.com

wrote:

There is one more C++ ticket I'd like to be included in 1.6 -

IGNITE-3113

[1].

[1] - https://issues.apache.org/jira/browse/IGNITE-3113

Best Regards,
Igor

On Thu, May 12, 2016 at 3:44 PM, Pavel Tupitsyn <

ptupit...@gridgain.com

wrote:


And one more .NET ticket: IGNITE-3118 .NET:
CacheConfiguration.EvictionPolicy

On Thu, May 12, 2016 at 12:20 PM, Denis Magda <

dma...@gridgain.com>

wrote:

Yakov,

Processed all the tickets mentioned in 1. The only one is

left

is

the

following
https://issues.apache.org/jira/browse/IGNITE-2954 <
https://issues.apache.org/jira/browse/IGNITE-2954>

Alex G. I do remember you’ve fixed IGNITE-2954 before.

Have

you

merged it

into the master? Is the fix in ignite-1.6 already?

—
Denis


On May 11, 2016, at 8:56 AM, Yakov Zhdanov <

yzhda...@apache.org

wrote:

Guys,

I moved most of the tickets to 1.7 version.

I had to leave the following tickets untouched (~80

tickets):

1. labeled with - community important performance

customer -

Denis,

Vladimir and Val can you please review these tickets and

move

non-urgent

ones. You can use query below
2. with status "in progress". Please everyone having

such

tickets

move

it

yourself or finish it in 1.6
3. with status "patch available". Committers, please

split

the

reviews

and

let's include checked/tested fixes to 1.6. Others should

be

moved.

Sam, can you please review and merge -
https://issues.apache.org/jira/browse/IGNITE-2744 -

Optimize

"unwindEvict"

call in GridCacheIoManager.processMessage().


Query for p1:

project = IGNITE AND fixVersion = 1.6 AND resolution

Re: About https://apacheignite-fs.readme.io/docs

2016-04-07 Thread

Hi:

From the backup,Spark, Hadoop and other related content, the backup 
date is 9 months ago, such as 
https://github.com/apacheignite/documentation/tree/v1.5/distributed-file-system.

This part of the document, there is no update in the near future?

Https://apacheignite.readme.io/docs
From this site, I found a lot of content has been modified.

在 16/4/7 17:00, Dmitriy Setrakyan 写道:

Sorry for the late reply.

Yes, this should be the latest copy for the Ignite 1.5 and should contain
all the updates. It also has v. 1.6 which is the documentation for the
upcoming version.

D.

On Fri, Mar 25, 2016 at 5:40 AM, 李玉珏@163 <18624049...@163.com> wrote:


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

In this site, and IGFS, Hadoop, Spark related content and no backup?
I'd like to have a copy of the latest online document. I want to make a
chinese document synchronization.
If don't have this backup, I don't know what the content has been modified.


在 16/3/25 03:16, Dmitriy Setrakyan 写道:

Hi,

I think you are right, the content is similar. The only change is that it
was separated from the main documentation.

D.

On Thu, Mar 24, 2016 at 5:12 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi:

https://apacheignite-fs.readme.io/docs
This site has a similar
https://github.com/apacheignite/documentation/tree/v1.5 such backup?

If not, is there anyone in the community can help me to get a copy of
this
document from readme.io and send it to my mailbox?
I want to make a synchronization between the chinese manual and the 1.5
edition of the latest.

thanks!











Re: About https://apacheignite-fs.readme.io/docs

2016-03-25 Thread

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

In this site, and IGFS, Hadoop, Spark related content and no backup?
I'd like to have a copy of the latest online document. I want to make a chinese 
document synchronization.
If don't have this backup, I don't know what the content has been modified.


在 16/3/25 03:16, Dmitriy Setrakyan 写道:

Hi,

I think you are right, the content is similar. The only change is that it
was separated from the main documentation.

D.

On Thu, Mar 24, 2016 at 5:12 AM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

https://apacheignite-fs.readme.io/docs
This site has a similar
https://github.com/apacheignite/documentation/tree/v1.5 such backup?

If not, is there anyone in the community can help me to get a copy of this
document from readme.io and send it to my mailbox?
I want to make a synchronization between the chinese manual and the 1.5
edition of the latest.

thanks!








About https://apacheignite-fs.readme.io/docs

2016-03-24 Thread

Hi:

https://apacheignite-fs.readme.io/docs
This site has a similar 
https://github.com/apacheignite/documentation/tree/v1.5 such backup?


If not, is there anyone in the community can help me to get a copy of 
this document from readme.io and send it to my mailbox?
I want to make a synchronization between the chinese manual and the 1.5 
edition of the latest.


thanks!




Re: Great blog about Ignite!

2016-03-10 Thread

yes.

My chinese blog address is: my.oschina.net/liyuj/blog.
About Ignite, the address is: 
http://my.oschina.net/liyuj/blog?catalog=3378059.


Mostly translation, including Roman's blog, my own writing, up to now, 
only two articles.


All the articles have a corresponding in 
https://www.zybuluo.com/liyuj/note/230739, but the content is slightly 
different.


在 16/3/10 04:16, Dmitriy Setrakyan 写道:

On Wed, Mar 9, 2016 at 3:43 AM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

If I write the content will be released to:
Https://www.zybuluo.com/liyuj/note/230739


Is your blog in Chinese? If yes, then I doubt we can help promote it.
However, I believe that you can post it to any developer hubs in China.

Did you already write the blog or planning to write one?\




I say "authority", mainly refers to the relevant content, if written by
the designer, will be more depth.



在 16/3/9 11:16, Dmitriy Setrakyan 写道:

On Thu, Mar 3, 2016 at 11:45 PM, 李玉珏@163 <18624049...@163.com> wrote:

I wrote some, but it was not deep enough, and the authority was not

enough.

I think we should still publish it. Can you explain what you meant by the

“authority”?


在 16/3/4 09:39, Dmitriy Setrakyan 写道:

Couldn’t agree more. It will be great if more community members would


volunteer to write blogs or articles.











Re: new blogs added to Ignite News section

2016-03-10 Thread

I will sort out the related content, and then translate it into chinese.

在 16/3/10 06:18, Dmitriy Setrakyan 写道:

Igniters,

The latest blogs were added to the Ignite website news section:

https://ignite.apache.org/
https://ignite.apache.org/news.html

Thanks to Roman Shtykh and Shamim Bhuiyan for contributing.

Blogs about Ignite go a long way towards improving adoption and awareness
about our project. I would like to encourage all community members to blog
more.

Thanks,
D.






Re: About Infinispan

2016-03-10 Thread

From the functionality, I just feel that the two are comparable.
From the point of view of publicity can strengthen the advantages of 
Ignite, such as ANSI SQL Query IGFS, and so on.


在 16/3/10 20:41, Yakov Zhdanov 写道:

Hello!

I am afraid I don't fully understand you. Can you please explain what you
suggest in other words? Are you talking about benchmarks for comparison?

--Yakov

2016-03-10 18:38 GMT+06:00 李玉珏@163 <18624049...@163.com>:


Hi,

Can community for Infinispan and Ignite in function to make a contrast?
Like Redis, Gemfire, Hazelcast, Coherence?







About Infinispan

2016-03-10 Thread

Hi,

Can community for Infinispan and Ignite in function to make a contrast? 
Like Redis, Gemfire, Hazelcast, Coherence?




Re: Great blog about Ignite!

2016-03-09 Thread

Hi:

If I write the content will be released to:
Https://www.zybuluo.com/liyuj/note/230739

I say "authority", mainly refers to the relevant content, if written by 
the designer, will be more depth.


在 16/3/9 11:16, Dmitriy Setrakyan 写道:

On Thu, Mar 3, 2016 at 11:45 PM, 李玉珏@163 <18624049...@163.com> wrote:


I wrote some, but it was not deep enough, and the authority was not enough.


I think we should still publish it. Can you explain what you meant by the
“authority”?



在 16/3/4 09:39, Dmitriy Setrakyan 写道:

Couldn’t agree more. It will be great if more community members would

volunteer to write blogs or articles.









Re: readme.io (again)

2016-03-08 Thread

Hi:

https://apacheignite-fs.readme.io/docs
The above content is not synchronized?

在 16/3/8 10:43, Dmitriy Setrakyan 写道:

Cos, the readme team facilitates export to GIT (upon our request):
https://github.com/apacheignite/documentation

What would be the next step?

D





Re: Great blog about Ignite!

2016-03-03 Thread

I wrote some, but it was not deep enough, and the authority was not enough.

在 16/3/4 09:39, Dmitriy Setrakyan 写道:

Couldn’t agree more. It will be great if more community members would
volunteer to write blogs or articles.





Re: Great blog about Ignite!

2016-03-03 Thread

Hi:

Very good, I hope this article can more!

Srini Penchikala wrote a series of articles on the InfoQ are as follows:
Http://www.infoq.com/articles/apache-spark-introduction
Http://www.infoq.com/articles/apache-spark-sql
Http://www.infoq.com/articles/apache-spark-streaming

If the Ignite community core members, can also write this article, and 
then published in the influential technology website, will be a very 
good thing.


在 16/3/4 05:35, Dmitriy Setrakyan 写道:

https://dzone.com/articles/linking-apache-ignite-and-apache-kafka-for-highly

Roman, thanks for putting it together!

D.






Re: streamer documentation

2016-02-23 Thread

chinese version updated.

在 16/2/22 04:46, Raul Kripalani 写道:

Done. Cheers.

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
Blog: raul.io | twitter: @raulvk 

On Thu, Feb 11, 2016 at 6:31 AM, Denis Magda  wrote:


Thanks Raul!

Please don't forget to add the doc to both 1.5 and 1.6 [1], that has been
recently created.

[1] https://apacheignite.readme.io/v1.6

--
Denis


On 2/11/2016 1:34 AM, Raul Kripalani wrote:


Hey guys,

I'll take care of Camel and MQTT this week(end).

Thanks for the patience.

Cheers,
Raúl.

On Tue, 2 Feb 2016 08:49 Denis Magda  wrote:

Dmitriy,

Raul contributed both Camel and MQTT.
Twitter streamer was implemented by Lalit Kumar Jha.

Actually I tried reach out both Raul and Lalit Kumar Jha earlier
regarding this topic but seems that they were too busy because I didn't
get any response from them.

Raul, Lalit Kumar Jha, do you have time to add the documentation or
someone else from the community should take care of this?

Regards,
Denis

On 2/2/2016 11:42 AM, Dmitriy Setrakyan wrote:


Denis,

Is there any chance you can mention the names of the contributors, so we
could reach out to them personally and ask for help with the


documentation?


I know that Camel streamer was done by Raul, but not sure about the
other
two.

D.

On Tue, Feb 2, 2016 at 12:37 AM, Denis Magda 


wrote:


The tickets are already there

Twitter: https://issues.apache.org/jira/browse/IGNITE-2413
MQTT: https://issues.apache.org/jira/browse/IGNITE-2411
Camel: https://issues.apache.org/jira/browse/IGNITE-2530

It would be perfect if Igniters who contributed this functionality will
add the documentation as well.

--
Denis


On 2/2/2016 11:31 AM, Dmitriy Setrakyan wrote:

Igniters,

I have been trying to find documentation for the following streamers


but

couldn’t:

- Camel
- MQTT
- Twitter

Can I ask the contributors to document these features on readme?

Thanks,
D.








Re: About issue 1661

2016-02-18 Thread

Hi:

Thanks!

在 16/2/18 06:29, Dmitriy Setrakyan 写道:

I linked IGNITE-2610 and IGNITE-1661 in Jira. Let’s process them together.

On Wed, Feb 17, 2016 at 12:58 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:


Yes, from the description it looks related to IGNITE-2610. I will check the
test attached to the IGNITE-1661 once I finish the fix for IGNITE-2610.






About issue-1661

2016-02-17 Thread

Hi:

https://issues.apache.org/jira/browse/IGNITE-1661?filter=-2.

The issue is china's developer found, but the community has no feedback.
Today, the issue reporter asked me, but I can't answer.
I would like to ask, does anyone know what the issue is? Are developers 
using incorrect? If it is bug, when can fix it?




About issue 1661

2016-02-17 Thread

Hi:

https://issues.apache.org/jira/browse/IGNITE-1661?filter=-2.

The issue is china's developer found, but the community has no feedback.
Today, the issue reporter asked me, but I can't answer.
I would like to ask, does anyone know what the issue is? Are developers 
using incorrect? If it is bug, when can fix it?




Re: about AOP development

2016-02-03 Thread

Hi:

I found the ignite-aop module on github, and I asked what the module is 
to do?

In addition, this module does not have a document.

在 16/1/21 19:40, Vladimir Ershov 写道:

Hi,

Yes, sure, I can take a look. Just send me, please, your full logs with
exception, and describe how exactly you reproduce it (how many nodes
started, which one is client and etc.).

Thanks!

On Thu, Jan 21, 2016 at 9:43 AM, 李玉珏 <18624049...@163.com> wrote:


Hi:

I understand your approach, it should be feasible, but not very elegant.
If use ProxyFactory in spring. At runtime dynamically add interceptor,
can solve the problem, but performance will influence.

I switched to a different way of writing, using the Service mechanism,
code has been updated to GitHub, throws NullException. I survey the
reason, the problem is in service deployment process of marshal and
unmarshal stage, because of AdvisedSupport's methodCache is transient,
this may be a compatibility problem, also asks you to look at.


Sent from Mail Master


On 2016-01-20 22:20 , Vladimir Ershov  Wrote:

As for the last step, let me correct myself:

3. Start server Ignite node from spring context *AND *put spring jars
inside classpath in *.sh file. Be sure, that both nodes are using the same
xml context.

On Wed, Jan 20, 2016 at 5:07 PM, Vladimir Ershov 
wrote:


Hi!

I've checked your code and spot an issue. The root cause, is using of
Autowired annotation, since it cause bean to be serialized on a client
side, and that leads ClassNotFoundException on the server side during

bean

deserialization, since server was started from *.sh, without necessary
spring jars in the classpath.

Good news here, that it could be fixed easily with those steps:

1. Remove Autowired from transferred entities as ComputeGridJob
2. When you need an applicationContext, use
@SpringApplicationContextResource annotation.  You are need to use it

in

your ComputeGridTask.
3. Start server Ignite node from spring context, or put spring jars
inside classpath in *.sh file.

Also, you can simplify your solution for ComputeGridService by using
@ServiceResource. Take a look:
https://apacheignite.readme.io/docs/service-example

Thanks!

On Wed, Jan 20, 2016 at 6:07 AM, 李玉珏 <18624049...@163.com> wrote:


Hi:
The relevant code on the GitHub, the address is:
https://github.com/liyuj/computegrid


Sent from Mail Master



On 2016-01-20 04:32 , Dmitriy Setrakyan Wrote:

The list does not support attachments. You can use pastebin [1] or gist
[2]
to paste your code and send the link here.

[1] http://pastebin.com/
[2] https://gist.github.com/

D.

On Tue, Jan 19, 2016 at 4:48 AM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

I had just sent the code to the list.

在 16/1/19 20:39, Denis Magda 写道:

Seems that peerClassLoading doesn't work for your case. Please share

the

source code of your example.

--
Denis

On 1/18/2016 3:48 PM, 李玉珏@163 wrote:


Hi:

I have already opened the peerClassLoading.
My practice is in eclipse create a java project, developed a
ComputeTaskSplitAdapter examples, then in the ComputeJobAdapter

call

configured spring interceptors service. This example in eclipse

operation

is no problem.

But if I open a node in the command line by ignite.sh, it will

prompt

the following error in the command line.

In the default configuration file of ignite, the same configuration

of

the peerClassLoading=true.

在 16/1/18 19:39, Yakov Zhdanov 写道:


Can you please try enabling "peerClassLoading" and share the

results

here?

--Yakov

2016-01-16 12:09 GMT+03:00 李玉珏@163 <18624049...@163.com>:

Hi:

In a distributed environment, if use the spring AOP programming,
generated
a class of byte code enhancement, then the error will be reported

as

follows:

java.lang.ClassNotFoundException:


demo.computegrid.ComputeGridService$$EnhancerBySpringCGLIB$$7b44b192

This error I understand, this class does not exist on the remote

node.

But the question is, is it a technical limitation of Ignite, or

is

it

the
way I use it,or is it a bug?

I opened the peer class loading , the normal deployment I did not

test,

but I estimate it will be the same error.











来自 *网易**手机号码邮箱* -- 手机号码就是邮箱帐号,了解详情> <http://shouji.163.com>






Re: Re: Ignite Readme.IO UX issue

2016-01-28 Thread
Hi

The following address:
https://github.com/apacheignite/documentation/tree/v1.5
The git commit comment that "automatic commit from readme", I think 
readme.io with automatic backup function, and before this content is 
always updated, but  recent canot synchronize with the online version.
I logged in readme.io and also did not find automatic backup related 
settings, only the export function, I do not know how this is going on.

If do not have this backup, if I can get the export file from the 
community when the new version is released, there is no problem.


Sent from Mail Master



On 2016-01-29 07:33 , Dmitriy Setrakyan Wrote:

Hi Yujie Li,

Can you please suggest what official github backup function you would like
us to enable? I can’t find anything directly in Github, other than just a
zip download.

Thanks,
D.

On Wed, Jan 27, 2016 at 4:05 AM, 李玉珏@163 <18624049...@163.com> wrote:

> Hi:
>
> I have seen the changes in the document. I also found that part of the
> DataGrid has added a new section called "Lock".
> I maintain manual approach is, first from github document backup find
> changes, then according to the change point to find the online version of
> the difference and according to the online version do translation to ensure
> document consistency, because I know there is a part of the document is not
> open.
> So, I would like to have the official github backup function, otherwise I
> can't know what parts of the document have changed.
>
> 在 16/1/27 11:11, Dmitriy Setrakyan 写道:
>
> The version that corresponds to the documentation translated in Chinese is
>> 1.5.0-b1:
>> https://apacheignite.readme.io/v1.5-b1
>>
>> The new v.1.5 contains mainly the following changes:
>> - Hadoop and Spark were moved to a separate space:
>> https://apacheignite-fs.readme.io/docs
>> - Every category has an overview session now, e.g. Clustering, Data
>> Structures, etc.
>>
>> You should be able to compare the GIT repos to apply the changes. Let me
>> know if you have more questions.
>>
>> D.
>>
>> On Tue, Jan 26, 2016 at 4:13 AM, 李玉珏@163 <18624049...@163.com> wrote:
>>
>> Hi:
>>>
>>> I found that there was update on the online manual, but the GitHub backup
>>> is not updated.What is the reason?
>>>
>>> Https://github.com/apacheignite/documentation/tree/v1.5
>>>
>>> I was through the GitHub document to update the Chinese version of the
>>> document, if you do not have this backup, I can not know that the
>>> document
>>> has been adjusted.
>>>
>>> 在 16/1/26 01:28, Dmitriy Setrakyan 写道:
>>>
>>> Hadoop/IGFS documentation is being refactored right now. Could be a side
>>>
>>>> effect of what you were observing.
>>>>
>>>> Btw, everyone with login to readme can file a support issue. However, I
>>>> would not do it yet, while Prachi is still working on refactoring.
>>>>
>>>> D.
>>>>
>>>> On Mon, Jan 25, 2016 at 6:51 AM, Alexey Kuznetsov <
>>>> akuznet...@gridgain.com>
>>>> wrote:
>>>>
>>>> Hi!
>>>>
>>>>> Does someone knows it is possible or not to "sync" left pane with
>>>>> documentation categories and right pane with content of some selected
>>>>> category?
>>>>>
>>>>> For example: https://apacheignite.readme.io/docs/igfs
>>>>>
>>>>> I see some IGFS documentation, but on the left pane I do not see
>>>>> selected
>>>>> category "IGFS", I need to scroll down. This is very annoying when you
>>>>> are
>>>>> reading several related topics - you need to scroll every time.
>>>>>
>>>>> As I know readme.io is a kind of CMS, so who knows how to open an
>>>>> issue
>>>>> for
>>>>> them?
>>>>> Do they have any kind of JIRA / mail list / support forum?
>>>>>
>>>>> --
>>>>> Alexey Kuznetsov
>>>>> GridGain Systems
>>>>> www.gridgain.com
>>>>>
>>>>>
>>>>>
>>>
>
>


Re: Ignite Readme.IO UX issue

2016-01-27 Thread

Hi:

I have seen the changes in the document. I also found that part of the 
DataGrid has added a new section called "Lock".
I maintain manual approach is, first from github document backup find 
changes, then according to the change point to find the online version 
of the difference and according to the online version do translation to 
ensure document consistency, because I know there is a part of the 
document is not open.
So, I would like to have the official github backup function, otherwise 
I can't know what parts of the document have changed.


在 16/1/27 11:11, Dmitriy Setrakyan 写道:

The version that corresponds to the documentation translated in Chinese is
1.5.0-b1:
https://apacheignite.readme.io/v1.5-b1

The new v.1.5 contains mainly the following changes:
- Hadoop and Spark were moved to a separate space:
https://apacheignite-fs.readme.io/docs
- Every category has an overview session now, e.g. Clustering, Data
Structures, etc.

You should be able to compare the GIT repos to apply the changes. Let me
know if you have more questions.

D.

On Tue, Jan 26, 2016 at 4:13 AM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

I found that there was update on the online manual, but the GitHub backup
is not updated.What is the reason?

Https://github.com/apacheignite/documentation/tree/v1.5

I was through the GitHub document to update the Chinese version of the
document, if you do not have this backup, I can not know that the document
has been adjusted.

在 16/1/26 01:28, Dmitriy Setrakyan 写道:

Hadoop/IGFS documentation is being refactored right now. Could be a side

effect of what you were observing.

Btw, everyone with login to readme can file a support issue. However, I
would not do it yet, while Prachi is still working on refactoring.

D.

On Mon, Jan 25, 2016 at 6:51 AM, Alexey Kuznetsov <
akuznet...@gridgain.com>
wrote:

Hi!

Does someone knows it is possible or not to "sync" left pane with
documentation categories and right pane with content of some selected
category?

For example: https://apacheignite.readme.io/docs/igfs

I see some IGFS documentation, but on the left pane I do not see selected
category "IGFS", I need to scroll down. This is very annoying when you
are
reading several related topics - you need to scroll every time.

As I know readme.io is a kind of CMS, so who knows how to open an issue
for
them?
Do they have any kind of JIRA / mail list / support forum?

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com









Re: 回复: Re: about CacheTypeMetadata

2016-01-26 Thread

Hi:

chinese version updated.

在 16/1/26 20:29, Denis Magda 写道:

Hi,

Fixed.

--
Denis

On 1/26/2016 3:02 PM, 李玉珏@163 wrote:

Hi:

Address is :https://apacheignite.readme.io/docs/cache-queries
At the bottom of this page。

在 16/1/21 17:01, Denis Magda 写道:
I've doubled checked both the pages and didn't find any usage of 
CacheTypeMetadata in Java code.


Please point out to a particular document and the code.


On 1/21/2016 11:55 AM, 李玉珏 wrote:

Hi:

On the sample code, you only modify the XML part, the Java code 
section is not modified, omitted.


Sent from Mail Master


在2016年01月20日 17:41 ,Denis Magda <mailto:dma...@gridgain.com>写 
道:


Updated the docs. Thanks for pointing out.

On 1/16/2016 12:19 PM, 李玉珏@163 wrote:
> Hi:
>
> In the 1.5.0 version, I found that CacheTypeMetadata was
abandoned and
> replaced by QueryEntity.
>
> I find that two classes of related instructions exist in the
manual:
> https://apacheignite.readme.io/docs/sql-queries
> https://apacheignite.readme.io/docs/cache-queries
>
> I suggest deleting the instructions and sample code for
> CacheTypeMetadata, so as not to confuse the developer,
> CacheTypeMetadata only exists for the sake of backward
compatibility.
>
















Re: Ignite Readme.IO UX issue

2016-01-26 Thread

Hi:

I found that there was update on the online manual, but the GitHub 
backup is not updated.What is the reason?


Https://github.com/apacheignite/documentation/tree/v1.5

I was through the GitHub document to update the Chinese version of the 
document, if you do not have this backup, I can not know that the 
document has been adjusted.


在 16/1/26 01:28, Dmitriy Setrakyan 写道:

Hadoop/IGFS documentation is being refactored right now. Could be a side
effect of what you were observing.

Btw, everyone with login to readme can file a support issue. However, I
would not do it yet, while Prachi is still working on refactoring.

D.

On Mon, Jan 25, 2016 at 6:51 AM, Alexey Kuznetsov 
wrote:


Hi!

Does someone knows it is possible or not to "sync" left pane with
documentation categories and right pane with content of some selected
category?

For example: https://apacheignite.readme.io/docs/igfs

I see some IGFS documentation, but on the left pane I do not see selected
category "IGFS", I need to scroll down. This is very annoying when you are
reading several related topics - you need to scroll every time.

As I know readme.io is a kind of CMS, so who knows how to open an issue
for
them?
Do they have any kind of JIRA / mail list / support forum?

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com






Re: 回复: Re: about CacheTypeMetadata

2016-01-26 Thread

Hi:

Address is :https://apacheignite.readme.io/docs/cache-queries
At the bottom of this page。

在 16/1/21 17:01, Denis Magda 写道:
I've doubled checked both the pages and didn't find any usage of 
CacheTypeMetadata in Java code.


Please point out to a particular document and the code.


On 1/21/2016 11:55 AM, 李玉珏 wrote:

Hi:

On the sample code, you only modify the XML part, the Java code 
section is not modified, omitted.


Sent from Mail Master


在2016年01月20日 17:41 ,Denis Magda <mailto:dma...@gridgain.com>写道:

Updated the docs. Thanks for pointing out.

On 1/16/2016 12:19 PM, 李玉珏@163 wrote:
> Hi:
>
> In the 1.5.0 version, I found that CacheTypeMetadata was
abandoned and
> replaced by QueryEntity.
>
> I find that two classes of related instructions exist in the
manual:
> https://apacheignite.readme.io/docs/sql-queries
> https://apacheignite.readme.io/docs/cache-queries
>
> I suggest deleting the instructions and sample code for
> CacheTypeMetadata, so as not to confuse the developer,
> CacheTypeMetadata only exists for the sake of backward
compatibility.
>











Re: about AOP development

2016-01-21 Thread

Hi:

I am at home now, can not reproduce.

Do not need to cluster, to get the code to run directly, you can reproduce.

If you use the AOP spring technology, through the following code:

ClusterGroup cg = ignite.cluster().forServers();
IgniteCompute compute = ignite.compute(cg);
IgniteServices svcs = ignite.services(cg);
Service service = (Service)ac.getBean("computeGridService");
svcs.deployNodeSingleton("computeGridService", service);

Will throw an nullexception.

address is:https://github.com/liyuj/computegrid


在 16/1/21 19:40, Vladimir Ershov 写道:

Hi,

Yes, sure, I can take a look. Just send me, please, your full logs with
exception, and describe how exactly you reproduce it (how many nodes
started, which one is client and etc.).

Thanks!

On Thu, Jan 21, 2016 at 9:43 AM, 李玉珏 <18624049...@163.com> wrote:


Hi:

I understand your approach, it should be feasible, but not very elegant.
If use ProxyFactory in spring. At runtime dynamically add interceptor,
can solve the problem, but performance will influence.

I switched to a different way of writing, using the Service mechanism,
code has been updated to GitHub, throws NullException. I survey the
reason, the problem is in service deployment process of marshal and
unmarshal stage, because of AdvisedSupport's methodCache is transient,
this may be a compatibility problem, also asks you to look at.


Sent from Mail Master


On 2016-01-20 22:20 , Vladimir Ershov  Wrote:

As for the last step, let me correct myself:

3. Start server Ignite node from spring context *AND *put spring jars
inside classpath in *.sh file. Be sure, that both nodes are using the same
xml context.

On Wed, Jan 20, 2016 at 5:07 PM, Vladimir Ershov 
wrote:


Hi!

I've checked your code and spot an issue. The root cause, is using of
Autowired annotation, since it cause bean to be serialized on a client
side, and that leads ClassNotFoundException on the server side during

bean

deserialization, since server was started from *.sh, without necessary
spring jars in the classpath.

Good news here, that it could be fixed easily with those steps:

1. Remove Autowired from transferred entities as ComputeGridJob
2. When you need an applicationContext, use
@SpringApplicationContextResource annotation.  You are need to use it

in

your ComputeGridTask.
3. Start server Ignite node from spring context, or put spring jars
inside classpath in *.sh file.

Also, you can simplify your solution for ComputeGridService by using
@ServiceResource. Take a look:
https://apacheignite.readme.io/docs/service-example

Thanks!

On Wed, Jan 20, 2016 at 6:07 AM, 李玉珏 <18624049...@163.com> wrote:


Hi:
The relevant code on the GitHub, the address is:
https://github.com/liyuj/computegrid


Sent from Mail Master



On 2016-01-20 04:32 , Dmitriy Setrakyan Wrote:

The list does not support attachments. You can use pastebin [1] or gist
[2]
to paste your code and send the link here.

[1] http://pastebin.com/
[2] https://gist.github.com/

D.

On Tue, Jan 19, 2016 at 4:48 AM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

I had just sent the code to the list.

在 16/1/19 20:39, Denis Magda 写道:

Seems that peerClassLoading doesn't work for your case. Please share

the

source code of your example.

--
Denis

On 1/18/2016 3:48 PM, 李玉珏@163 wrote:


Hi:

I have already opened the peerClassLoading.
My practice is in eclipse create a java project, developed a
ComputeTaskSplitAdapter examples, then in the ComputeJobAdapter

call

configured spring interceptors service. This example in eclipse

operation

is no problem.

But if I open a node in the command line by ignite.sh, it will

prompt

the following error in the command line.

In the default configuration file of ignite, the same configuration

of

the peerClassLoading=true.

在 16/1/18 19:39, Yakov Zhdanov 写道:


Can you please try enabling "peerClassLoading" and share the

results

here?

--Yakov

2016-01-16 12:09 GMT+03:00 李玉珏@163 <18624049...@163.com>:

Hi:

In a distributed environment, if use the spring AOP programming,
generated
a class of byte code enhancement, then the error will be reported

as

follows:

java.lang.ClassNotFoundException:


demo.computegrid.ComputeGridService$$EnhancerBySpringCGLIB$$7b44b192

This error I understand, this class does not exist on the remote

node.

But the question is, is it a technical limitation of Ignite, or

is

it

the
way I use it,or is it a bug?

I opened the peer class loading , the normal deployment I did not

test,

but I estimate it will be the same error.











来自 *网易**手机号码邮箱* -- 手机号码就是邮箱帐号,了解详情> <http://shouji.163.com>





回复: Re: about CacheTypeMetadata

2016-01-21 Thread
Hi:

On the sample code, you only modify the XML part, the Java code section is not 
modified, omitted.

Sent from Mail Master



在2016年01月20日 17:41 ,Denis Magda写道:

Updated the docs. Thanks for pointing out.

On 1/16/2016 12:19 PM, 李玉珏@163 wrote:
> Hi:
>
> In the 1.5.0 version, I found that CacheTypeMetadata was abandoned and
> replaced by QueryEntity.
>
> I find that two classes of related instructions exist in the manual:
> https://apacheignite.readme.io/docs/sql-queries
> https://apacheignite.readme.io/docs/cache-queries
>
> I suggest deleting the instructions and sample code for
> CacheTypeMetadata, so as not to confuse the developer,
> CacheTypeMetadata only exists for the sake of backward compatibility.
>



Re: Re: About IgniteAtomicSequence

2016-01-20 Thread
Hi:

I in a very old machine simple to do the test, if open reserv mechanism, 
the ID generation speed can reach 50K/s. If turn off reserv mechanism, 
the performance will be dropped to 13K/s, performance degradation is 
very obvious, but off reserv will enable ID increase linearly with 
time, this aspect of the advantages and disadvantages can allow 
developers to choose their own.

In addition, the performance of IgniteAtomicSequence may related to the 
performance of cache nodes, therefore,AtomicConfiguration, whether it is 
necessary to add an attribute, similar nodeFilter such, let developers 
control a distributed datastructure cache deployed on the nodes with 
high performance.


Sent from Mail Master



On 2016-01-20 04:29 , Dmitriy Setrakyan Wrote:

The performance of AtomicSequence is very good as most of the operations
are local. The way it works is that it will reserve a range of numbers by
sending a request, but then will return all new IDs locally, until the
reserved range is exhausted.

More information here:
https://apacheignite.readme.io/docs/id-generator

D.

On Tue, Jan 19, 2016 at 4:54 AM, 李玉珏@163 <18624049...@163.com> wrote:

> Hi:
>
> Oh, sorry, wrong title.
>
> 在 16/1/19 16:50, Dmitriy Setrakyan 写道:
>
>> Yujue Li, what exactly would you like to benchmark? Is it the
>> IgniteAtomicSequence or IgniteAtomicReference? Also, benchmarks are better
>> viewed in comparison to something else. Is there something else in
>> particular you would like to compare these data structures to?
>>
>> D.
>>
>> On Sun, Jan 17, 2016 at 7:31 PM, 李玉珏 <18624049...@163.com> wrote:
>>
>> Hi:
>>>
>>> About IgniteAtomicReference, I think the function in the existing
>>> distributed ID generator advantage is very obvious, if converted to
>>> hexadecimal, can do a very short。
>>>
>>> I would like to ask, is there a particular description about the
>>> performance? Did the benchmark test on a specific hardware?
>>>
>>
>
>


Re: Re: Re: about AOP development

2016-01-20 Thread
Hi:

I understand your approach, it should be feasible, but not very elegant.
If use ProxyFactory in spring. At runtime dynamically add interceptor, 
can solve the problem, but performance will influence.

I switched to a different way of writing, using the Service mechanism, 
code has been updated to GitHub, throws NullException. I survey the 
reason, the problem is in service deployment process of marshal and 
unmarshal stage, because of AdvisedSupport's methodCache is transient, 
this may be a compatibility problem, also asks you to look at.


Sent from Mail Master



On 2016-01-20 22:20 , Vladimir Ershov Wrote:

As for the last step, let me correct myself:

   3. Start server Ignite node from spring context *AND *put spring jars
inside classpath in *.sh file. Be sure, that both nodes are using the same
xml context.

On Wed, Jan 20, 2016 at 5:07 PM, Vladimir Ershov 
wrote:

> Hi!
>
> I've checked your code and spot an issue. The root cause, is using of
> Autowired annotation, since it cause bean to be serialized on a client
> side, and that leads ClassNotFoundException on the server side during bean
> deserialization, since server was started from *.sh, without necessary
> spring jars in the classpath.
>
> Good news here, that it could be fixed easily with those steps:
>
>1. Remove Autowired from transferred entities as ComputeGridJob
>2. When you need an applicationContext, use
>@SpringApplicationContextResource annotation.  You are need to use it in
>your ComputeGridTask.
>3. Start server Ignite node from spring context, or put spring jars
>inside classpath in *.sh file.
>
> Also, you can simplify your solution for ComputeGridService by using
> @ServiceResource. Take a look:
> https://apacheignite.readme.io/docs/service-example
>
> Thanks!
>
> On Wed, Jan 20, 2016 at 6:07 AM, 李玉珏 <18624049...@163.com> wrote:
>
>> Hi:
>> The relevant code on the GitHub, the address is:
>> https://github.com/liyuj/computegrid
>>
>>
>> Sent from Mail Master
>>
>>
>>
>> On 2016-01-20 04:32 , Dmitriy Setrakyan Wrote:
>>
>> The list does not support attachments. You can use pastebin [1] or gist
>> [2]
>> to paste your code and send the link here.
>>
>> [1] http://pastebin.com/
>> [2] https://gist.github.com/
>>
>> D.
>>
>> On Tue, Jan 19, 2016 at 4:48 AM, 李玉珏@163 <18624049...@163.com> wrote:
>>
>> > Hi:
>> >
>> > I had just sent the code to the list.
>> >
>> > 在 16/1/19 20:39, Denis Magda 写道:
>> >
>> > Seems that peerClassLoading doesn't work for your case. Please share the
>> >> source code of your example.
>> >>
>> >> --
>> >> Denis
>> >>
>> >> On 1/18/2016 3:48 PM, 李玉珏@163 wrote:
>> >>
>> >>> Hi:
>> >>>
>> >>> I have already opened the peerClassLoading.
>> >>> My practice is in eclipse create a java project, developed a
>> >>> ComputeTaskSplitAdapter examples, then in the ComputeJobAdapter call
>> >>> configured spring interceptors service. This example in eclipse
>> operation
>> >>> is no problem.
>> >>>
>> >>> But if I open a node in the command line by ignite.sh, it will prompt
>> >>> the following error in the command line.
>> >>>
>> >>> In the default configuration file of ignite, the same configuration of
>> >>> the peerClassLoading=true.
>> >>>
>> >>> 在 16/1/18 19:39, Yakov Zhdanov 写道:
>> >>>
>> >>>> Can you please try enabling "peerClassLoading" and share the results
>> >>>> here?
>> >>>>
>> >>>> --Yakov
>> >>>>
>> >>>> 2016-01-16 12:09 GMT+03:00 李玉珏@163 <18624049...@163.com>:
>> >>>>
>> >>>> Hi:
>> >>>>>
>> >>>>> In a distributed environment, if use the spring AOP programming,
>> >>>>> generated
>> >>>>> a class of byte code enhancement, then the error will be reported as
>> >>>>> follows:
>> >>>>>
>> >>>>> java.lang.ClassNotFoundException:
>> >>>>> demo.computegrid.ComputeGridService$$EnhancerBySpringCGLIB$$7b44b192
>> >>>>>
>> >>>>> This error I understand, this class does not exist on the remote
>> node.
>> >>>>> But the question is, is it a technical limitation of Ignite, or is
>> it
>> >>>>> the
>> >>>>> way I use it,or is it a bug?
>> >>>>>
>> >>>>> I opened the peer class loading , the normal deployment I did not
>> test,
>> >>>>> but I estimate it will be the same error.
>> >>>>>
>> >>>>>
>> >>>
>> >>>
>> >>
>> >
>> >
>>
>
>


Re: Re: about AOP development

2016-01-19 Thread
Hi:
The relevant code on the GitHub, the address is:
https://github.com/liyuj/computegrid


Sent from Mail Master



On 2016-01-20 04:32 , Dmitriy Setrakyan Wrote:

The list does not support attachments. You can use pastebin [1] or gist [2]
to paste your code and send the link here.

[1] http://pastebin.com/
[2] https://gist.github.com/

D.

On Tue, Jan 19, 2016 at 4:48 AM, 李玉珏@163 <18624049...@163.com> wrote:

> Hi:
>
> I had just sent the code to the list.
>
> 在 16/1/19 20:39, Denis Magda 写道:
>
> Seems that peerClassLoading doesn't work for your case. Please share the
>> source code of your example.
>>
>> --
>> Denis
>>
>> On 1/18/2016 3:48 PM, 李玉珏@163 wrote:
>>
>>> Hi:
>>>
>>> I have already opened the peerClassLoading.
>>> My practice is in eclipse create a java project, developed a
>>> ComputeTaskSplitAdapter examples, then in the ComputeJobAdapter call
>>> configured spring interceptors service. This example in eclipse operation
>>> is no problem.
>>>
>>> But if I open a node in the command line by ignite.sh, it will prompt
>>> the following error in the command line.
>>>
>>> In the default configuration file of ignite, the same configuration of
>>> the peerClassLoading=true.
>>>
>>> 在 16/1/18 19:39, Yakov Zhdanov 写道:
>>>
>>>> Can you please try enabling "peerClassLoading" and share the results
>>>> here?
>>>>
>>>> --Yakov
>>>>
>>>> 2016-01-16 12:09 GMT+03:00 李玉珏@163 <18624049...@163.com>:
>>>>
>>>> Hi:
>>>>>
>>>>> In a distributed environment, if use the spring AOP programming,
>>>>> generated
>>>>> a class of byte code enhancement, then the error will be reported as
>>>>> follows:
>>>>>
>>>>> java.lang.ClassNotFoundException:
>>>>> demo.computegrid.ComputeGridService$$EnhancerBySpringCGLIB$$7b44b192
>>>>>
>>>>> This error I understand, this class does not exist on the remote node.
>>>>> But the question is, is it a technical limitation of Ignite, or is it
>>>>> the
>>>>> way I use it,or is it a bug?
>>>>>
>>>>> I opened the peer class loading , the normal deployment I did not test,
>>>>> but I estimate it will be the same error.
>>>>>
>>>>>
>>>
>>>
>>
>
>


Re: About IgniteAtomicSequence

2016-01-19 Thread

Hi:

Oh, sorry, wrong title.

在 16/1/19 16:50, Dmitriy Setrakyan 写道:

Yujue Li, what exactly would you like to benchmark? Is it the
IgniteAtomicSequence or IgniteAtomicReference? Also, benchmarks are better
viewed in comparison to something else. Is there something else in
particular you would like to compare these data structures to?

D.

On Sun, Jan 17, 2016 at 7:31 PM, 李玉珏 <18624049...@163.com> wrote:


Hi:

About IgniteAtomicReference, I think the function in the existing
distributed ID generator advantage is very obvious, if converted to
hexadecimal, can do a very short。

I would like to ask, is there a particular description about the
performance? Did the benchmark test on a specific hardware?





Re: about AOP development

2016-01-19 Thread

Hi:

I had just sent the code to the list.

在 16/1/19 20:39, Denis Magda 写道:
Seems that peerClassLoading doesn't work for your case. Please share 
the source code of your example.


--
Denis

On 1/18/2016 3:48 PM, 李玉珏@163 wrote:

Hi:

I have already opened the peerClassLoading.
My practice is in eclipse create a java project, developed a 
ComputeTaskSplitAdapter examples, then in the ComputeJobAdapter call 
configured spring interceptors service. This example in eclipse 
operation is no problem.


But if I open a node in the command line by ignite.sh, it will prompt 
the following error in the command line.


In the default configuration file of ignite, the same configuration 
of the peerClassLoading=true.


在 16/1/18 19:39, Yakov Zhdanov 写道:
Can you please try enabling "peerClassLoading" and share the results 
here?


--Yakov

2016-01-16 12:09 GMT+03:00 李玉珏@163 <18624049...@163.com>:


Hi:

In a distributed environment, if use the spring AOP programming, 
generated

a class of byte code enhancement, then the error will be reported as
follows:

java.lang.ClassNotFoundException:
demo.computegrid.ComputeGridService$$EnhancerBySpringCGLIB$$7b44b192

This error I understand, this class does not exist on the remote node.
But the question is, is it a technical limitation of Ignite, or is 
it the

way I use it,or is it a bug?

I opened the peer class loading , the normal deployment I did not 
test,

but I estimate it will be the same error.











Re: About IgniteAtomicReference

2016-01-19 Thread

Hi:

I am concerned about the IgniteAtomicSequence, which function is 
distributed ID generator, so the performance is very important. I don't 
think IgniteAtomicReference has a performance problem.


The solution of the distributed ID generator is very much, the technical 
route is different, applicable scene is also different, the simple 
comparison of performance is not significant.


I think to refer to the developers, the official gives a specific 
hardware performance data can be, the remaining let developers 
themselves to make a choice, such as: 4*core 2.4GHz, 16g memory,no 
reserve, every second can generate 1 ID.


In addition, the performance of IgniteAtomicSequence may related to the 
performance of cache nodes, therefore, AtomicConfiguration, whether it 
is necessary to add an attribute, similar nodeFilter such, let 
developers control a distributed datastructure cache deployed on the 
nodes with high performance.


Thanks!

在 16/1/19 16:50, Dmitriy Setrakyan 写道:

Yujue Li, what exactly would you like to benchmark? Is it the
IgniteAtomicSequence or IgniteAtomicReference? Also, benchmarks are better
viewed in comparison to something else. Is there something else in
particular you would like to compare these data structures to?

D.

On Sun, Jan 17, 2016 at 7:31 PM, 李玉珏 <18624049...@163.com> wrote:


Hi:

About IgniteAtomicReference, I think the function in the existing
distributed ID generator advantage is very obvious, if converted to
hexadecimal, can do a very short。

I would like to ask, is there a particular description about the
performance? Did the benchmark test on a specific hardware?





Re: about AOP development

2016-01-18 Thread

Hi:

I have already opened the peerClassLoading.
My practice is in eclipse create a java project, developed a 
ComputeTaskSplitAdapter examples, then in the ComputeJobAdapter call 
configured spring interceptors service. This example in eclipse 
operation is no problem.


But if I open a node in the command line by ignite.sh, it will prompt 
the following error in the command line.


In the default configuration file of ignite, the same configuration of 
the peerClassLoading=true.


在 16/1/18 19:39, Yakov Zhdanov 写道:

Can you please try enabling "peerClassLoading" and share the results here?

--Yakov

2016-01-16 12:09 GMT+03:00 李玉珏@163 <18624049...@163.com>:


Hi:

In a distributed environment, if use the spring AOP programming, generated
a class of byte code enhancement, then the error will be reported as
follows:

java.lang.ClassNotFoundException:
demo.computegrid.ComputeGridService$$EnhancerBySpringCGLIB$$7b44b192

This error I understand, this class does not exist on the remote node.
But the question is, is it a technical limitation of Ignite, or is it the
way I use it,or is it a bug?

I opened the peer class loading , the normal deployment I did not test,
but I estimate it will be the same error.






About IgniteAtomicReference

2016-01-17 Thread
Hi:

About IgniteAtomicReference, I think the function in the existing 
distributed ID generator advantage is very obvious, if converted to 
hexadecimal, can do a very short。

I would like to ask, is there a particular description about the 
performance? Did the benchmark test on a specific hardware?

about CacheTypeMetadata

2016-01-16 Thread

Hi:

In the 1.5.0 version, I found that CacheTypeMetadata was abandoned and 
replaced by QueryEntity.


I find that two classes of related instructions exist in the manual:
https://apacheignite.readme.io/docs/sql-queries
https://apacheignite.readme.io/docs/cache-queries

I suggest deleting the instructions and sample code for 
CacheTypeMetadata, so as not to confuse the developer, CacheTypeMetadata 
only exists for the sake of backward compatibility.




about AOP development

2016-01-16 Thread

Hi:

In a distributed environment, if use the spring AOP programming, 
generated a class of byte code enhancement, then the error will be 
reported as follows:


java.lang.ClassNotFoundException: 
demo.computegrid.ComputeGridService$$EnhancerBySpringCGLIB$$7b44b192


This error I understand, this class does not exist on the remote node.
But the question is, is it a technical limitation of Ignite, or is it 
the way I use it,or is it a bug?


I opened the peer class loading , the normal deployment I did not test, 
but I estimate it will be the same error.


about AtomicConfiguration

2016-01-13 Thread

Hi:

About AtomicConfiguration, I found the following issue:

Configuration of node 1:

AtomicConfiguration atomicCfg = new AtomicConfiguration();
atomicCfg.setBackups(1);
atomicCfg.setAtomicSequenceReserveSize(0);

IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setAtomicConfiguration(atomicCfg);
Ignite ignite = Ignition.start(cfg);

Configuration of node 2:

Ignite ignite = Ignition.start();

Then there will be the following error:

Only two nodes are configured in the same configuration to successfully 
start up。


AtomicConfiguration is the global configuration of the start, can not be 
set dynamically after the start, and can not be set for a single sequence。


CacheConfiguration can be configured separately, and can be dynamically 
configured by ignite.getOrCreateCache(CacheConfiguration) after startup.


I think AtomicConfiguration's design is not reasonable。
I propose to merge the three parameters of the atomicSequence method 
with the AtomicConfiguration, and then add one:

Ignite.atomicSequence (AtomicConfiguration) method.

Or communitity can consider a more elegant approach.


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

2016-01-12 Thread

Hi:

About the 1.5 version of the chinese manual, in addition to the 
following mentioned some of the streamers, all have been translated.


Address for:https://www.zybuluo.com/liyuj/note/230739。

在 15/12/28 17:12, Denis Magda 写道:

Hi Yujue Li,

I've added documentation for Ignite Semaphore to Distributed Data 
Structures section

https://apacheignite.readme.io/docs/distributed-semaphore

Missed documentation for MQTT and Twitter streamers will be added a 
bit later. I'll let you know when this happens.


The rest of the 1.5 documentation articles look good for me.

Regards,
Denis

On 12/25/2015 7:40 PM, Dmitriy Setrakyan wrote:
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.

The reason to put the code on git.oschina.net

Re: Javadoc link need to be updated

2016-01-09 Thread

Hi


I note that the version number of the online manual is still in the beta 
state.




在 16/1/9 01:19, Dmitriy Setrakyan 写道:

Thanks Roman! I updated the link.

On Thu, Jan 7, 2016 at 7:40 PM, Roman Shtykh 
wrote:


Igniters,

I noticed Javadoc link on https://apacheignite.readme.io/ points to the
older 'b1' version, instead of 'final'
https://ignite.apache.org/releases/1.5.0.final/javadoc/

-Roman





Re: Ignite Voting Process

2016-01-01 Thread

Great!

在 16/1/1 02:35, Dmitriy Setrakyan 写道:

I tend to agree with Raul.

We have been anal-retentive to a fault with regard to LGPL, instead of
focusing on usability. Our users are already required to take a conscious
step to include LGPL modules into Ignite builds, so there is no implicit
“drag-in”, as Raul mentioned.

I would vote for publishing all Ignite modules to Maven, without exception.

D.



On Thu, Dec 31, 2015 at 5:21 AM, Raul Kripalani  wrote:


Hi Brane,

On Thu, Dec 31, 2015 at 8:58 AM, Branko Čibej  wrote:


We'd be publishing modules that can't be used without the LGPL
components. I'm not sure how that stands WRT our policies but I can't
see how it would be a service to our users to actively nudge them
towards using restrictive-licensed code.


The ASF policies specify that, as long as our components are optional and
not needed by the core project, we can publish them, obviously *without*
packaging the LGPL binary nor implicitly "dragging it in" during the build.
This can be achieved with a 'runtime' scope in Maven.

It does make a huge difference to the end user of these 3 modules – being
able to reference ignite-hibernate and simply having to manually drop in
the Hibernate dependency vs. having to: (1) check out the source, (2) run
the build, (3) publish the artifacts in their corporate Nexus repo, etc. +
having to do this *for each release*.

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk






Re: about ignite-hibernate module

2015-12-31 Thread

Hi:

Sorry, my understanding of the open source license is not very deep.

As far as I know, ehcache is also abide by Apache 2.0 license, ignite 
also abideby Apache 2.0 license, is because ignite with a commercial 
version that led to this situation now?


If so, ignite-hibernate-1.2.0-incubating should also be removed from the 
Maven repo, because the release version and git code has been inconsistent.


Or, the ignite-hibernate module can be released in the open source 
version, there is no commercial version of this module.


In addition, the module of this information should also be described in 
the document.


在 15/12/30 20:56, Sergey Kozlov 写道:

Hi

Hibernate is licensed under LGPL thus it's not allowed to deploy in Apache
Ignite maven repository

On Wed, Dec 30, 2015 at 3:46 PM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

There are a few problems:
1.in the 1.4.0 and 1.5.0-b1 version of the release package, there is no
ignite-hibernate module, I think this is a mistake, it should be added, in
addition, Maven repo version is not correct;

2 in the 1.5.0-b1 version of the release package, Hibernate 2-level cache
part of the sample code is missing, and the 1.4.0 version contains the code;

3 recommended in the official release of the package, including the
building point of the source code, and many other open source projects are
doing so,to facilitate the development of personnel debugging, I now get
the 1.4 version of the source code has been inconsistent with the release
version.









Re: List of contributors has been updated

2015-12-30 Thread

Hi:

My name is YuJue Li,I am Ignite chinese document translation.

在 15/12/30 20:17, Denis Magda 写道:

Igniters,

I've just updated the list of Apache Ignite contributors adding the 
following guys to the list


Roman Shtykh
Igor Sapego
Ilya Lantukh
Michael Griggs
Pavel Konstantinov
Saikat Maitra
Vasiliy Sisko
Vladimir Ershov
Vladislav Jelisavcic
Nigel Westbury

Undoubtedly I've forgot to add someone else. If have contributed to 
Apache Ignite and don't see you in contributors table on this page [1] 
please let me know.


[1] https://ignite.apache.org/community/resources.html

Regards,
Denis





Re: Re: about ignite-hibernate module

2015-12-30 Thread
Hi

I said that the ignite-hibernate module,not the hibernate itself.

The latest version of the current maven repo is 1.2.0-incubating.



On 2015-12-30 20:56 , Sergey Kozlov Wrote:

Hi

Hibernate is licensed under LGPL thus it's not allowed to deploy in Apache
Ignite maven repository

On Wed, Dec 30, 2015 at 3:46 PM, 李玉珏@163 <18624049...@163.com> wrote:

> Hi:
>
> There are a few problems:
> 1.in the 1.4.0 and 1.5.0-b1 version of the release package, there is no
> ignite-hibernate module, I think this is a mistake, it should be added, in
> addition, Maven repo version is not correct;
>
> 2 in the 1.5.0-b1 version of the release package, Hibernate 2-level cache
> part of the sample code is missing, and the 1.4.0 version contains the code;
>
> 3 recommended in the official release of the package, including the
> building point of the source code, and many other open source projects are
> doing so,to facilitate the development of personnel debugging, I now get
> the 1.4 version of the source code has been inconsistent with the release
> version.
>
>


--
Sergey Kozlov
GridGain Systems
www.gridgain.com


about ignite-hibernate module

2015-12-30 Thread

Hi:

There are a few problems:
1.in the 1.4.0 and 1.5.0-b1 version of the release package, there is no 
ignite-hibernate module, I think this is a mistake, it should be added, 
in addition, Maven repo version is not correct;


2 in the 1.5.0-b1 version of the release package, Hibernate 2-level 
cache part of the sample code is missing, and the 1.4.0 version contains 
the code;


3 recommended in the official release of the package, including the 
building point of the source code, and many other open source projects 
are doing so,to facilitate the development of personnel debugging, I 
now get the 1.4 version of the source code has been inconsistent with 
the release version.




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

2015-12-28 Thread

Hi:

OK!

在 15/12/28 17:12, Denis Magda 写道:

Hi Yujue Li,

I've added documentation for Ignite Semaphore to Distributed Data 
Structures section

https://apacheignite.readme.io/docs/distributed-semaphore

Missed documentation for MQTT and Twitter streamers will be added a 
bit later. I'll let you know when this happens.


The rest of the 1.5 documentation articles look good for me.

Regards,
Denis

On 12/25/2015 7:40 PM, Dmitriy Setrakyan wrote:
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.

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
man

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

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

2015-12-24 Thread

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 if anyone in the community would be able
to

contribute. Looks like oschina.net is a copy of GitHub. I tried to

create
a user there, but could not (I am not getting a verification email).
Any
ideas?

I think the best way to share this process would be to add users to
the
GIT project on oschina (just like we do with readme.io).

D.


On Sun, Nov 15, 2015 at 4:37 AM, 姜 为  wrote:

Hi:

I do not agree with Yujue Li,his approach is very selfish.

At first I wanted to help him complete the Chinese
translation
of
the open-source project,
but he can not be on the oschina fork, which means that
if
he
appeared wrong semantic translation,
others can not make changes to the correction!

I hope he can follow

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

2015-12-05 Thread

Hi:

As of today, distributed data structures have been translated, and 
https://www.zybuluo.com/liyuj/note/230739 has been updated. On the 
whole, I have about half the workload.


My spare time is completely in the translation work, so the overall 
progress is still very fast, if everything goes smoothly, the end of 
this month should be able to complete.


I have seen the community about the 1.5 version of the progress, I 
intend to complete the 1.4 version of the translation, first do a full 
version, and then I compare the difference between the version of the 
GitHub to upgrade to version 1.5.


After the document is updated to version 1.5, I will try to keep the 
development of the community in line to ensure that documents and Ignite 
version of the release synchronization.



在 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 if anyone in the community would be able
to

contribute. Looks like oschina.net is a copy of GitHub. I tried to

create
a user there, but could not (I am not getting a verification email).
Any
ideas?

I think the best way to share this process would be 

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

2015-12-03 Thread

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 if anyone in the community would be able
to


contribute. Looks like oschina.net is a copy of GitHub. I tried to
create
a user there, but could not (I am not getting a verification email).
Any
ideas?

I think the best way to share this process would be to add users to the
GIT project on oschina (just like we do with readme.io).

D.


On Sun, Nov 15, 2015 at 4:37 AM, 姜 为  wrote:

Hi:


   I do not agree with Yujue Li,his approach is very selfish.
   At first I wanted to help him complete the Chinese
translation
of
the open-source project,
   but he can not be on the oschina fork, which means that if
he
appeared wrong semantic translation,
   others can not make changes to the correction!

   I hope he can follow the spirit of open source, but not for
themselves to achieve certain purposes do such a thing!

在 2015年11月15日,上午10:19,李玉珏@163 <18624049...@163.com> 写道:


Hi:

On the Ignite Development Manual of the simplified chinese

localization, I have the first part of the 'basic concepts'

translation
is
completed, the second part of the 'cluster' has been translated, the
content is being carried out.

Some people suggest that I translate directly on the readme.io,

because I'm here to visit the readme.io speed is slower, and the

other
readme uses a hybrid online editing mode, for the consideration of the
translation speed, I use pure markdown to write. In view of the effect
of
readme.io is better, but I have limited time, if there is a volunteer
in
the community will be willing to convert pure m

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

2015-11-30 Thread

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 
contribute. Looks like oschina.net is a copy of GitHub. I tried to
create
a user there, but could not (I am not getting a verification email). Any
ideas?

I think the best way to share this process would be to add users to the
GIT project on oschina (just like we do with readme.io).

D.


On Sun, Nov 15, 2015 at 4:37 AM, 姜 为  wrote:

Hi:

  I do not agree with Yujue Li,his approach is very selfish.
  At first I wanted to help him complete the Chinese translation
of
the open-source project,
  but he can not be on the oschina fork, which means that if he
appeared wrong semantic translation,
  others can not make changes to the correction!

  I hope he can follow the spirit of open source, but not for
themselves to achieve certain purposes do such a thing!

在 2015年11月15日,上午10:19,李玉珏@163 <18624049...@163.com> 写道:

Hi:

On the Ignite Development Manual of the simplified chinese


localization, I have the first part of the 'basic concepts' translation
is
completed, the second part of the 'cluster' has been translated, the
content is being carried out.


Some people suggest that I translate directly on the readme.io,


because I'm here to visit the readme.io speed is slower, and the other
readme uses a hybrid online editing mode, for the consideration of the
translation speed, I use pure markdown to write. In view of the effect
of
readme.io is better, but I have limited time, if there is a volunteer
in
the community will be willing to convert pure markdown to readme, and
help
me do the translation of the audit, will be a very good thing.


If no one is willing to do this more tedious work, I plan to convert


pure markdown to html, like mail attachments, and then the official put
a
link to my page is OK.


在 15/11/9 15:29, Dmitriy Setrakyan 写道:


On Sun, Nov 8, 2015 at 10:36 PM, 姜 为  wrote:

Hi Dmitriy:

  I create https://apacheignitecn.readme.io/docs <
https://apacheignitecn.readme.io/docs> for translate Chinese.

Thanks, I will add the link to Ignite website, once we have something

to
publish.


  And http://apacheignite.readme.io/ <
http://apacheignite.readme.io/>

have plans to do international translate?

I don’t think readme.io supports this feature.




在 2015年11月8日,下午5:38,Dmitriy Setrakyan  写道

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

2015-11-17 Thread

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 
wrote:


In general, it would be great if anyone in the community would be able to
contribute. Looks like oschina.net is a copy of GitHub. I tried to create
a user there, but could not (I am not getting a verification email). Any
ideas?

I think the best way to share this process would be to add users to the
GIT project on oschina (just like we do with readme.io).

D.


On Sun, Nov 15, 2015 at 4:37 AM, 姜 为  wrote:


Hi:

 I do not agree with Yujue Li,his approach is very selfish.
 At first I wanted to help him complete the Chinese translation of
the open-source project,
 but he can not be on the oschina fork, which means that if he
appeared wrong semantic translation,
 others can not make changes to the correction!

 I hope he can follow the spirit of open source, but not for
themselves to achieve certain purposes do such a thing!


在 2015年11月15日,上午10:19,李玉珏@163 <18624049...@163.com> 写道:

Hi:

On the Ignite Development Manual of the simplified chinese

localization, I have the first part of the 'basic concepts' translation is
completed, the second part of the 'cluster' has been translated, the
content is being carried out.

Some people suggest that I translate directly on the readme.io,

because I'm here to visit the readme.io speed is slower, and the other
readme uses a hybrid online editing mode, for the consideration of the
translation speed, I use pure markdown to write. In view of the effect of
readme.io is better, but I have limited time, if there is a volunteer in
the community will be willing to convert pure markdown to readme, and help
me do the translation of the audit, will be a very good thing.

If no one is willing to do this more tedious work, I plan to convert

pure markdown to html, like mail attachments, and then the official put a
link to my page is OK.

在 15/11/9 15:29, Dmitriy Setrakyan 写道:

On Sun, Nov 8, 2015 at 10:36 PM, 姜 为  wrote:


Hi Dmitriy:

 I create https://apacheignitecn.readme.io/docs <
https://apacheignitecn.readme.io/docs> for translate Chinese.


Thanks, I will add the link to Ignite website, once we have something

to

publish.



 And http://apacheignite.readme.io/ <

http://apacheignite.readme.io/>

have plans to do international translate?


I don’t think readme.io supports this feature.





在 2015年11月8日,下午5:38,Dmitriy Setrakyan  写道:

On Sat, Nov 7, 2015 at 6:30 PM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

I have registered the readme.io account, and I know how to use it

in

general.
I asked, the Suggest Edits will be effective or need a review

process

after the submission?


The committers will review the edits.



In addition, I now know about Ignite is not deep enough, I'm afraid

I

can

only modify some obvious mistakes.


This is OK, any improvement to the documentation helps.



在 15/11/7 17:04, Dmitriy Setrakyan 写道:

Hi,

I agree that documentation may be inconsistent in some places. Can

you

use

the “Suggest Edits” feature of readme.io to provide the fixes to
documentation?

D.

On Fri, Nov 6, 2015 at 4:06 AM, 李玉珏@163 <18624049...@163.com>

wrote:

Hi:

The speed of the problem may be related to the network situation

between

China and the United States, I am here very fast.
I am not very busy recently, so the speed of the translation of

these

days
is very fast, and it is expected that the next week will be

related to

the
cluster will be translated, and then into the translation of data

grid.

In addition,In the translation process, I found that some parts

of the

document is clearly wrong, mainly in the description of some
configuration
parameters, and the code does not match, for example, in the end

of

the

chapter of the cluster configuration, the parameters of the
TcpDiscoverySpi, some obvious mistakes, the other part of

about apache ignite's document localization(Simplified Chinese)

2015-11-14 Thread

Hi:

On the Ignite Development Manual of the simplified chinese localization, 
I have the first part of the 'basic concepts' translation is completed, 
the second part of the' cluster 'has been translated, the content is 
being carried out.


Some people suggest that I translate directly on the readme.io, because 
I'm here to visit the readme.io speed is slower, and the other readme 
uses a hybrid online editing mode, for the consideration of the 
translation speed, I use pure markdown to write. In view of the effect 
of readme.io is better, but I have limited time, if there is a volunteer 
in the community will be willing to convert pure markdown to readme, and 
help me do the translation of the audit, will be a very good thing.


If no one is willing to do this more tedious work, I plan to convert 
pure markdown to html, like mail attachments, and then the official put 
a link to my page is OK.


在 15/11/9 15:29, Dmitriy Setrakyan 写道:

On Sun, Nov 8, 2015 at 10:36 PM, 姜 为  wrote:


Hi Dmitriy:

 I create https://apacheignitecn.readme.io/docs <
https://apacheignitecn.readme.io/docs> for translate Chinese.


Thanks, I will add the link to Ignite website, once we have something to
publish.



 And http://apacheignite.readme.io/ <http://apacheignite.readme.io/>
have plans to do international translate?


I don’t think readme.io supports this feature.






在 2015年11月8日,下午5:38,Dmitriy Setrakyan  写道:

On Sat, Nov 7, 2015 at 6:30 PM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

I have registered the readme.io account, and I know how to use it in
general.
I asked, the Suggest Edits will be effective or need a review process
after the submission?


The committers will review the edits.



In addition, I now know about Ignite is not deep enough, I'm afraid I

can

only modify some obvious mistakes.


This is OK, any improvement to the documentation helps.



在 15/11/7 17:04, Dmitriy Setrakyan 写道:

Hi,

I agree that documentation may be inconsistent in some places. Can you

use

the “Suggest Edits” feature of readme.io to provide the fixes to
documentation?

D.

On Fri, Nov 6, 2015 at 4:06 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi:

The speed of the problem may be related to the network situation

between

China and the United States, I am here very fast.
I am not very busy recently, so the speed of the translation of these
days
is very fast, and it is expected that the next week will be related to
the
cluster will be translated, and then into the translation of data

grid.

In addition,In the translation process, I found that some parts of the
document is clearly wrong, mainly in the description of some
configuration
parameters, and the code does not match, for example, in the end of

the

chapter of the cluster configuration, the parameters of the
TcpDiscoverySpi, some obvious mistakes, the other part of the problem
also
exists.
I think this is a big problem, it may be difficult to maintain the

unity

of the code and documentation, but still hope that the development

team

can
improve the problem, otherwise easy to mislead the developer, because

it

is
not every developer will go to see the code。


在 15/11/6 01:17, Dmitriy Setrakyan 写道:

Yes, I can visit the link, although it takes a while to load.

Please keep us posted with your progress. Let us know once you have
enough
ready for us to post on the website. It does not have to be a complete
set,
just enough to get people started.

Thanks,
D.

On Thu, Nov 5, 2015 at 4:04 AM, 李玉珏@163 <18624049...@163.com> wrote:

Hi:

OK, I've subscribed to it.

I confirm that I have made the link you can visit it? I would like to
take git.oschina.net as the hosting platform of the document, the

HTML

will be generated after the completion of the translation will also

be

placed in the oschina.net, I have to make sure that all people can

be

normal access.

在 15/11/5 02:19, Dmitriy Setrakyan 写道:

Yujue Li,

Have you been able to properly subscribe? Usually you would get a

reply

and you have to reply to that reply. After that your subscription is
done.

D.

On Wed, Nov 4, 2015 at 3:52 AM, 李玉珏@163 < <18624049...@163.com>
18624049...@163.com> wrote:

Hi:

I am a developer from China, I hope to join the ignite community.
I hope that in the community to engage in the work is to translate

the

documentation of Ignite into simplified chinese, to help Ignite
promotion
in china.

Thanks!











# 1.基本概念
## 1.1.Ignite是什么
Apache 
Ignite内存数据组织是高性能的、集成化的以及分布式的内存平台,他可以实时地在大数据集中执行事务和计算,和传统的基于磁盘或者闪存的技术相比,性能有数量级的提升。
### 1.1.1.特性一览
可以将Ignite视为一个独立的、易于集成的内存组件的集合,目的是改进应用程序的性能和可扩展性,部分组件包括:
 - 高级的集群化
 - 数据网格(JCache)
 - 流计算和CEP
 - 计算网格
 - 服务网格
 - Ignite文件系统
 - 分布式数据结构
 - 分布式消息
 - 分布式事件模型
 - Hadoop加速
 - Spark共享RDD

## 1.2.入门
这部分帮助你开始一个新的Ignite程序,你会发现他瞬间就可以跑起来!
### 1.2.1.准备
Apache Ignite官方在如下环境中进行的测试:
 - JDK:Oracle JDK7及以上
 - OS:Linux(任何版本),Mac OS X(10.6及以上),Windows(XP及以上),Windows Server

Re: developer from China

2015-11-07 Thread

Hi:

I have registered the readme.io account, and I know how to use it in 
general.
I asked, the Suggest Edits will be effective or need a review process 
after the submission?


In addition, I now know about Ignite is not deep enough, I'm afraid I 
can only modify some obvious mistakes.


在 15/11/7 17:04, Dmitriy Setrakyan 写道:

Hi,

I agree that documentation may be inconsistent in some places. Can you use
the “Suggest Edits” feature of readme.io to provide the fixes to
documentation?

D.

On Fri, Nov 6, 2015 at 4:06 AM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

The speed of the problem may be related to the network situation between
China and the United States, I am here very fast.
I am not very busy recently, so the speed of the translation of these days
is very fast, and it is expected that the next week will be related to the
cluster will be translated, and then into the translation of data grid.

In addition,In the translation process, I found that some parts of the
document is clearly wrong, mainly in the description of some configuration
parameters, and the code does not match, for example, in the end of the
chapter of the cluster configuration, the parameters of the
TcpDiscoverySpi, some obvious mistakes, the other part of the problem also
exists.
I think this is a big problem, it may be difficult to maintain the unity
of the code and documentation, but still hope that the development team can
improve the problem, otherwise easy to mislead the developer, because it is
not every developer will go to see the code。


在 15/11/6 01:17, Dmitriy Setrakyan 写道:

Yes, I can visit the link, although it takes a while to load.

Please keep us posted with your progress. Let us know once you have enough
ready for us to post on the website. It does not have to be a complete set,
just enough to get people started.

Thanks,
D.

On Thu, Nov 5, 2015 at 4:04 AM, 李玉珏@163 <18624049...@163.com> wrote:


Hi:

OK, I've subscribed to it.

I confirm that I have made the link you can visit it? I would like to
take git.oschina.net as the hosting platform of the document, the HTML
will be generated after the completion of the translation will also be
placed in the oschina.net, I have to make sure that all people can be
normal access.

在 15/11/5 02:19, Dmitriy Setrakyan 写道:

Yujue Li,

Have you been able to properly subscribe? Usually you would get a reply
and you have to reply to that reply. After that your subscription is done.

D.

On Wed, Nov 4, 2015 at 3:52 AM, 李玉珏@163 < <18624049...@163.com>
18624049...@163.com> wrote:


Hi:

I am a developer from China, I hope to join the ignite community.
I hope that in the community to engage in the work is to translate the
documentation of Ignite into simplified chinese, to help Ignite promotion
in china.

Thanks!












Re: developer from China

2015-11-06 Thread

Hi:

The speed of the problem may be related to the network situation between 
China and the United States, I am here very fast.
I am not very busy recently, so the speed of the translation of these 
days is very fast, and it is expected that the next week will be related 
to the cluster will be translated, and then into the translation of data 
grid.


In addition,In the translation process, I found that some parts of the 
document is clearly wrong, mainly in the description of some 
configuration parameters, and the code does not match, for example, in 
the end of the chapter of the cluster configuration, the parameters of 
the TcpDiscoverySpi, some obvious mistakes, the other part of the 
problem also exists.
I think this is a big problem, it may be difficult to maintain the unity 
of the code and documentation, but still hope that the development team 
can improve the problem, otherwise easy to mislead the developer, 
because it is not every developer will go to see the code。



在 15/11/6 01:17, Dmitriy Setrakyan 写道:

Yes, I can visit the link, although it takes a while to load.

Please keep us posted with your progress. Let us know once you have 
enough ready for us to post on the website. It does not have to be a 
complete set, just enough to get people started.


Thanks,
D.

On Thu, Nov 5, 2015 at 4:04 AM, 李玉珏@163 <18624049...@163.com 
<mailto:18624049...@163.com>> wrote:


Hi:

OK, I've subscribed to it.

I confirm that I have made the link you can visit it? I would like
to take git.oschina.net <http://git.oschina.net> as the hosting
platform of the document, the HTML will be generated after the
completion of the translation will also be placed in the
oschina.net <http://oschina.net>, I have to make sure that all
people can be normal access.

在 15/11/5 02:19, Dmitriy Setrakyan 写道:

Yujue Li,

Have you been able to properly subscribe? Usually you would get a
reply and you have to reply to that reply. After that your
subscription is done.

D.

On Wed, Nov 4, 2015 at 3:52 AM, 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>> wrote:

Hi:

I am a developer from China, I hope to join the ignite community.
I hope that in the community to engage in the work is to
translate the documentation of Ignite into simplified
chinese, to help Ignite promotion in china.

Thanks!










  1   2   >