[jira] [Created] (IGNITE-4552) Optimize GridDhtLocalPartition.rmvQueue

2017-01-16 Thread Alexei Scherbakov (JIRA)
Alexei Scherbakov created IGNITE-4552: - Summary: Optimize GridDhtLocalPartition.rmvQueue Key: IGNITE-4552 URL: https://issues.apache.org/jira/browse/IGNITE-4552 Project: Ignite Issue

scripting languages base cases using swig

2017-01-16 Thread Evgeniy Stanilovskiy
Hi all. Not so long ago i had to know that ignite had reduced functionality support in scripting languages. So, idea was to take an existing C++ client and using SWIG (http://www.swig.org) as automatic wrapper, generate clients for absence scripting languages. What do you think about this

Re: DDL implementation details

2017-01-16 Thread Sergey Kozlov
For the approach schema==cache it is not clear how it works for some cases (especialy if SQL and regular cache operations are mixed): 1. I want to store two tables in same cache (same schema) and both tables have identical structure like id Integer, name String. How they will be processed for

Re: DDL implementation details

2017-01-16 Thread Sergi Vladykin
Dima, I agree that cache==table is definitely a wrong choice, but as far as I see Vova suggests having cache==tablespace instead of cache==schema. I tend to agree with this decoupling of physical and logical grouping, but the concern is that it will require much more work to do. Sergi

Re: DDL implementation details

2017-01-16 Thread Dmitriy Setrakyan
Vova, Currently I see only 2 ways we can proceed here: 1. cache == table 2. cache == schema I agree that "cache==table" may be more flexible, but I don't think it will work in Ignite. We may end up with 1,000s of caches, which will carry significant overhead on memory and cluster overall.

[jira] [Created] (IGNITE-4551) Reconsider cache key/value peer class loading

2017-01-16 Thread Alexey Goncharuk (JIRA)
Alexey Goncharuk created IGNITE-4551: Summary: Reconsider cache key/value peer class loading Key: IGNITE-4551 URL: https://issues.apache.org/jira/browse/IGNITE-4551 Project: Ignite Issue

Re: Ignite ASF blog

2017-01-16 Thread Konstantin Boudnik
The blog https://blogs.apache.org/ignite/ has been configured. I have admin rights so please let me know if you want to start contributing and I will grant you the credentials for it. Cheers, Cos On Fri, Jan 13, 2017 at 08:39AM, Konstantin Boudnik wrote: > FYI >

[GitHub] ignite pull request #1433: IGNITE-4548 Implemented mapping of enum fields fo...

2017-01-16 Thread vsisko
GitHub user vsisko opened a pull request: https://github.com/apache/ignite/pull/1433 IGNITE-4548 Implemented mapping of enum fields for POJO STORE You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1432: IGNITE-4046: Implemented BinaryArrayIdentityResol...

2017-01-16 Thread isapego
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1432 IGNITE-4046: Implemented BinaryArrayIdentityResolver. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4046

[GitHub] ignite pull request #1309: IGNITE-4045 .NET: Support DML API

2017-01-16 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1309 --- 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 #1417: IGNITE-3400: add available size check before data...

2017-01-16 Thread tledkov-gridgain
Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1417 --- 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

Re: Product ID for Apache Ignite

2017-01-16 Thread Mark Thomas
On 03/01/2017 17:52, Denis Magda wrote: > Hi Mark, > > I reached out both MITRE and cvedetails.com > folks as you suggested earlier. Below you can > see the answer from MITRE. CVE guys have not replied yet. > > One of the things suggested by MITRE is the following > >>

Re: Contributing to Ignite.NET

2017-01-16 Thread Pavel Tupitsyn
Sergey, sure, go ahead and take it! Please assign to yourself and click "Start Progress". Let me know if you have any questions. Thanks, Pavel On Mon, Jan 16, 2017 at 2:49 PM, Guru Stron wrote: > Hi igniters, > > I want to improve LINQ support in IGNITE.NET. > > Is

Re: Contributing to Ignite.NET

2017-01-16 Thread Guru Stron
Hi igniters, I want to improve LINQ support in IGNITE.NET. Is it ok if i take this task: IGNITE-4425 .NET: Support "Array.Contains" in LINQ On 9 January 2017 at 15:40, Pavel Tupitsyn wrote: > Sergey, I've merged your

Re: DDL implementation details

2017-01-16 Thread Alexander Paschenko
Sergi, Regarding CREATE SCHEMA/TABLE parsing: 2017-01-12 18:51 GMT+03:00 Sergi Vladykin : > Hi, > > 1. For now I'm against inventing any custom SQL syntax and implementing > parsing. > Currently H2 supports the following syntax: > > CREATE TABLE test(...) WITH

Re: DDL implementation details

2017-01-16 Thread Alexander Paschenko
Dima, 2017-01-13 21:20 GMT+03:00 Dmitriy Setrakyan : > How about dynamic caches? Isn't the metadata already maintained across all > nodes every time a new cache is created? What am I missing here? Right, however, this section of the docs

[jira] [Created] (IGNITE-4549) .NET: Add LINQPad samples to logging NuGet packages

2017-01-16 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-4549: -- Summary: .NET: Add LINQPad samples to logging NuGet packages Key: IGNITE-4549 URL: https://issues.apache.org/jira/browse/IGNITE-4549 Project: Ignite

[GitHub] ignite pull request #1431: Ignite 1.7.5 p1

2017-01-16 Thread avinogradovgg
GitHub user avinogradovgg opened a pull request: https://github.com/apache/ignite/pull/1431 Ignite 1.7.5 p1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.7.5-p1 Alternatively you can review and

Re: DDL implementation details

2017-01-16 Thread Vladimir Ozerov
Sergi, Dima, In the scope of Ignite 1.x it is perfectly fine to have "schema = cache". Nobody suffers from it because nobody use Ignite as database. But in future, thanks to page memory, we are going to target real database use cases. Users will have multiple tables in Ignite. Plus views,