Re: ETL with Ignite

Cos, I see that you have already found the JSON ticket: https://issues.apache.org/jira/browse/IGNITE-962 This ticket will make it possible to index JSON object in Ignite cache and use them in SQL queries. If you don’t need indexes, why not just store JSONs as String objects or byte arrays? D. O

ETL with Ignite

Guys, We have a data-pipeline ingesting some data into Ignite cache from a JSON source. While JSON ingestion isn't an issue by itself, it seems that there's no mechanism in place to detect and create a schema class for JSON data structure on the fly. I know there's a functionality to automaticall

[GitHub] ignite pull request: Ignite 481

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/234 Ignite 481 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-481 Alternatively you can review and apply these cha

Re: Ignite interpreter for Zeppelin

Hi Andrey. Our situation is a little bit different as we are setting up and tightly control the configurations during the cluster's deployment phase. Basically, we provide a template for the interpreters file. Appreciate the example! Cos On Wed, Nov 11, 2015 at 01:32PM, Andrey Gura wrote: > Cos,

Re: Ignite-1.5 Release

Folks, I am working on portable marshalling performance at the moment. I took a scenario which is good for OptimziedMarshaller and is very unfortunate for PortableMarshaller: object with 40 int fields. My idea here is that this scenario is so bad for Portable, so that in the vast majority of sensi

[jira] [Created] (IGNITE-1915) .Net: Ignite as Entity Framework Second-Level Cache

Pavel Tupitsyn created IGNITE-1915: --- Summary: .Net: Ignite as Entity Framework Second-Level Cache Key: IGNITE-1915 URL: https://issues.apache.org/jira/browse/IGNITE-1915 Project: Ignite Is

Classloading in Ignite

Hi team, I'm seeing instances of ClassLoaders being kept as instance variables in many places. It looks a bit ad-hoc. What surprises me is that the user-set ClassLoader (IgniteConfiguration#setClassLoader) is ignored in many places where, in my opinion, it should be preferred, e.g.: * Optimized

Re: Check Ignite code base with Findbugs.

On Fri, Nov 13, 2015 at 4:51 PM, Alexey Kuznetsov wrote: > Raul, I'm afraid it will produce 100500 false-positive warnings. > Yep, it's likely. I think we need to investigate what will be generated by FB tune it and > then decide to include it or not into maven build. > Exactly. We should do a

Re: Custom ThreadFactory

On Fri, Nov 13, 2015 at 4:16 AM, Yakov Zhdanov wrote: > Andrey, I closed (with proper relation) > https://issues.apache.org/jira/browse/IGNITE-1899 since we already had > https://issues.apache.org/jira/browse/IGNITE-10 Andrey, would you be interested in contributing this feature? > > > --Yako

Re: Check Ignite code base with Findbugs.

Raul, I'm afraid it will produce 100500 false-positive warnings. I think we need to investigate what will be generated by FB tune it and then decide to include it or not into maven build. Or may be we could have it as optional step (it is possible?). On Fri, Nov 13, 2015 at 11:32 PM, Raul Kripal

Re: Check Ignite code base with Findbugs.

I'd prefer to plug it into the Maven build: https://gleclaire.github.io/findbugs-maven-plugin/. *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.

[jira] [Created] (IGNITE-1914) .Net: Get rid of boxing in DoOutInOpNullable

Pavel Tupitsyn created IGNITE-1914: --- Summary: .Net: Get rid of boxing in DoOutInOpNullable Key: IGNITE-1914 URL: https://issues.apache.org/jira/browse/IGNITE-1914 Project: Ignite Issue Typ

[GitHub] ignite pull request: IGNITE-1912 .Net: Continuous query does not w...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/233 IGNITE-1912 .Net: Continuous query does not work for value types You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1912

Re: Check Ignite code base with Findbugs.

It absolutely does make sense. Of course it will not find complex bugs but it is pretty good at spotting stupid mistakes. Time ago I used to run Eclipse plugin for FindBugs, I believe something alike should exist for Idea as well. Sergi 2015-11-13 17:49 GMT+03:00 Alexey Kuznetsov : > Igniters,

RE: OSGi migration may require a special marshaller

Raul, if you don't mind, for posterity, could you please collect all your ideas spread all over this two-week long email thread and update the wiki page here https://cwiki.apache.org/confluence/display/IGNITE/OSGI+Compatibility? The details of your de-/serialization implementation would be espec

[jira] [Created] (IGNITE-1913) Assertion fail cause Grid hangs

Anton Vinogradov created IGNITE-1913: Summary: Assertion fail cause Grid hangs Key: IGNITE-1913 URL: https://issues.apache.org/jira/browse/IGNITE-1913 Project: Ignite Issue Type: Bug

Check Ignite code base with Findbugs.

Igniters, What do you think about checking Ignite code base with Findbugs ( http://findbugs.sourceforge.net)? Does it make sense? Maybe someone will try? Thoughts? -- Alexey Kuznetsov

[jira] [Created] (IGNITE-1912) .Net: Continuous query does not work for value types

Pavel Tupitsyn created IGNITE-1912: --- Summary: .Net: Continuous query does not work for value types Key: IGNITE-1912 URL: https://issues.apache.org/jira/browse/IGNITE-1912 Project: Ignite I

Re: Ignite-1.5 Release

Hi Denis, Thanks a lot, it looks like my test setup was wrong, I added semaphore tests to GridCacheAbstractDataStructuresFailoverSelfTest suite. Now I have following problem: when I run tests with TOP_CHANGE_THREAD_CNT = 3 tests fail when they reach stop() with the following exception: class org.

Re: ignite-platform module

On Thu, Nov 12, 2015 at 8:24 PM, Dmitriy Setrakyan wrote: > How about renaming your module folders as following: > > - modules > |— osgi > |— osgi-karaf > |— osgi-paxlogging > Sounds good to me! *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration

[GitHub] ignite pull request: IGNITE-1910 .Net: Possible handle leak in Sca...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/232 IGNITE-1910 .Net: Possible handle leak in ScanQuery You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1910 Alternativel

[jira] [Created] (IGNITE-1910) .Net: Possible handle leak in ScanQuery

Pavel Tupitsyn created IGNITE-1910: --- Summary: .Net: Possible handle leak in ScanQuery Key: IGNITE-1910 URL: https://issues.apache.org/jira/browse/IGNITE-1910 Project: Ignite Issue Type: Bu

[jira] [Created] (IGNITE-1911) Discovery MessageWorker thread moves node to "zombie" state when fails

Denis Magda created IGNITE-1911: --- Summary: Discovery MessageWorker thread moves node to "zombie" state when fails Key: IGNITE-1911 URL: https://issues.apache.org/jira/browse/IGNITE-1911 Project: Ignite

Re: Fwd: IGNITE-1227 patch available

Amir, great thanks! If you don't mind I'll review your changes in a couple of days. However, probably someone else will do this earlier:) -- Denis From: *Amir Akhmedov* > Date: Fri, Nov 13, 2015 at 11:28 AM Subject: IGNITE-1227 patch available To: dev@ignite.

[GitHub] ignite pull request: IGNITE-1896 .Net: Improve query API

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/231 IGNITE-1896 .Net: Improve query API You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1896 Alternatively you can review

Re: Ignite with Spring boot

I was wrong regarding the following, sorry / //However, I'm afraid that the fix is inapplicable because you changed methods' return type from IgniteMXBean public API.// //This will break source code compatibility between current and released Ignite versions./ It's OK to change the return type

Re: Custom ThreadFactory

Andrey, I closed (with proper relation) https://issues.apache.org/jira/browse/IGNITE-1899 since we already had https://issues.apache.org/jira/browse/IGNITE-10 --Yakov 2015-11-13 2:40 GMT+03:00 Andrey Kornev : > There you go: > https://issues.apache.org/jira/browse/IGNITE-1898 > and > https://iss

Re: Ignite with Spring boot

姜 为 , for fix this error disable spring jmx in application properties spring.jmx.enabled=false пт, 13 нояб. 2015 г. в 14:30, Denis Magda : > Hi, > > As I see you've already found out the reason of the issue [1] and, > moreover, have already fixed it [2] :) Perfect. > > However, I'm afraid that

Re: Implement IgniteMultimap data structures

I'll do my best :) Then I'll assign it to me. Thanks. 2015-11-13 14:47 GMT+03:00 Yakov Zhdanov : > Amir, you are welcome! It would be cool if we can get it to 1.6 > > --Yakov > > 2015-11-13 13:50 GMT+03:00 Amir Akhmedov : > > > Hi, > > > > If no objections then I would like to start to work on

[jira] [Created] (IGNITE-1909) .Net: Discovery configuration

Pavel Tupitsyn created IGNITE-1909: --- Summary: .Net: Discovery configuration Key: IGNITE-1909 URL: https://issues.apache.org/jira/browse/IGNITE-1909 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-1908) .Net: Query configuration

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

[jira] [Created] (IGNITE-1907) .Net: Cache configuration

Pavel Tupitsyn created IGNITE-1907: --- Summary: .Net: Cache configuration Key: IGNITE-1907 URL: https://issues.apache.org/jira/browse/IGNITE-1907 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-1906) .Net: Ignite configuration without Spring.

Pavel Tupitsyn created IGNITE-1906: --- Summary: .Net: Ignite configuration without Spring. Key: IGNITE-1906 URL: https://issues.apache.org/jira/browse/IGNITE-1906 Project: Ignite Issue Type:

Re: Implement IgniteMultimap data structures

Amir, you are welcome! It would be cool if we can get it to 1.6 --Yakov 2015-11-13 13:50 GMT+03:00 Amir Akhmedov : > Hi, > > If no objections then I would like to start to work on this ticket ( > IGNITE-640 ) > > -- > Sincerely Yours Amir Akhmedo

[jira] [Created] (IGNITE-1905) High contention for CacheLockImpl causes AssertionErrors

Denis Magda created IGNITE-1905: --- Summary: High contention for CacheLockImpl causes AssertionErrors Key: IGNITE-1905 URL: https://issues.apache.org/jira/browse/IGNITE-1905 Project: Ignite Issue

[jira] [Created] (IGNITE-1904) Need to add two new dependencies in pom-file to cover special cases

Pavel Konstantinov created IGNITE-1904: -- Summary: Need to add two new dependencies in pom-file to cover special cases Key: IGNITE-1904 URL: https://issues.apache.org/jira/browse/IGNITE-1904 Proje

Implement IgniteMultimap data structures

Hi, If no objections then I would like to start to work on this ticket ( IGNITE-640 ) -- Sincerely Yours Amir Akhmedov

[GitHub] ignite pull request: IGNITE-1901: Adopted new marshalling flags.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/230 IGNITE-1901: Adopted new marshalling flags. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-1901 Alternatively you can re

Re: How to build ignite-1.5.0 from source code

thank you all! I will have a try! Thanks, kcheng On Fri, Nov 13, 2015 at 6:09 PM, Ken Cheng wrote: > at the same I check the ignite-1.4 this branch, it has below setting > > > org.apache.ignite > apache-ignite > 1.4.0-SNAPSHOT > pom > > > > but in maven central repository, the v

Re: How to build ignite-1.5.0 from source code

at the same I check the ignite-1.4 this branch, it has below setting org.apache.ignite apache-ignite 1.4.0-SNAPSHOT pom but in maven central repository, the version is 1.4.0. If I want to build 1.4 from branch 'ignite-1.4', which commands should I use to generate jars like

Re: How to build ignite-1.5.0 from source code

Hi Ken, Everything is correct. Version should be changed to 1.5.0 manually. Please check DEVNOTES.txt for release instructions. Quote from DEVNOTES.txt: "Ensure you have RELEASE (not SNAPSHOT) version at Ignite poms. Maven release plugin release:prepare goal can be used to make release tag." O

Re: How to build ignite-1.5.0 from source code

yes, you are right. the pom as below org.apache.ignite apache-ignite 1.5.0-SNAPSHOT pom but I want to build a release version instead of a snapshot. I just want to know to to build a release version(1.5.0) by the way I am using the command "mvn clean package -DskipTests" Tha

[GitHub] ignite pull request: IGNITE-1902 NET: Adopt new marshalling flags.

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/229 IGNITE-1902 NET: Adopt new marshalling flags. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1902 Alternatively you

Re: How to build ignite-1.5.0 from source code

Ken Cheng wrote > Hi All, > > Even I am on the branch ignite-1.5, but when I try to build 1.5.0 release, > the version I got is '1.5.0-SNAPSHOT' > > I checked the ignite/pom.xml but could not find any clue. > > What I am expecting is '1.5.0' instead of '1.5.0-SNAPSHOT' > > Anybody can help me

How to build ignite-1.5.0 from source code

Hi All, Even I am on the branch ignite-1.5, but when I try to build 1.5.0 release, the version I got is '1.5.0-SNAPSHOT' I checked the ignite/pom.xml but could not find any clue. What I am expecting is '1.5.0' instead of '1.5.0-SNAPSHOT' Anybody can help me out? Many Thanks, kcheng

IGNITE-1903: CacheStore implementation is serialised to grid clients whether they require it or not

Moving the conversation from the User list. vkulichenko wrote > You get an error because you don't have a class on the client node. With > ClassFactory it doesn't receive the store instance, but it still receives > corresponding Class object, therefore fails. I think the cleanest way to > solve i

[GitHub] ignite pull request: IGNITE-1878 added jspm as vendor libs packet ...

GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/228 IGNITE-1878 added jspm as vendor libs packet manager You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite ignite-1878 Alternative

[jira] [Created] (IGNITE-1903) CacheStore implementation is serialised to grid clients whether they require it or not

Michael Griggs created IGNITE-1903: -- Summary: CacheStore implementation is serialised to grid clients whether they require it or not Key: IGNITE-1903 URL: https://issues.apache.org/jira/browse/IGNITE-1903

Re: NuGet icon hosting

Perfect, thank you! On Thu, Nov 12, 2015 at 11:58 PM, Dmitriy Setrakyan wrote: > Here you go: > https://ignite.apache.org/images/logo_ignite_32_32.png > > D. > > On Thu, Nov 12, 2015 at 10:09 AM, Pavel Tupitsyn > wrote: > > > Hi Dmitry, > > > > Looks like you have misunderstood me. There is no

[jira] [Created] (IGNITE-1902) NET: Adopt new marshalling flags.

Vladimir Ozerov created IGNITE-1902: --- Summary: NET: Adopt new marshalling flags. Key: IGNITE-1902 URL: https://issues.apache.org/jira/browse/IGNITE-1902 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-1901) CPP: Adopt new marshalling flags.

Vladimir Ozerov created IGNITE-1901: --- Summary: CPP: Adopt new marshalling flags. Key: IGNITE-1901 URL: https://issues.apache.org/jira/browse/IGNITE-1901 Project: Ignite Issue Type: Sub-task

IGNITE-1227 patch available

Hi Igniters, I submitted patch for IGNITE-1227 , could review it whenever it is possible. Thanks. -- Sincerely Yours Amir Akhmedov