[jira] [Created] (IGNITE-2134) .Net: Query configuration via attributes

Pavel Tupitsyn created IGNITE-2134: -- Summary: .Net: Query configuration via attributes Key: IGNITE-2134 URL: https://issues.apache.org/jira/browse/IGNITE-2134 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2135) ClassNotFoundException for CacheContinuousQueryExample

Sergey Kozlov created IGNITE-2135: - Summary: ClassNotFoundException for CacheContinuousQueryExample Key: IGNITE-2135 URL: https://issues.apache.org/jira/browse/IGNITE-2135 Project: Ignite

Re: BinaryObjectBuilder in EntryProcessor

how about "toBuilder()"? --Yakov 2015-12-11 13:02 GMT+03:00 Alexey Goncharuk : > Igniters, > > I was creating an example showing how to use BinaryObjects and > EntryProcessor for the case when server nodes do not have cache classes > definitions and realized that

[jira] [Created] (IGNITE-2133) Schema Import Utility should print warning about wrong IGNITE_HOME

Alexey Kuznetsov created IGNITE-2133: Summary: Schema Import Utility should print warning about wrong IGNITE_HOME Key: IGNITE-2133 URL: https://issues.apache.org/jira/browse/IGNITE-2133 Project:

[GitHub] ignite pull request: IGNITE-2125 added common directive to show di...

GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/320 IGNITE-2125 added common directive to show dialog message, apllied on pages You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite

Re: BinaryObjectBuilder in EntryProcessor

On Fri, Dec 11, 2015 at 3:44 AM, Yakov Zhdanov wrote: > how about "toBuilder()"? > I like it. Also, does it make sense to pass a copy of the BinaryObject into the EntryProcessor? > > --Yakov > > 2015-12-11 13:02 GMT+03:00 Alexey Goncharuk : > >

[jira] [Created] (IGNITE-2139) Expose indexing metrics using MBean

Vladimir Ershov created IGNITE-2139: --- Summary: Expose indexing metrics using MBean Key: IGNITE-2139 URL: https://issues.apache.org/jira/browse/IGNITE-2139 Project: Ignite Issue Type: Task

[GitHub] ignite pull request: IGNITE-2082: Added docs generation for the CP...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/322 IGNITE-2082: Added docs generation for the CPP. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2082 Alternatively you

Re: BinaryObjectBuilder in EntryProcessor

> > I like it. I will add this method if there will be no objections. > Also, does it make sense to pass a copy of the BinaryObject into > the EntryProcessor? I am not sure I understood the question correctly. We never copy BinaryObject since it is immutable.

[jira] [Created] (IGNITE-2137) CacheAutoStoreExample fails with ClassNotFoundException

Sergey Kozlov created IGNITE-2137: - Summary: CacheAutoStoreExample fails with ClassNotFoundException Key: IGNITE-2137 URL: https://issues.apache.org/jira/browse/IGNITE-2137 Project: Ignite

[GitHub] ignite pull request: ignite-2065: rename classes

Github user ashutakGG closed the pull request at: https://github.com/apache/ignite/pull/321 --- 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

[GitHub] ignite pull request: Ignite-2065

GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/325 Ignite-2065 https://issues.apache.org/jira/browse/IGNITE-2065 The rest of portable -> binary renaming: methods, javadoc and etc. You can merge this pull request into a Git repository by

[GitHub] ignite pull request: IGNITE-1979 Support case insensitive nonquote...

GitHub user VladimirErshov opened a pull request: https://github.com/apache/ignite/pull/324 IGNITE-1979 Support case insensitive nonquoted cache names in SQL IGNITE-1979 Support case insensitive nonquoted cache names in SQL You can merge this pull request into a Git repository by

Re: Client connect "hangs"

I agree that we have a consistency issue here. I am OK with the change. On Fri, Dec 11, 2015 at 11:43 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Folks, > > Currently there are two different ways how a client node behaves in case > there are no server nodes: > >1. If

Re: Client connect "hangs"

Dmitry, How do you think, should we just change the behavior or make it configurable? -Val On Fri, Dec 11, 2015 at 1:59 PM, Dmitriy Setrakyan wrote: > I agree that we have a consistency issue here. I am OK with the change. > > On Fri, Dec 11, 2015 at 11:43 AM, Valentin

CacheLoadOnlyStoreAdapter

Igniters, We have a class that is called CacheLoadOnlyStoreAdapter. This is a cache store adapter that implements utility logic for multithreaded data loading, so that user has to provide only the logic that queries DB and parses DB row into object. Everything else is done automatically. It's a

Using HDFS as a secondary FS

Igniters, I'm looking at the question on SO [1] and I'm a bit confused. We ship ignite-hadoop module only in Hadoop Accelerator and without Hadoop JARs, assuming that user will include them from the Hadoop distribution he uses. It seems OK for me when accelerator is plugged in to Hadoop to run

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

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

[GitHub] ignite pull request: IGNITE-1906 .Net: Ignite configuration withou...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/319 IGNITE-1906 .Net: Ignite configuration without Spring You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1906

Client connect "hangs"

Folks, Currently there are two different ways how a client node behaves in case there are no server nodes: 1. If it's trying to start, it will wait and block the thread that called Ignition.start(). 2. If server nodes left when it was already running, it will throw disconnect

[jira] [Created] (IGNITE-2131) NPE in GridJobProcessor

Alexey Kuznetsov created IGNITE-2131: Summary: NPE in GridJobProcessor Key: IGNITE-2131 URL: https://issues.apache.org/jira/browse/IGNITE-2131 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2142) CPP: Move ODBC MSVS projects to separate solution.

Igor Sapego created IGNITE-2142: --- Summary: CPP: Move ODBC MSVS projects to separate solution. Key: IGNITE-2142 URL: https://issues.apache.org/jira/browse/IGNITE-2142 Project: Ignite Issue

[jira] [Created] (IGNITE-2141) Cleanup ODBC configuration.

Igor Sapego created IGNITE-2141: --- Summary: Cleanup ODBC configuration. Key: IGNITE-2141 URL: https://issues.apache.org/jira/browse/IGNITE-2141 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2132) Start test-drive on agent from web

Andrey Novikov created IGNITE-2132: -- Summary: Start test-drive on agent from web Key: IGNITE-2132 URL: https://issues.apache.org/jira/browse/IGNITE-2132 Project: Ignite Issue Type: Sub-task