[jira] [Created] (IGNITE-2251) Please add a tooltip on Client Summary on POJO tab...

Pavel Konstantinov created IGNITE-2251: -- Summary: Please add a tooltip on Client Summary on POJO tab... Key: IGNITE-2251 URL: https://issues.apache.org/jira/browse/IGNITE-2251 Project: Ignite

[jira] [Created] (IGNITE-2250) Client section on Summary contains ServerConfigurationFactory java class

Pavel Konstantinov created IGNITE-2250: -- Summary: Client section on Summary contains ServerConfigurationFactory java class Key: IGNITE-2250 URL: https://issues.apache.org/jira/browse/IGNITE-2250

[GitHub] ignite pull request: IGNITE-2220 added support to eslint

GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/365 IGNITE-2220 added support to eslint You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite ignite-2220 Alternatively you can review

Re: Dynamic caches creation

>>Basically, I am trying to think of how to make this whole thing more >>user-friendly and less middleware developers oriented. Wouldn't it be great if >>a user can load some external data and immediately start playing with it and >>doing some OLAP or even - oh horror :) - OLTP on it? I will descr

Re: 1.5.final

I closed one, Left: IGNITE-2175 Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7) On Wed, Dec 23, 2015 at 9:22 AM, Vladimir Ozerov wrote: > I closed my ticket. There was a problem in test preventing compilation with > Java 8. > > On We

Re: Dynamic caches creation

Cos, As far as schema-on-read, you can set all your caches in XML configuration, and they will be pre-created for you. Will this do the trick? D. On Tue, Dec 22, 2015 at 7:30 PM, Konstantin Boudnik wrote: > On Tue, Dec 22, 2015 at 03:45PM, Alexey Kuznetsov wrote: > > Cos, > > > > How you are g

Re: 1.5.final

I closed my ticket. There was a problem in test preventing compilation with Java 8. On Wed, Dec 23, 2015 at 4:54 AM, Dmitriy Setrakyan wrote: > As of today, there are still 4 tickets open: > http://s.apache.org/ignite-1.5.0.final > > Anton - 2 tickets > Vladimir - 1 ticket > Alexey - 1 ticket >

Re: sqlSchema usability question

1. You are actually never use cache name in SQL, you are always use schema name. In case when sqlSchema property is not set it is just derived from cache name. 2. Exactly this happens right now. Property sqlSchema is optional. If you are asking why is it always quoted and case sensitive, that is fo

[GitHub] ignite pull request: IGNITE-2249 - Do not deserialize services on ...

GitHub user vkulichenko opened a pull request: https://github.com/apache/ignite/pull/364 IGNITE-2249 - Do not deserialize services on client node You can merge this pull request into a Git repository by running: $ git pull https://github.com/vkulichenko/incubator-ignite ignite

[jira] [Created] (IGNITE-2249) Services are sometimes deserialized on client

Valentin Kulichenko created IGNITE-2249: --- Summary: Services are sometimes deserialized on client Key: IGNITE-2249 URL: https://issues.apache.org/jira/browse/IGNITE-2249 Project: Ignite

Re: Dynamic caches creation

On Tue, Dec 22, 2015 at 03:45PM, Alexey Kuznetsov wrote: > Cos, > > How you are going to create caches in already started cluster? > I think you will create a cache configuration and after that will get cache > via Ignite.getOrCreateCache(ccfg). I would imagine that I can write some Java code to

sqlSchema usability question

Folks, I'm testing https://issues.apache.org/jira/browse/IGNITE-1979 and have the following questions: 1) why I'm cannot use cache name in queries if I set sqlSchema for cache? 2) why we cannot just use cache name as sqlSchema if sqlSchema is not set explicitly (sqlSchema is null) and cache name

Re: 1.5 GA

Great, thanks! On Tue, Dec 22, 2015 at 07:52PM, Anton Vinogradov wrote: > Versions updated. > > On Tue, Dec 22, 2015 at 12:36 PM, Anton Vinogradov > wrote: > > > Seems everything is ok, > > > > https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-b1 > > https://versionatorr.appspot.com/?a=1.

Re: 1.5.final

As of today, there are still 4 tickets open: http://s.apache.org/ignite-1.5.0.final Anton - 2 tickets Vladimir - 1 ticket Alexey - 1 ticket D. On Tue, Dec 22, 2015 at 5:50 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Looks like it is a duplicate of IGNITE-2135. > The issue is ca

Re: 1.5 GA

Anton, Can you please close this ticket if you are done with it? https://issues.apache.org/jira/browse/IGNITE-2226 D. On Tue, Dec 22, 2015 at 8:52 AM, Anton Vinogradov wrote: > Versions updated. > > On Tue, Dec 22, 2015 at 12:36 PM, Anton Vinogradov < > avinogra...@gridgain.com > > wrote: > >

Re: UNRESOLVED tickets

Generally speaking, Resolved would mean that the issue is fixed, but some extra verification needs to take place, e.g. an additional TC run or some other testing. Raul, if you are saying your tickets should be treated as closed, should I just go ahead and close them? D. On Tue, Dec 22, 2015 at 1

[jira] [Created] (IGNITE-2248) CPP: Implement obtaining the row-identifying column of tables for the ODBC driver.

Igor Sapego created IGNITE-2248: --- Summary: CPP: Implement obtaining the row-identifying column of tables for the ODBC driver. Key: IGNITE-2248 URL: https://issues.apache.org/jira/browse/IGNITE-2248 Proj

[jira] [Created] (IGNITE-2247) CPP: Implement error handling for the ODBC driver.

Igor Sapego created IGNITE-2247: --- Summary: CPP: Implement error handling for the ODBC driver. Key: IGNITE-2247 URL: https://issues.apache.org/jira/browse/IGNITE-2247 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2246) CPP: Implement Descriptors support for the ODBC driver.

Igor Sapego created IGNITE-2246: --- Summary: CPP: Implement Descriptors support for the ODBC driver. Key: IGNITE-2246 URL: https://issues.apache.org/jira/browse/IGNITE-2246 Project: Ignite Issue

[jira] [Created] (IGNITE-2245) CPP: Implement Statement attributes manipulation for the ODBC driver.

Igor Sapego created IGNITE-2245: --- Summary: CPP: Implement Statement attributes manipulation for the ODBC driver. Key: IGNITE-2245 URL: https://issues.apache.org/jira/browse/IGNITE-2245 Project: Ignite

[jira] [Created] (IGNITE-2244) CPP: Implement Connection attributes manipulation for the ODBC driver.

Igor Sapego created IGNITE-2244: --- Summary: CPP: Implement Connection attributes manipulation for the ODBC driver. Key: IGNITE-2244 URL: https://issues.apache.org/jira/browse/IGNITE-2244 Project: Ignite

[jira] [Created] (IGNITE-2243) CPP: Implement Environment attributes manipulation for the ODBC driver.

Igor Sapego created IGNITE-2243: --- Summary: CPP: Implement Environment attributes manipulation for the ODBC driver. Key: IGNITE-2243 URL: https://issues.apache.org/jira/browse/IGNITE-2243 Project: Ignite

[jira] [Created] (IGNITE-2242) CPP: Implement SQLGetData function for the ODBC driver.

Igor Sapego created IGNITE-2242: --- Summary: CPP: Implement SQLGetData function for the ODBC driver. Key: IGNITE-2242 URL: https://issues.apache.org/jira/browse/IGNITE-2242 Project: Ignite Issue

[jira] [Created] (IGNITE-2241) CPP: Implement SQLGEtTypeInfo function for the ODBC driver.

Igor Sapego created IGNITE-2241: --- Summary: CPP: Implement SQLGEtTypeInfo function for the ODBC driver. Key: IGNITE-2241 URL: https://issues.apache.org/jira/browse/IGNITE-2241 Project: Ignite I

[GitHub] ignite pull request: Ignite tmp

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/363 Ignite tmp temp PRQ for proprietary build. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-TMP Alternatively you

Re: 1.5 GA

Versions updated. On Tue, Dec 22, 2015 at 12:36 PM, Anton Vinogradov wrote: > Seems everything is ok, > > https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-b1 > https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-final > > I'll update versions. > > On Tue, Dec 22, 2015 at 12:28 PM, Ant

[jira] [Created] (IGNITE-2240) CPP: Implement SQLEndTran function for the ODBC driver.

Igor Sapego created IGNITE-2240: --- Summary: CPP: Implement SQLEndTran function for the ODBC driver. Key: IGNITE-2240 URL: https://issues.apache.org/jira/browse/IGNITE-2240 Project: Ignite Issue

[jira] [Created] (IGNITE-2239) CPP: Implement SQLConnect function for the ODBC driver.

Igor Sapego created IGNITE-2239: --- Summary: CPP: Implement SQLConnect function for the ODBC driver. Key: IGNITE-2239 URL: https://issues.apache.org/jira/browse/IGNITE-2239 Project: Ignite Issue

[jira] [Created] (IGNITE-2238) CPP: Implement basic cursor operations for the ODBC driver.

Igor Sapego created IGNITE-2238: --- Summary: CPP: Implement basic cursor operations for the ODBC driver. Key: IGNITE-2238 URL: https://issues.apache.org/jira/browse/IGNITE-2238 Project: Ignite I

[jira] [Created] (IGNITE-2237) GridFutureAdapter: simplify and optimize.

Vladimir Ozerov created IGNITE-2237: --- Summary: GridFutureAdapter: simplify and optimize. Key: IGNITE-2237 URL: https://issues.apache.org/jira/browse/IGNITE-2237 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2236) Simplify GridCompoundFuture.

Vladimir Ozerov created IGNITE-2236: --- Summary: Simplify GridCompoundFuture. Key: IGNITE-2236 URL: https://issues.apache.org/jira/browse/IGNITE-2236 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2235) GridNioServer$AbstractNioClientWorker,changeReqs can be changed to queue.

Vladimir Ozerov created IGNITE-2235: --- Summary: GridNioServer$AbstractNioClientWorker,changeReqs can be changed to queue. Key: IGNITE-2235 URL: https://issues.apache.org/jira/browse/IGNITE-2235 Proje

[jira] [Created] (IGNITE-2234) GridCacheMvccManager.contextReset() generates garbage.

Vladimir Ozerov created IGNITE-2234: --- Summary: GridCacheMvccManager.contextReset() generates garbage. Key: IGNITE-2234 URL: https://issues.apache.org/jira/browse/IGNITE-2234 Project: Ignite

[jira] [Created] (IGNITE-2233) Avoid boxing in BinaryContext collections

Vladimir Ozerov created IGNITE-2233: --- Summary: Avoid boxing in BinaryContext collections Key: IGNITE-2233 URL: https://issues.apache.org/jira/browse/IGNITE-2233 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2232) Whole-product optimziations.

Vladimir Ozerov created IGNITE-2232: --- Summary: Whole-product optimziations. Key: IGNITE-2232 URL: https://issues.apache.org/jira/browse/IGNITE-2232 Project: Ignite Issue Type: Task

[GitHub] ignite pull request: ignite-2080 Data alignment issues with Unsafe

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/362 ignite-2080 Data alignment issues with Unsafe You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-2080 Alternatively yo

[GitHub] ignite pull request: ignite-2080 Data alignment issues with Unsafe

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

Re: 1.5.final

Looks like it is a duplicate of IGNITE-2135. The issue is caused by not setting deployment info bean in query request when binary marshaller is used. I anticipate the fix to be pretty simple, though need some more time to add a proper test and to run CI. Will send an update once all is done.

Re: 1.5.final

On Tue, Dec 22, 2015 at 9:25 AM, Anton Vinogradov wrote: > IGNITE-2116 ignite-osgi-karaf has only readme and license files > Waiting for Raul's answer. > Replied in the ticket. Sorry for the delay. Too many open fronts! *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integratio

Re: 1.5.final

​Sure, I will provide my feedback in a couple of hours.

Re: 1.5.final

We found yet another blocker issue (the behavior changed it becomes more important from my standpoint): IGNITE-2200 CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa Alexey could you take a look and investigate it? If n

[jira] [Created] (IGNITE-2231) 'Put' cache event treats entry created at lock acquisition time as old value

Denis Magda created IGNITE-2231: --- Summary: 'Put' cache event treats entry created at lock acquisition time as old value Key: IGNITE-2231 URL: https://issues.apache.org/jira/browse/IGNITE-2231 Project: I

[jira] [Created] (IGNITE-2230) CPP: Implement "Bind offset" feature for the ODBC driver.

Igor Sapego created IGNITE-2230: --- Summary: CPP: Implement "Bind offset" feature for the ODBC driver. Key: IGNITE-2230 URL: https://issues.apache.org/jira/browse/IGNITE-2230 Project: Ignite Issu

Re: 1.5.final

Anton, I think it is worth while to send your question for IGNITE-2116 here as well. Perhaps Raul will have access to the email and respond. D. On Tue, Dec 22, 2015 at 1:25 AM, Anton Vinogradov wrote: > My tickets: > > IGNITE-2226 Replace dash in 1.5.0-final with dot 1.5.0.final > > IGNITE-217

Re: 1.5 GA

Seems everything is ok, https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-b1 https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-final I'll update versions. On Tue, Dec 22, 2015 at 12:28 PM, Anton Vinogradov wrote: > Dmitriy, > > that's not a big change, but we have to check it will

Re: 1.5 GA

Dmitriy, that's not a big change, but we have to check it will not break something else. I'll check it today. Raul, Could you please check this solution is suitable for OSGi? On Tue, Dec 22, 2015 at 10:04 AM, Dmitriy Setrakyan wrote: > I filed the ticket: > https://issues.apache.org/jira/brow

Re: 1.5.final

My tickets: IGNITE-2226 Replace dash in 1.5.0-final with dot 1.5.0.final IGNITE-2175 Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7) Both should be ready today. IGNITE-2116 ignite-osgi-karaf has only readme and license files Waiting

[jira] [Created] (IGNITE-2229) Full text queries do not return valid results on unstable topology

Alexey Goncharuk created IGNITE-2229: Summary: Full text queries do not return valid results on unstable topology Key: IGNITE-2229 URL: https://issues.apache.org/jira/browse/IGNITE-2229 Project: I

Re: UNRESOLVED tickets

My resolved tickets can be closed too. I wasn't aware that you differentiated both statuses in this project. Will do it later when I'm on a computer. Raúl. On 22 Dec 2015 06:26, "Dmitriy Setrakyan" wrote: > Raul, Cos, > > You have 9 tickets in RESOLVED state for 1.5 release. Can these tickets b

Re: Dynamic caches creation

Cos, How you are going to create caches in already started cluster? I think you will create a cache configuration and after that will get cache via Ignite.getOrCreateCache(ccfg). So if you server cluster at some point was completely restarted, then executing getOrCreateCache(ccfg) will create cac

Dynamic caches creation

Guys, is it possible to configure caches dynamically and persist their configuration in some shape and form? Here's the use case: - we want to create some caches in the already running cluster for a data set - once it is done, we'll run some SQL queries on top of those - ideally, we'd like to b

Re: Versioning policies for .NET and CPP

Betas should be also dropped for multiple other reasons I've explained elsethreads. Cos On Mon, Dec 21, 2015 at 11:49PM, Dmitriy Setrakyan wrote: > Our versions should be the same for .NET, C++, and Java. If this means > dropping betas, so be it. > > D. > > On Mon, Dec 21, 2015 at 10:26 PM, Kon