[GitHub] ignite pull request #1223: IGNITE-4100: Improved README and DEVNOTES for CPP...

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1223 --- 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 #1430: IGNITE-1680: Implemented basic API for user entry...

2017-01-13 Thread isapego
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1430 IGNITE-1680: Implemented basic API for user entry point lookup and Cache::Invoke. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1424: Ignite 4540-1

2017-01-13 Thread AMashenkov
Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1424 --- 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

Re: Configuring Cassandra persistence from code

2017-01-13 Thread Valentin Kulichenko
Hi Igor, Why did you choose to use a special format instead of going with Spring in the first place? It seems to that this is what creating difficulties here, because with Spring any of scenarios we mentioned is possible: - You can create a template in XML, load it using

[GitHub] ignite pull request #1213: IGNITE-4183: Returning size of the fixed-sized co...

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1213 --- 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 #1190: IGNITE-4113: Added some tests. Improved statement...

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1190 --- 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 #1196: IGNITE-4090: Added compiler flags so stdint and l...

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1196 --- 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

[jira] [Created] (IGNITE-4547) Apache Ignite 2.0 quick and needed tasks

2017-01-13 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-4547: --- Summary: Apache Ignite 2.0 quick and needed tasks Key: IGNITE-4547 URL: https://issues.apache.org/jira/browse/IGNITE-4547 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1124: IGNITE-3873: Added configs for WiX to generate OD...

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1124 --- 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 #1222: IGNITE-4201: Fixed version fix maven step.

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1222 --- 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

Want to learn Ignite more? Help to release 2.0

2017-01-13 Thread Denis Magda
Igniters and dear users, I’ve aggregated a list of quick tickets that have to be done in approaching hge Apache Ignite 2.0 release: https://issues.apache.org/jira/browse/IGNITE-4547 Go ahead a pick the one of your interests whether you’re

Re: DDL implementation details

2017-01-13 Thread Dmitriy Setrakyan
Vova, I will join Sergi here. It seems like "schema = cache" will take care of all different configuration properties required for different groups of caches. In addition, it cleanly maps into current Ignite architecture. We will need to have a very strong reason to move away from it. D. On

[GitHub] ignite pull request #1260: IGNITE-4249: TCP message sended by ODBC driver in...

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1260 --- 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

Re: DDL implementation details

2017-01-13 Thread Dmitriy Setrakyan
On Fri, Jan 13, 2017 at 12:26 AM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Dima, > > >> But, as you have justly noted, we have to keep nodes joining the > >> cluster up-to-date about what schemas and tables need to be created in > >> order for those nodes to participate in

[GitHub] ignite pull request #1126: IGNITE-3868: Fix for Tableau connect using DSN.

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1126 --- 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 #965: IGNITE-2943 .NET: Fix cache store error propagatio...

2017-01-13 Thread isapego
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/965 --- 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

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

2017-01-13 Thread Denis Magda
Hi Nikita, I can’t find provided account in Ignite JIRA https://issues.apache.org/jira/browse/IGNITE Please create an account there and share with me. This information might be useful for you as well. Subscribe to both dev and user lists:

Re: Empty cache memory overhead

2017-01-13 Thread Denis Magda
Alexander, Please feel free to create a JIRA ticket. Hope that someone will start working on it soon. — Denis > On Jan 11, 2017, at 11:05 PM, Alexey Goncharuk > wrote: > > Yes, it is relevant. All of these structures are not replaced with page > memory. > > On

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

2017-01-13 Thread Denis Magda
Sally, no worries, take your time! Have nice weekends, Denis > On Jan 13, 2017, at 8:30 AM, Sally Khudairi wrote: > > Hi folks --just a quick heads-up that I haven't forgotten about you! > > I issued three press releases + the January "Success at Apache" this week, so >

Re: Ignite ASF blog [Was: Blogging about new .NET features]

2017-01-13 Thread Denis Magda
Cos, awesome! Thanks for pushing it forward. — Denis > On Jan 13, 2017, at 8:39 AM, Konstantin Boudnik wrote: > > FYI >https://issues.apache.org/jira/browse/INFRA-13324 > > once the JIRA is finished, we'd have an office Apache blog for Ignite, listed > and syndicated

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

2017-01-13 Thread Sally Khudairi
Hi folks --just a quick heads-up that I haven't forgotten about you! I issued three press releases + the January "Success at Apache" this week, so there's been a little extra press activity than usual. I'm aiming to get the draft to you today...otherwise over the weekend. I apologize for the

Ignite ASF blog [Was: Blogging about new .NET features]

2017-01-13 Thread Konstantin Boudnik
FYI https://issues.apache.org/jira/browse/INFRA-13324 once the JIRA is finished, we'd have an office Apache blog for Ignite, listed and syndicated across all ASF resources. Hence raising the visibility of the project. Regards, Cos On Sat, Nov 26, 2016 at 01:21PM, Konstantin Boudnik wrote:

[jira] [Created] (IGNITE-4546) .NET: BinaryConfiguration handles nested type names incorrectly

2017-01-13 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-4546: -- Summary: .NET: BinaryConfiguration handles nested type names incorrectly Key: IGNITE-4546 URL: https://issues.apache.org/jira/browse/IGNITE-4546 Project: Ignite

Re: DDL implementation details

2017-01-13 Thread Sergi Vladykin
Lets move on with SQL schema == Ignite cache. It worked always like this, I see no reasons to change this. Sergi 2017-01-13 11:20 GMT+03:00 Vladimir Ozerov : > "Tablespace" (Oracle, PostgreSQL) is what maps better than "schema" to our > cache. But not ideally still. > > On

Re: DDL implementation details

2017-01-13 Thread Sergi Vladykin
Could you please elaborate why it will not work this way? Sergi 2017-01-13 12:39 GMT+03:00 Vladimir Ozerov : > Correct, it worked, because Ignite has never had real database use case in > mind. Unfortunately, if our global plans go as expected, it will not work > for

Re: IGNITE-4302 discovery messages to exchange binary metadata - design proposal

2017-01-13 Thread Vladimir Ozerov
Sergey, In my understanding the only difficult thing here is how to disallow usage of not-yet-confirmed metadata during serialization. As we assume metadata updates to be relatively rare, can we always initiate message send from coordinator node? In this case we will have total order of all

Re: IGNITE-4302 discovery messages to exchange binary metadata - design proposal

2017-01-13 Thread Alexey Goncharuk
Vladimir, Given that metadata updates will be initiated with DiscoveryCustomEvent, I see no problems neither with total message ordering (the order will be the same on all nodes and consistent with discovery events) nor with failover - the event is marked with @TcpDiscoveryEnsureDelivery, so the

Re: DDL implementation details

2017-01-13 Thread Vladimir Ozerov
Alex, Currently Ignite is not used as database. It is used as search engine - several types, several tables, several joins. This is why having "SCHEMA == cache" was never a problem. Users have never build complex SQL applications on top of Ignite. But we are going towards database. And my

Re: DDL implementation details

2017-01-13 Thread Vladimir Ozerov
"Tablespace" (Oracle, PostgreSQL) is what maps better than "schema" to our cache. But not ideally still. On Fri, Jan 13, 2017 at 11:10 AM, Vladimir Ozerov wrote: > Alex, > > Currently Ignite is not used as database. It is used as search engine - > several types, several

IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

2017-01-13 Thread Nikita Amelchev
Hello everyone. I'd like to take IGNITE-2894. Can you assign to me? Username: NSAmelchev -- Best wishes, Amelchev Nikita

Re: DDL implementation details

2017-01-13 Thread Vladimir Ozerov
Correct, it worked, because Ignite has never had real database use case in mind. Unfortunately, if our global plans go as expected, it will not work for Ignite 2.x+. On Fri, Jan 13, 2017 at 11:53 AM, Sergi Vladykin wrote: > Lets move on with SQL schema == Ignite cache.

[GitHub] ignite pull request #1425: IGNITE-4036: Near cache is not expired together w...

2017-01-13 Thread AMashenkov
GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1425 IGNITE-4036: Near cache is not expired together with corresponding server cache Test added You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1426: IGNITE-4518 Fixed parallel load cache.

2017-01-13 Thread nva
GitHub user nva opened a pull request: https://github.com/apache/ignite/pull/1426 IGNITE-4518 Fixed parallel load cache. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4518 Alternatively you can

[jira] [Created] (IGNITE-4545) Improve router node detection for external client

2017-01-13 Thread Andrey Novikov (JIRA)
Andrey Novikov created IGNITE-4545: -- Summary: Improve router node detection for external client Key: IGNITE-4545 URL: https://issues.apache.org/jira/browse/IGNITE-4545 Project: Ignite Issue

[GitHub] ignite pull request #1428: IGNITE-4545 Added cache for router hostnames.

2017-01-13 Thread nva
GitHub user nva opened a pull request: https://github.com/apache/ignite/pull/1428 IGNITE-4545 Added cache for router hostnames. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4545 Alternatively

Re: Allow distributed SQL query execution over explicit set of partitions

2017-01-13 Thread Alexei Scherbakov
PartitionSet hides internal implementation of int array. This allows as to efficiently represent contiguous range of partitions and defines clear API for ordered iteration over partitions and containment check. Even better to go with compressed bitmap, as I mentioned in ticket comment. This will

Re: Allow distributed SQL query execution over explicit set of partitions

2017-01-13 Thread Sergi Vladykin
Internally we still use int[] when we send partitions (see GridH2QueryRequest.parts). It looks like we only do more work with PartitionSet. I like the idea of bitset for partitions, but 1. We have to change internals first to use it, otherwise the optimization makes no sense. 2. We will need to

[GitHub] ignite pull request #1427: Ignite 4513

2017-01-13 Thread ntikhonov
GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/1427 Ignite 4513 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4513 Alternatively you can review and apply these

Re: IGNITE-4302 discovery messages to exchange binary metadata - design proposal

2017-01-13 Thread Sergey Chugunov
Vladimir, Alexey, Let me describe my current vision of the task; please correct me if I'm wrong somewhere. 1. The only class adding and retrieving metadata to/from sys-cache is *CacheObjectBinaryProcessorImpl*. I expect all code managing discovery events flow to be placed here.

[GitHub] ignite pull request #1429: Ignite 4540

2017-01-13 Thread AMashenkov
Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1429 --- 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

[GitHub] ignite pull request #1429: Ignite 4540

2017-01-13 Thread AMashenkov
GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1429 Ignite 4540 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4540 Alternatively you can review and apply

Re: Allow distributed SQL query execution over explicit set of partitions

2017-01-13 Thread Alexei Scherbakov
OK, let's do it this way. 2017-01-13 13:27 GMT+03:00 Sergi Vladykin : > Internally we still use int[] when we send partitions (see > GridH2QueryRequest.parts). It looks like we only do more work with > PartitionSet. > > I like the idea of bitset for partitions, but