[jira] [Created] (IGNITE-2173) Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with if (log.isDebugEnabled())

[Michael Griggs (JIRA)]

Michael Griggs created IGNITE-2173:
--

 Summary: Some log.debug() calls in CacheAbstractJdbcStore.java are 
not protected with if (log.isDebugEnabled())
 Key: IGNITE-2173
 URL: https://issues.apache.org/jira/browse/IGNITE-2173
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.5
Reporter: Michael Griggs
Priority: Minor


e.g., line 1029

{code}
log.debug("Write entries to db one by one using update and insert statements 
[cache name=" +
{code}

A side-effect of this is WARNing messages in your log file when these 
statements are executed:

{code}
2015-12-15 16:19:26 WARN  CacheJdbcPojoStore:463 - Logging at DEBUG level 
without checking if DEBUG level is enabled: 
{code}




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

[jira] [Created] (IGNITE-2164) CPP: Namespace/class desciptions are missing in generated docs.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2164:
---

 Summary: CPP: Namespace/class desciptions are missing in generated 
docs.
 Key: IGNITE-2164
 URL: https://issues.apache.org/jira/browse/IGNITE-2164
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.5






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

Re: translate document into korean

[younggyu Chun]

Thanks for the invitation
here is a question. Which version of ignite document should be translated?

2015년 12월 15일 화요일, Dmitriy Setrakyan님이 작성한 메시지:

> Hi, Younggyu Chun!
>
> I have added you to the English documentation project on readme. I have
> also created an empty project for Korean documentation and sent you an
> invite as well.
>
> Give readme a shot and see if you like it. Let me know if you have any
> questions.
>
> D.
>
> On Tue, Dec 15, 2015 at 1:09 AM, younggyu Chun  >
> wrote:
>
> > hi Dmitriy Setrakyan
> >
> > readme.io will be good choice
> > i'm just planning to use the same format as english version documents did
> >
> > could you please create project in readmeio and give me english version
> > html for me?
> >
> > younggyu, chun
> >
> >
> >
> > 2015년 12월 15일 화요일, Dmitriy Setrakyan >님이 작성한 메시지:
> >
> > > Thanks, Younggyu Chun!
> > >
> > > This will be a great contribution.
> > >
> > > Feel free to choose the format for the documentation. For example, we
> can
> > > create a project for you in readme.io, like we have for the main
> Ignite
> > > documentation. Alternatively you may choose to do it directly in MD
> > format,
> > > and then use some tool to generate HTML pages, like Yujue Li chose for
> > the
> > > Chinese documentation here:
> > >
> > > https://www.zybuluo.com/liyuj/note/230739
> > >
> > > Let us know if we can help in any way. Whenever ready, we will add a
> link
> > > to the Korean documentation to the Ignite website.
> > >
> > > D.
> > >
> > > On Mon, Dec 14, 2015 at 11:44 PM, younggyu Chun <
> > younggyuchu...@gmail.com 
> > > >
> > > wrote:
> > >
> > > > Dear igniters
> > > >
> > > > I would like to translate the ignite documents in Korean as many
> > Koreans
> > > > recently are getting intereted in the ignite project. I introduced
> > > > my colleagues to the ignite, and then my colleagues are planning to
> use
> > > the
> > > > ignite as shared RDDs for spark and data grid instead of applying
> > Oracle
> > > > Coherence.
> > > >
> > > > I am sure that the ignite would become one of the most popular
> project
> > in
> > > > the near future in Korea so I would like to help many Koreans who are
> > > > strugging with reading documents written in English, which would
> > > > dramatically boost up the popularity of the ignite in Korea
> > > >
> > > > feel free to give any comment on translation
> > > >
> > > > Best Regards,
> > > > Younggyu, Chun
> > > >
> > >
> >
>

Re: translate document into korean

[Dmitriy Setrakyan]

Thanks, Younggyu Chun!

This will be a great contribution.

Feel free to choose the format for the documentation. For example, we can
create a project for you in readme.io, like we have for the main Ignite
documentation. Alternatively you may choose to do it directly in MD format,
and then use some tool to generate HTML pages, like Yujue Li chose for the
Chinese documentation here:

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

Let us know if we can help in any way. Whenever ready, we will add a link
to the Korean documentation to the Ignite website.

D.

On Mon, Dec 14, 2015 at 11:44 PM, younggyu Chun 
wrote:

> Dear igniters
>
> I would like to translate the ignite documents in Korean as many Koreans
> recently are getting intereted in the ignite project. I introduced
> my colleagues to the ignite, and then my colleagues are planning to use the
> ignite as shared RDDs for spark and data grid instead of applying Oracle
> Coherence.
>
> I am sure that the ignite would become one of the most popular project in
> the near future in Korea so I would like to help many Koreans who are
> strugging with reading documents written in English, which would
> dramatically boost up the popularity of the ignite in Korea
>
> feel free to give any comment on translation
>
> Best Regards,
> Younggyu, Chun
>

Re: translate document into korean

[Dmitriy Setrakyan]

Hi, Younggyu Chun!

I have added you to the English documentation project on readme. I have
also created an empty project for Korean documentation and sent you an
invite as well.

Give readme a shot and see if you like it. Let me know if you have any
questions.

D.

On Tue, Dec 15, 2015 at 1:09 AM, younggyu Chun 
wrote:

> hi Dmitriy Setrakyan
>
> readme.io will be good choice
> i'm just planning to use the same format as english version documents did
>
> could you please create project in readmeio and give me english version
> html for me?
>
> younggyu, chun
>
>
>
> 2015년 12월 15일 화요일, Dmitriy Setrakyan님이 작성한 메시지:
>
> > Thanks, Younggyu Chun!
> >
> > This will be a great contribution.
> >
> > Feel free to choose the format for the documentation. For example, we can
> > create a project for you in readme.io, like we have for the main Ignite
> > documentation. Alternatively you may choose to do it directly in MD
> format,
> > and then use some tool to generate HTML pages, like Yujue Li chose for
> the
> > Chinese documentation here:
> >
> > https://www.zybuluo.com/liyuj/note/230739
> >
> > Let us know if we can help in any way. Whenever ready, we will add a link
> > to the Korean documentation to the Ignite website.
> >
> > D.
> >
> > On Mon, Dec 14, 2015 at 11:44 PM, younggyu Chun <
> younggyuchu...@gmail.com
> > >
> > wrote:
> >
> > > Dear igniters
> > >
> > > I would like to translate the ignite documents in Korean as many
> Koreans
> > > recently are getting intereted in the ignite project. I introduced
> > > my colleagues to the ignite, and then my colleagues are planning to use
> > the
> > > ignite as shared RDDs for spark and data grid instead of applying
> Oracle
> > > Coherence.
> > >
> > > I am sure that the ignite would become one of the most popular project
> in
> > > the near future in Korea so I would like to help many Koreans who are
> > > strugging with reading documents written in English, which would
> > > dramatically boost up the popularity of the ignite in Korea
> > >
> > > feel free to give any comment on translation
> > >
> > > Best Regards,
> > > Younggyu, Chun
> > >
> >
>

[jira] [Created] (IGNITE-2166) .NET: Add toBuilder() method on BinaryObject interface.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2166:
---

 Summary: .NET: Add toBuilder() method on BinaryObject interface.
 Key: IGNITE-2166
 URL: https://issues.apache.org/jira/browse/IGNITE-2166
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.6


Port IGNITE-2138 to .NET.



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

Re: translate document into korean

[Alexey Kuznetsov]

Hi Younggyu, Chun!

Thats pretty cool! Thanks a lot for your help!

We already have translation to simplified chinese.

And I think we should do the same for Korean.
Take a look at this thread:
http://apache-ignite-developers.2346864.n4.nabble.com/about-apache-ignite-s-document-localization-Simplified-Chinese-td4497.html


On Tue, Dec 15, 2015 at 2:44 PM, younggyu Chun 
wrote:

> Dear igniters
>
> I would like to translate the ignite documents in Korean as many Koreans
> recently are getting intereted in the ignite project. I introduced
> my colleagues to the ignite, and then my colleagues are planning to use the
> ignite as shared RDDs for spark and data grid instead of applying Oracle
> Coherence.
>
> I am sure that the ignite would become one of the most popular project in
> the near future in Korea so I would like to help many Koreans who are
> strugging with reading documents written in English, which would
> dramatically boost up the popularity of the ignite in Korea
>
> feel free to give any comment on translation
>
> Best Regards,
> Younggyu, Chun
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-2163) CPP: ODBC driver supported version should be upgraded to 3.x

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2163:
---

 Summary: CPP: ODBC driver supported version should be upgraded to 
3.x
 Key: IGNITE-2163
 URL: https://issues.apache.org/jira/browse/IGNITE-2163
 Project: Ignite
  Issue Type: Task
Reporter: Igor Sapego
Assignee: Igor Sapego


Currently our implementation of the ODBC driver states that it supports ODBC 
standard version 2.0. It seems that many features that Tablue uses are not 
supported in this version of the ODBC. So we need to set our version to 3.x and 
make sure it works.



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

Re: Using HDFS as a secondary FS

[Denis Magda]

Hi Ivan,

Thanks for clarification.

Actually I’ve modified the content of the following pages:

- Added “Atomatic Hadoop Configuration” section that describes the usage of 
setup-hadoop with all its pros and cons for Apache Hadoop and CDH
http://apacheignite.gridgain.org/v1.5/docs/installing-on-apache-hadoop#automatic-hadoop-configuration
http://apacheignite.gridgain.org/docs/installing-on-cloudera-cdh

- Provided more info on how to use ‘HDFS’ as a secondary file system for ‘IGFS’ 
using your yesterday answer and referring to the updated configuration guides
http://apacheignite.gridgain.org/docs/secondary-file-system

Please as an IGFS & Hadoop expert review my changes and edit them whenever 
required.

In addition I noted that we have a disabled and empty article for BigTop 
distribution. Is this OK?

—
Denis

> On 15 дек. 2015 г., at 12:10, Ivan V.  wrote:
> 
> Denis, good question.
> Yes, there are several reasons.
> 1) setup-hadoop is suitable for Apache Hadoop distribution, but not for all
> others (e.g. BigTop)
> 2) setup-hadoop rewrites global configs (core-site.xml, mapred-site.xml),
> what prevents further cluster usage without Ignite.
> 3) setup-hadoop needs write permission to all the folders it writes files
> to.
> 4) It is possible to provide all the required functionality without any
> file modifications in the existing Hadoop cluster at all, see
> https://issues.apache.org/jira/browse/IGNITE-483.
> 
> There were plans to remove "setup-hadoop", but that is not yet done.
> In any way, I 100% agree that presence of several different versions of the
> documentation is quite confusing and misleading.
> 
> 
> On Mon, Dec 14, 2015 at 10:58 PM, Denis Magda  wrote:
> 
>> Ivan,
>> 
>> Is there any reason why we don’t recommend using
>> apache-ignite-hadoop-{version}/bin/setup-hadoop.sh/bat in our Hadooop
>> Accelerator articles?
>> 
>> With setup-hadoop.sh I was able to build a valid classpath, create
>> symlinks to the accelerator's jars from hadoop’s libs folder automatically
>> and started an Ignite node that uses HDFS as a secondary FS in less than 10
>> minutes.
>> 
>> I just followed the instructions from
>> apache-ignite-hadoop-{version}/HADOOP_README.txt. Instructions from the
>> readme.io  look much more complex for me, they don’t
>> mention setup-hadoop.sh/bat at all making the end user to perform a
>> manual setup.
>> 
>> —
>> Denis
>> 
>>> On 14 дек. 2015 г., at 20:24, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> On Mon, Dec 14, 2015 at 7:28 AM, Denis Magda 
>> wrote:
>>> 
 Yes, this will be documented tomorrow. I want to go though all the steps
 by myself checking all other possible obstacles the user may face with.
 
>>> 
>>> Thanks, Denis!
>>> 
>>> 
 
 —
 Denis
 
> On 14 дек. 2015 г., at 18:11, Dmitriy Setrakyan >> 
 wrote:
> 
> Ivan, I think this should be documented, no?
> 
> On Mon, Dec 14, 2015 at 2:25 AM, Ivan V. 
 wrote:
> 
>> To enable just an IGFS persistence there is no need to use HDFS (this
>> requires Hadoop dependency, requires configured HDFS cluster, etc.).
>> We have requests https://issues.apache.org/jira/browse/IGNITE-1120 ,
>> https://issues.apache.org/jira/browse/IGNITE-1926 to implement the
>> persistence upon local file system, and we already close to  the
 solution.
>> 
>> Regarding the secondary Fs doc page (
>> http://apacheignite.gridgain.org/docs/secondary-file-system) I would
>> suggest to add the following text there:
>> 
>> If Ignite node with secondary file system configured on a machine with
>> Hadoop distribution, make sure Ignite is able to find appropriate
>> Hadoop
>> libraries: set HADOOP_HOME environment variable for the Ignite process
 if
>> you're using Apache Hadoop distribution, or, if you use another
>> distribution (HDP, Cloudera, BigTop, etc.) make sure
>> /etc/default/hadoop
>> file exists and has appropriate contents.
>> 
>> If Ignite node with secondary file system configured on a machine
 without
>> Hadoop distribution, you can manually add necessary Hadoop
>> dependencies
 to
>> Ignite node classpath: these are dependencies of groupId
>> "org.apache.hadoop" listed in file modules/hadoop/pom.xml . Currently
 they
>> are:
>> 
>> 1. hadoop-annotations
>> 2. hadoop-auth
>> 3. hadoop-common
>> 4. hadoop-hdfs
>> 5. hadoop-mapreduce-client-common
>> 6. hadoop-mapreduce-client-core
>> 
>> 
>> 
>> On Mon, Dec 14, 2015 at 11:21 AM, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>> 
>>> Guys,
>>> 
>>> Why don't we include ignite-hadoop module in Fabric? This user simply
>> wants
>>> to configure 

[GitHub] ignite pull request: Ignite 2016: Kafka Connect Integration

[shroman]

GitHub user shroman opened a pull request:

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

Ignite 2016: Kafka Connect Integration

Kafka Connect is a new standard method "for scalably and reliably streaming 
data between Apache Kafka and other systems" from the latest Kafka 0.9.0.

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

$ git pull https://github.com/shroman/ignite ignite-2016

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

https://github.com/apache/ignite/pull/335.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #335


commit 098a208309274619595347ee45cfb517e3d98214
Author: shtykh_roman 
Date:   2015-12-15T06:55:04Z

IGNITE-2016: Kafka Connect integration

commit 6925406de8e4d76abed959f557a48914e1c6c77a
Author: shtykh_roman 
Date:   2015-12-15T09:57:39Z

IGNITE-2016: Check for null key -- not allowed in Ignite

commit c474cb76c560d2a987bbfa530c145c210674e82c
Author: shtykh_roman 
Date:   2015-12-15T10:03:08Z

IGNITE-2016: Added README




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: Ignite-2106

[avinogradovgg]

Github user avinogradovgg closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-2159: Implemented 64-bit atomics with ...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-2159: Implemented 64-bit atomics with supported functions.



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

$ git pull https://github.com/isapego/ignite ignite-2159

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

https://github.com/apache/ignite/pull/336.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #336


commit 19abcd547ba1d35fc28719726f1e4881c02e9cda
Author: isapego 
Date:   2015-12-15T10:24:34Z

IGNITE-2159: IMplemented 64-bit atomics with supported functions.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-2164: Added documentation brief descri...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-2164: Added documentation brief description auto generation.



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

$ git pull https://github.com/isapego/ignite ignite-2164

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

https://github.com/apache/ignite/pull/337.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #337


commit 2962d92002e08717abcd1fe3e9f97017ed5a3a41
Author: isapego 
Date:   2015-12-15T10:51:33Z

IGNITE-2164: Added documentation brief description autogeneration.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

store examples

[Yakov Zhdanov]

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

Guys,

It seems that CacheDummyStoreExample, CacheJdbcStoreExample and
CacheSpringStoreExample do not work correctly in distributed environment
after code modifications to demonstrate clear() and withSkipStore()

This is an old issue and it is 100% examples' issue, so I suggest removing
them from 1.5 and fix and return back to distro in 1.6

Thoughts?

--Yakov

[GitHub] ignite pull request: IGNITE-1994 .Net: CrossPlatformExample looks ...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-1994 .Net: CrossPlatformExample looks unnecessary



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

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

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

https://github.com/apache/ignite/pull/338.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #338


commit 98c73e6073e64b31e24fa277dafcd7d7692dfd64
Author: Pavel Tupitsyn 
Date:   2015-12-15T12:13:21Z

IGNITE-1994 .Net: CrossPlatformExample looks unnecessary




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: ignite-2065

[ashutakGG]

Github user ashutakGG closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: store examples

[Dmitriy Setrakyan]

I think we should fix all the examples. What has changed that makes these
examples so difficult to fix?

I really do not like removing the examples that have been continuously
shipped in every release. If it is so difficult for us to upgrade them to
1.5, how difficult will it be for our users?

D.

On Tue, Dec 15, 2015 at 7:24 AM, Yakov Zhdanov  wrote:

> We still have very advanced and cool CacheBinaryAutoStoreExample and it
> works properly
>
> --Yakov
>
> 2015-12-15 18:11 GMT+03:00 Dmitriy Setrakyan :
>
> > If it is an example issue, why can’t we fix the examples? I am not
> > comfortable removing CacheJdbcStoreExample from the release.
> >
> > On Tue, Dec 15, 2015 at 4:02 AM, Yakov Zhdanov 
> > wrote:
> >
> > > https://issues.apache.org/jira/browse/IGNITE-2158
> > >
> > > Guys,
> > >
> > > It seems that CacheDummyStoreExample, CacheJdbcStoreExample and
> > > CacheSpringStoreExample do not work correctly in distributed
> environment
> > > after code modifications to demonstrate clear() and withSkipStore()
> > >
> > > This is an old issue and it is 100% examples' issue, so I suggest
> > removing
> > > them from 1.5 and fix and return back to distro in 1.6
> > >
> > > Thoughts?
> > >
> > > --Yakov
> > >
> >
>

Re: store examples

[Dmitriy Setrakyan]

If the problem is the H2 in-memory store not being shared between multiple
Ignite nodes, then why not switch to using H2 disk store?

On Tue, Dec 15, 2015 at 4:11 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> As far as I understand, the issue is that CacheJdbcStoreExample
> and CacheSpringStoreExample use in-memory H2 database, so the cache store
> is not shared among nodes. What if we just switch to a file-based DB? It
> looks like a simple change to me.
>
> And I would remove CacheDummyStoreExample. It looks weird and doesn't
> demonstrate anything that is not shown in other store examples.
>
> -Val
>
> On Tue, Dec 15, 2015 at 2:03 PM, Dmitriy Setrakyan 
> wrote:
>
> > I think we should fix all the examples. What has changed that makes these
> > examples so difficult to fix?
> >
> > I really do not like removing the examples that have been continuously
> > shipped in every release. If it is so difficult for us to upgrade them to
> > 1.5, how difficult will it be for our users?
> >
> > D.
> >
> > On Tue, Dec 15, 2015 at 7:24 AM, Yakov Zhdanov 
> > wrote:
> >
> > > We still have very advanced and cool CacheBinaryAutoStoreExample and it
> > > works properly
> > >
> > > --Yakov
> > >
> > > 2015-12-15 18:11 GMT+03:00 Dmitriy Setrakyan :
> > >
> > > > If it is an example issue, why can’t we fix the examples? I am not
> > > > comfortable removing CacheJdbcStoreExample from the release.
> > > >
> > > > On Tue, Dec 15, 2015 at 4:02 AM, Yakov Zhdanov 
> > > > wrote:
> > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-2158
> > > > >
> > > > > Guys,
> > > > >
> > > > > It seems that CacheDummyStoreExample, CacheJdbcStoreExample and
> > > > > CacheSpringStoreExample do not work correctly in distributed
> > > environment
> > > > > after code modifications to demonstrate clear() and withSkipStore()
> > > > >
> > > > > This is an old issue and it is 100% examples' issue, so I suggest
> > > > removing
> > > > > them from 1.5 and fix and return back to distro in 1.6
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > --Yakov
> > > > >
> > > >
> > >
> >
>

Re: Mandatory requirement to run ExampleNodeStartup only for a several examples

[Ilya Suntsov]

Guys,
I've re-checked these examples. Most of the benchmarks corresponding to the
description that was provided by Yakov above but the following examples
don't work with remote nodes started with server classpath :

   - org.apache.ignite.examples.datagrid.CacheQueryExample
   - org.apache.ignite.examples.streaming.StreamVisitorExample
   - org.apache.ignite.examples.java8.streaming.StreamTransformerExample
   - org.apache.ignite.examples.java8.streaming.StreamVisitorExample


2015-12-14 17:53 GMT+03:00 Yakov Zhdanov :

> Guys,
>
> There is currently a limitation - we cannot effectively deploy class
> definitions over discovery protocol. This is possible to fix, but needs
> some more investigation.
>
> As far as current situation with examples, I think that the following
> examples should work with remote nodes started with server classpath
> (yes/no). Sergey, can you please check if my vision is correct and let us
> know:
>
> Java
> Y: org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample
> Y: org.apache.ignite.examples.datagrid.starschema.CacheStarSchemaExample
> N: org.apache.ignite.examples.datagrid.store.auto.CacheAutoStoreExample
> N: org.apache.ignite.examples.datagrid.store.dummy.CacheDummyStoreExample
> N: org.apache.ignite.examples.datagrid.store.jdbc.CacheJdbcStoreExample
> N: org.apache.ignite.examples.datagrid.store.spring.CacheSpringStoreExample
> Y: org.apache.ignite.examples.datagrid.CacheQueryExample
> N: org.apache.ignite.examples.servicegrid.ServicesExample - service cannot
> be peer deployed now
> Y: org.apache.ignite.examples.streaming.StreamTransformerExample
> Y: org.apache.ignite.examples.streaming.StreamVisitorExample
> Y: org.apache.ignite.examples.streaming.org.apache.ignite.
> examples.streaming.wordcount.QueryWords
> Y: org.apache.ignite.examples.streaming.org.apache.ignite.
> examples.streaming.wordcount.StreamWords
>
> Scala
> Y: org.apache.ignite.scalar.examples.ScalarCacheQueryExample
> Y: org.apache.ignite.scalar.examples.ScalarSnowflakeSchemaExample
>
> Java8
> Y: org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> Y: org.apache.ignite.examples.java8.streaming.StreamVisitorExample
>
> LGPL:
> N: org.apache.ignite.examples.datagrid.store.hibernate.
> CacheHibernateStoreExample
> --Yakov
>
> 2015-12-12 5:23 GMT+03:00 Alexey Kuznetsov :
>
> > Dmitriy,
> >
> > As far as I know P2P works mainly for Compute
> > See: https://apacheignite.readme.io/v1.5/docs/zero-deployment
> >
> > On Sat, Dec 12, 2015 at 4:47 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Why are we not allowing to deploy factory classes over P2P deployment?
> > >
> > > On Fri, Dec 11, 2015 at 7:29 AM, Alexey Kuznetsov <
> > akuznet...@gridgain.com
> > > >
> > > wrote:
> > >
> > > > I can confirm examples developed/changed by me.
> > > >
> > > > >>
> org.apache.ignite.examples.datagrid.store.auto.CacheAutoStoreExample
> > > > DO NOT ALLOW to start remote nodes via ignite.sh out of the box, but
> if
> > > > user put example cache store factory class into \libs folder example
> > will
> > > > run.
> > > >
> > > > >>
> > > >
> > > >
> > >
> >
> org.apache.ignite.examples.binary.datagrid.store.auto.CacheBinaryAutoStoreExample
> > > > This example ALLOW to start remote nodes via ignite.sh.
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>



-- 
Ilya Suntsov

[jira] [Created] (IGNITE-2174) Error with owerwrite dialog on loading metadata from DB

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2174:
--

 Summary: Error with owerwrite dialog on loading metadata from DB
 Key: IGNITE-2174
 URL: https://issues.apache.org/jira/browse/IGNITE-2174
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov


To reproduce just try to load the same metadata twice.



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

Re: Using HDFS as a secondary FS

[Ivan V.]

Hi, Denis,
1) my opinion is that we'd better not mention 'setup-hadoop' script at all
(for the reasons mentioned above) and delete it in the nearest release.
2) Now Ignite is a part of BigTop distribution (see
https://issues.apache.org/jira/browse/IGNITE-665), so the old BigTop
instruction is not relevant any more. I guess, this is the reason.


On Tue, Dec 15, 2015 at 12:35 PM, Denis Magda  wrote:

> Hi Ivan,
>
> Thanks for clarification.
>
> Actually I’ve modified the content of the following pages:
>
> - Added “Atomatic Hadoop Configuration” section that describes the usage
> of setup-hadoop with all its pros and cons for Apache Hadoop and CDH
>
> http://apacheignite.gridgain.org/v1.5/docs/installing-on-apache-hadoop#automatic-hadoop-configuration
> http://apacheignite.gridgain.org/docs/installing-on-cloudera-cdh
>
> - Provided more info on how to use ‘HDFS’ as a secondary file system for
> ‘IGFS’ using your yesterday answer and referring to the updated
> configuration guides
> http://apacheignite.gridgain.org/docs/secondary-file-system
>
> Please as an IGFS & Hadoop expert review my changes and edit them whenever
> required.
>
> In addition I noted that we have a disabled and empty article for BigTop
> distribution. Is this OK?
>
> —
> Denis
>
> > On 15 дек. 2015 г., at 12:10, Ivan V.  wrote:
> >
> > Denis, good question.
> > Yes, there are several reasons.
> > 1) setup-hadoop is suitable for Apache Hadoop distribution, but not for
> all
> > others (e.g. BigTop)
> > 2) setup-hadoop rewrites global configs (core-site.xml, mapred-site.xml),
> > what prevents further cluster usage without Ignite.
> > 3) setup-hadoop needs write permission to all the folders it writes files
> > to.
> > 4) It is possible to provide all the required functionality without any
> > file modifications in the existing Hadoop cluster at all, see
> > https://issues.apache.org/jira/browse/IGNITE-483.
> >
> > There were plans to remove "setup-hadoop", but that is not yet done.
> > In any way, I 100% agree that presence of several different versions of
> the
> > documentation is quite confusing and misleading.
> >
> >
> > On Mon, Dec 14, 2015 at 10:58 PM, Denis Magda 
> wrote:
> >
> >> Ivan,
> >>
> >> Is there any reason why we don’t recommend using
> >> apache-ignite-hadoop-{version}/bin/setup-hadoop.sh/bat in our Hadooop
> >> Accelerator articles?
> >>
> >> With setup-hadoop.sh I was able to build a valid classpath, create
> >> symlinks to the accelerator's jars from hadoop’s libs folder
> automatically
> >> and started an Ignite node that uses HDFS as a secondary FS in less
> than 10
> >> minutes.
> >>
> >> I just followed the instructions from
> >> apache-ignite-hadoop-{version}/HADOOP_README.txt. Instructions from the
> >> readme.io  look much more complex for me, they don’t
> >> mention setup-hadoop.sh/bat at all making the end user to perform a
> >> manual setup.
> >>
> >> —
> >> Denis
> >>
> >>> On 14 дек. 2015 г., at 20:24, Dmitriy Setrakyan  >
> >> wrote:
> >>>
> >>> On Mon, Dec 14, 2015 at 7:28 AM, Denis Magda 
> >> wrote:
> >>>
>  Yes, this will be documented tomorrow. I want to go though all the
> steps
>  by myself checking all other possible obstacles the user may face
> with.
> 
> >>>
> >>> Thanks, Denis!
> >>>
> >>>
> 
>  —
>  Denis
> 
> > On 14 дек. 2015 г., at 18:11, Dmitriy Setrakyan <
> dsetrak...@apache.org
> >>>
>  wrote:
> >
> > Ivan, I think this should be documented, no?
> >
> > On Mon, Dec 14, 2015 at 2:25 AM, Ivan V. 
>  wrote:
> >
> >> To enable just an IGFS persistence there is no need to use HDFS
> (this
> >> requires Hadoop dependency, requires configured HDFS cluster, etc.).
> >> We have requests https://issues.apache.org/jira/browse/IGNITE-1120
> ,
> >> https://issues.apache.org/jira/browse/IGNITE-1926 to implement the
> >> persistence upon local file system, and we already close to  the
>  solution.
> >>
> >> Regarding the secondary Fs doc page (
> >> http://apacheignite.gridgain.org/docs/secondary-file-system) I
> would
> >> suggest to add the following text there:
> >> 
> >> If Ignite node with secondary file system configured on a machine
> with
> >> Hadoop distribution, make sure Ignite is able to find appropriate
> >> Hadoop
> >> libraries: set HADOOP_HOME environment variable for the Ignite
> process
>  if
> >> you're using Apache Hadoop distribution, or, if you use another
> >> distribution (HDP, Cloudera, BigTop, etc.) make sure
> >> /etc/default/hadoop
> >> file exists and has appropriate contents.
> >>
> >> If Ignite node with secondary file system configured on a machine
>  without
> >> Hadoop distribution, you can manually add necessary Hadoop
> >> dependencies

Abandoned ticket: Provide Integration with Spring Data [IGNITE-1192]

[Denis Magda]

Hi Vikrant,

Do you have free time to complete the integration in the nearest month?

This integration is becoming quite urgent. So if you don’t have time for now 
someone else from the community will pick this ticket up.

Regards,
Denis

Re: translate document into korean

[Dmitriy Setrakyan]

Hi, Younggyu Chun.

You should translate the latest version, which is 1.5.

When we move to the next version, you can translate only the changes. All
the documentation changes are recorded in the Ignite Documentation GIT
Repository on GitHub:

https://github.com/apacheignite/documentation

D.

On Tue, Dec 15, 2015 at 1:46 AM, younggyu Chun 
wrote:

> Thanks for the invitation
> here is a question. Which version of ignite document should be translated?
>
> 2015년 12월 15일 화요일, Dmitriy Setrakyan님이 작성한 메시지:
>
> > Hi, Younggyu Chun!
> >
> > I have added you to the English documentation project on readme. I have
> > also created an empty project for Korean documentation and sent you an
> > invite as well.
> >
> > Give readme a shot and see if you like it. Let me know if you have any
> > questions.
> >
> > D.
> >
> > On Tue, Dec 15, 2015 at 1:09 AM, younggyu Chun  > >
> > wrote:
> >
> > > hi Dmitriy Setrakyan
> > >
> > > readme.io will be good choice
> > > i'm just planning to use the same format as english version documents
> did
> > >
> > > could you please create project in readmeio and give me english version
> > > html for me?
> > >
> > > younggyu, chun
> > >
> > >
> > >
> > > 2015년 12월 15일 화요일, Dmitriy Setrakyan > >님이 작성한 메시지:
> > >
> > > > Thanks, Younggyu Chun!
> > > >
> > > > This will be a great contribution.
> > > >
> > > > Feel free to choose the format for the documentation. For example, we
> > can
> > > > create a project for you in readme.io, like we have for the main
> > Ignite
> > > > documentation. Alternatively you may choose to do it directly in MD
> > > format,
> > > > and then use some tool to generate HTML pages, like Yujue Li chose
> for
> > > the
> > > > Chinese documentation here:
> > > >
> > > > https://www.zybuluo.com/liyuj/note/230739
> > > >
> > > > Let us know if we can help in any way. Whenever ready, we will add a
> > link
> > > > to the Korean documentation to the Ignite website.
> > > >
> > > > D.
> > > >
> > > > On Mon, Dec 14, 2015 at 11:44 PM, younggyu Chun <
> > > younggyuchu...@gmail.com 
> > > > >
> > > > wrote:
> > > >
> > > > > Dear igniters
> > > > >
> > > > > I would like to translate the ignite documents in Korean as many
> > > Koreans
> > > > > recently are getting intereted in the ignite project. I introduced
> > > > > my colleagues to the ignite, and then my colleagues are planning to
> > use
> > > > the
> > > > > ignite as shared RDDs for spark and data grid instead of applying
> > > Oracle
> > > > > Coherence.
> > > > >
> > > > > I am sure that the ignite would become one of the most popular
> > project
> > > in
> > > > > the near future in Korea so I would like to help many Koreans who
> are
> > > > > strugging with reading documents written in English, which would
> > > > > dramatically boost up the popularity of the ignite in Korea
> > > > >
> > > > > feel free to give any comment on translation
> > > > >
> > > > > Best Regards,
> > > > > Younggyu, Chun
> > > > >
> > > >
> > >
> >
>

Re: store examples

[Alexey Kuznetsov]

I think mentioned examples could be easily fixed by switching from use of
H2 started from example to o.a.i.examples.util.DbH2ServerStartup.
This will start full fledged H2 server with in-memory db and all nodes will
work with it.

>> Ignite nodes, then why not switch to using H2 disk store?
Dima, this would not work, because file will be locked by first started
process and other will failed.

I think we should go as I mentioned above.


On Wed, Dec 16, 2015 at 7:23 AM, Dmitriy Setrakyan 
wrote:

> If the problem is the H2 in-memory store not being shared between multiple
> Ignite nodes, then why not switch to using H2 disk store?
>
> On Tue, Dec 15, 2015 at 4:11 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > As far as I understand, the issue is that CacheJdbcStoreExample
> > and CacheSpringStoreExample use in-memory H2 database, so the cache store
> > is not shared among nodes. What if we just switch to a file-based DB? It
> > looks like a simple change to me.
> >
> > And I would remove CacheDummyStoreExample. It looks weird and doesn't
> > demonstrate anything that is not shown in other store examples.
> >
> > -Val
> >
> > On Tue, Dec 15, 2015 at 2:03 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > I think we should fix all the examples. What has changed that makes
> these
> > > examples so difficult to fix?
> > >
> > > I really do not like removing the examples that have been continuously
> > > shipped in every release. If it is so difficult for us to upgrade them
> to
> > > 1.5, how difficult will it be for our users?
> > >
> > > D.
> > >
> > > On Tue, Dec 15, 2015 at 7:24 AM, Yakov Zhdanov 
> > > wrote:
> > >
> > > > We still have very advanced and cool CacheBinaryAutoStoreExample and
> it
> > > > works properly
> > > >
> > > > --Yakov
> > > >
> > > > 2015-12-15 18:11 GMT+03:00 Dmitriy Setrakyan  >:
> > > >
> > > > > If it is an example issue, why can’t we fix the examples? I am not
> > > > > comfortable removing CacheJdbcStoreExample from the release.
> > > > >
> > > > > On Tue, Dec 15, 2015 at 4:02 AM, Yakov Zhdanov <
> yzhda...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > https://issues.apache.org/jira/browse/IGNITE-2158
> > > > > >
> > > > > > Guys,
> > > > > >
> > > > > > It seems that CacheDummyStoreExample, CacheJdbcStoreExample and
> > > > > > CacheSpringStoreExample do not work correctly in distributed
> > > > environment
> > > > > > after code modifications to demonstrate clear() and
> withSkipStore()
> > > > > >
> > > > > > This is an old issue and it is 100% examples' issue, so I suggest
> > > > > removing
> > > > > > them from 1.5 and fix and return back to distro in 1.6
> > > > > >
> > > > > > Thoughts?
> > > > > >
> > > > > > --Yakov
> > > > > >
> > > > >
> > > >
> > >
> >
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-2172) Uneven API between IgniteMessaging#stopRemoteListen and #stopLocalListen

[JIRA]

Raúl Kripalani created IGNITE-2172:
--

 Summary: Uneven API between IgniteMessaging#stopRemoteListen and 
#stopLocalListen
 Key: IGNITE-2172
 URL: https://issues.apache.org/jira/browse/IGNITE-2172
 Project: Ignite
  Issue Type: Improvement
  Components: messaging
Affects Versions: 1.5
Reporter: Raúl Kripalani


Compare:

{code}
UUID remoteListen(@Nullable Object topic, IgniteBiPredicate p)
{code}

vs.

{code}
void stopLocalListen(@Nullable Object topic, IgniteBiPredicate p)
{code}

It would be nice to identify local listeners with an UUID too.



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

[jira] [Created] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2175:


 Summary: Not valid exceptions in case when example can't works 
with remote node started with server classpath (Java 7)
 Key: IGNITE-2175
 URL: https://issues.apache.org/jira/browse/IGNITE-2175
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
 Environment: jdk 1.7
OS X 10.10.2
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov
Priority: Critical
 Fix For: 1.5


Steps for reproduce:
1. Start one node form IDEA and one more from terminal
2. Run StreamVisitorExample.
Got exception:
{noformat}
16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
update job.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
at 
org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
at 
org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
at 
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
... 13 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:274)
at 
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1443)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:116)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:280)
at 

[GitHub] ignite pull request: IGNITE-2152 .NET: Introduction page is missin...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-2152 .NET: Introduction page is missing.



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

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

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

https://github.com/apache/ignite/pull/339.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #339


commit 1b2d64d2000282c85fdcad4b8f75601cd96fdbc5
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:46:06Z

IGNITE-2152 .NET: Introduction page is missing.

commit 30657ac100f761a0c77bd26359c921850ca9980d
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:49:21Z

wip

commit f49e7028e79770d780f6f3dc6065ce68acfc1ca2
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:52:19Z

wip




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---