Fifo eviction for atomic cache

and explain such behavior? -- Sergey Kozlov

Re: Fifo eviction for atomic cache

It seems this behavior caused removeAll on empty cache executed before puts. On Wed, Nov 11, 2015 at 1:16 PM, Sergey Kozlov <skoz...@gridgain.com> wrote: > Hi > > I've tested some cache configurations with eviction policy and found a bit > strange behavior. > >

Re: Fifo eviction for atomic cache

ve all entries > 3. put entries > > On Wed, Nov 11, 2015 at 2:59 PM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > > It seems this behavior caused removeAll on empty cache executed before > > puts. > > > > On Wed, Nov 11, 2015 at 1:16 PM, Sergey Kozlov

Re: Ignite 1.4

FYI: We've at least 161 unclosed issues planned to fix in version 1.4 On Tue, Sep 1, 2015 at 11:48 AM, Vladimir Ozerov wrote: > I'm going to create a branch "ignite-1.4" for this release from master. > Please let me know if anyone has concerns. > > On Mon, Aug 31, 2015

Re: Ignite 1.4

state. I think it will be sent for > vote Tue-Wed next week. > > -- > Yakov Zhdanov, Director R > *GridGain Systems* > www.gridgain.com > > 2015-09-04 0:31 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > > > On Thu, Sep 3, 2015 at 1:31 AM, Sergey Ko

Re: Ignite 1.4

I'm ok On Mon, Sep 7, 2015 at 3:31 PM, Anton Vinogradov <avinogra...@gridgain.com> wrote: > Seems worth specify "None" fixversion instead of 1.5. > Thoughts? > > On Mon, Sep 7, 2015 at 2:50 PM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > >

Re: Ignite 1.4

Yakov Zhdanov <yzhda...@apache.org> > >> wrote: > >> > > >> > > Of course, we will release ignite-1.4.0. Anton V, can you please > fix? > >> > > > >> > > --Yakov > >> > > > >> > > 2015-09-0

Re: IGNITE-1195

> I think the same question stands - what is the main challenge here? > > Yarn module is compatible with Hadoop version 2.7.0 and above. Exist two > way: set different variables for yarn and hadoop modules or make yarn > module compiled with older hadoop versions. > -- Sergey Kozlov

IGNITE-1195

ml and build.* *2. For maven version 3.2.1 or newest: * *mvn clean package -DskipTests -Dignite.edition=hadoop -Dhadoop.version=X.X.X -pl !module/yarn* Thoughts? Objections? -- Sergey Kozlov

Re: IGNITE-1195

or us to fix this? > > On Wed, Sep 2, 2015 at 11:58 AM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > > Hi Igniters > > > > I suppose that issue below won't be fixed in nearest release 1.4. > > > > IGNITE-1195 Released Ignite version 1.3.0 does not build with &

Re: Ignite 1.4

; > 2015-09-01 22:14 GMT+03:00 Branko Čibej <br...@apache.org>: > > > On 01.09.2015 20:46, Konstantin Boudnik wrote: > > > On Tue, Sep 01, 2015 at 08:45PM, Sergey Kozlov wrote: > > >> FYI: We've at least 161 unclosed issues planned to fix in version 1.4

Update version for master

Hi Now we've branch ignite-1.4 for release thus make sense to update for version for master to 1.5? -- Sergey Kozlov

Heap size in topology snapshot

has a few server nodes and many clients. -- Sergey Kozlov

TCP Loopback Fast Path on Windows 8/2012

Hi Igniters I found the intersting article: http://blogs.technet.com/b/wincat/archive/2012/12/05/fast-tcp-loopback-performance-and-low-latency-with-windows-server-2012-tcp-loopback-fast-path.aspx Could someone take a look how to difficult to implement it for Ignite? -- Sergey Kozlov

Re: LGPL in 1.4 examples

I filed the ticket: Build examples failed from binary fabric package <https://issues.apache.org/jira/browse/IGNITE-1579> On Wed, Sep 30, 2015 at 9:06 AM, Sergey Kozlov <skoz...@gridgain.com> wrote: > > > On Wed, Sep 30, 2015 at 4:10 AM, Dmitriy Setrakyan <dsetra

Re: LGPL in 1.4 examples

Building ignite-examples 1.4.0 [INFO] [WARNING] The POM for org.apache.ignite:ignite-hibernate:jar:1.4.0 is missing, no dependency information available [WARNING] The POM for org.apache.ignite:ignite-schedule:jar:1.4.0 is missing, no dependency information available -- Sergey Kozlov

Re: what is "communication encryption"?

n"? If yes, shouldn't we just say > "ssl=off"? > > D. > Yes, in that case communication encryption is SSL -- Sergey Kozlov

Re: version names

- Forwarded message from Dmitriy Setrakyan < > > > > dsetrak...@apache.org> > > > > > > > - > > > > > > > > > > > > > > Date: Sat, 26 Sep 2015 10:50:08 -0500 > > > > > > > From: Dmitriy Setrakyan <dsetrak...@apache.org> > > > > > > > To: dev@ignite.apache.org > > > > > > > Subject: Re: Need Project Admin rights on JIRA > > > > > > > > > > > > > > Done. > > > > > > > > > > > > > > On Sat, Sep 26, 2015 at 5:27 AM, Raul Kripalani < > > ra...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > > > Hi guys, > > > > > > > > > > > > > > > > I need project admin rights for Ignite in JIRA so I can add a > > new > > > > > > release > > > > > > > > ignite-1.4.1. > > > > > > > > > > > > > > > > For future releases, it would be great if the release manager > > adds > > > > the > > > > > > > next > > > > > > > > micro [and minor [and major]] versions in JIRA when cutting > the > > > > first > > > > > > RC. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > *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.net | twitter: @raulvk > > > > > > > > > > > > > > > > > > > > > > - End forwarded message - > > > > > > > > > > > > > > > > > > > > -- Sergey Kozlov

Fwd: Nodes starts in tests

t/destroy which are much more > >> fast than grid start/stop, > >> I think we should go through a refactoring and use existing nodes > within a > >> suite as much as possible. > >> I believe this can reduce run time of cache related tests like 10 times. > >> > >> Sergi > >> > > -- Sergey Kozlov

Re: ignite 1.4 status

; > > > > > > > > Igniters, > > > > > > > > > > We are not ready to release today. > > > > > > > > > > Alexey Goncharuk is still working on ignite-1171. Alex please > provide > > > > > updates by the end of the day. > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1516 - performance > > > offheap > > > > > query benchmark is not fully recovered. Semyon will be fixing it. > > > Sergi, > > > > > can you please assist? > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-973 - Semyon has > fixed > > > race > > > > > in > > > > > cache logic, but issue is still reproducible due to possible issues > > in > > > > > indexing logic. Sergi, this is on you. Can you please take a look? > > > > > > > > > > --Yakov > > > > > > > > > > > > > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: ignite 1.4 status

I couldn't reproduce IGNITE-973 but would like to get a comment from the reporter. Maybe some points for testing of issue have been missed by me... On Wed, Sep 23, 2015 at 8:48 PM, Sergey Kozlov <skoz...@gridgain.com> wrote: > I'm working to reproduce IGNITE-973 > > On Wed, Sep 2

Re: More query examples

changes need > to take place? > > D. > > On Mon, Dec 7, 2015 at 6:45 AM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > > Hi Igniters > > > > I think queries (SQL) is a killer feature of Ignite. But we still have > the > > example CacheQueryEx

More query examples

into separate examples like CacheQueryExample CacheQueryJoinExample CacheQueryCrossCacheExample CacheQueryExplainExample etc >From my standpoint it will be easier to maintain and extend in future. For ignite user it's more clear where to find the a query functional example. -- Sergey Kozlov

Update version for branch ignite-1.5

Hi Now we released Apache Ignite 1.5.0-b1 and version in branch ignite-1.5 should changed to 1.5.0-b2 Thoughts? -- Sergey Kozlov

Re: [CLOSE] [VOTE] Apache Ignite 1.5.0-b1

gt; > 3. Nick Tikhonov +1 (binding) > > 4. Raul Kripalani +1 (binding) > > 5. Vladislav Jelisavcic +1 > > 6. Alexey Kuznetsov +1 (binding) > > 7. Denis Magda +1 (bnding) > > 8. Sergi Vladykin +1 (binding) > > 9. Roman Shtykh +1 > > > > Thanks everyone! > > > > --Yakov > > > -- Sergey Kozlov

Changes for ignite-jms11 and ignite-mtqq modules for fabric binary package

that such changes are ok? -- Sergey Kozlov

Re: Versioning policies for .NET and CPP

/2015 > - D = 24 * 340 /* days since 01/01/2015 */ + 6 /* hours */ = Ignite.NET > 1.5.0.8166. > > *Pros:* > - Newer versions always have bigger "D" component. GA will be greater than > beta, patch 2 will be greater than patch 1, etc.. > *Cons:* > - Version have to be updated just before release. > > Does anyone have concerns/thoughts about it? > > Vladimir. > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

t; > >- Sergi Vladykin (binding) > > >- 姜 为 > > >- Alexey Kuznetsov > > >- Roman Shtykh > > > > > > Here is the link to vote thread - > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-5-0-final-RC3-td6305.html > > > > > > Ignite 1.5.0.final successfuly released to > > > https://dist.apache.org/repos/dist/release/ignite/1.5.0.final/ > > > > > > Site & Maven will be updated soon. > > > > > > Thanks! > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: 1.5.final

tarted with server classpath (Java 7) <https://issues.apache.org/jira/browse/IGNITE-2175> On Wed, Dec 23, 2015 at 3:10 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > The fix for https://issues.apache.org/jira/browse/IGNITE-2200 has been > merged to ignite-1.5​ > -- Sergey Kozlov

Re: 1.5.final

Hi Last issue has been fixed and we started to prepare the release Apache Ignite 1.5 On Thu, Dec 24, 2015 at 8:12 PM, Sergey Kozlov <skoz...@gridgain.com> wrote: > Yes, sure. > > On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > &

Add suites for JDK8 on ci.ignite.apache.org

should be enough to avoid such issues in future.ues. -- Sergey Kozlov

Re: Add suites for JDK8 on ci.ignite.apache.org

I'm ok for this. On Fri, Dec 18, 2015 at 6:16 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Hm… Why not just switch a few existing tests to JDK8? > > On Fri, Dec 18, 2015 at 5:48 AM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > > Hi > > >

Re: 1.5.final

Yes, sure. On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > If the examples work well with BinaryMarshaller, I think we can push this > ticket to 1.6. Thoughts? > > On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov <skoz...@

Re: 1.5.final

netsov <akuznet...@gridgain.com> wrote: > IGNITE-2252 Add support for cache sql schema in REST topology command > > Fixed, tested, docs updated and merged into release branch. > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > -- Sergey Kozlov

Re: about ignite-hibernate module

tains the code; > > 3 recommended in the official release of the package, including the > building point of the source code, and many other open source projects are > doing so，to facilitate the development of personnel debugging, I now get > the 1.4 version of the source code has been inconsist

Re: Providing an example as part of contribution

on whether to add example >>> or not relying on what functionality is being added. >>> >>> --Yakov >>> >>> 2015-12-29 16:21 GMT+03:00 Sergey Kozlov <skoz...@gridgain.com>: >>> >>> Hi >>>> >>>> https:

Outstanding issues for 1.5

Hi Igniters We still have 195 non-closed issues with fix-version in 1.5 in JIRA . I think that would be great to sort out which issues actually will be in release 1.5 -- Sergey Kozlov

Re: Ignite-1.5 Release

company or project does that, to my knowledge. I would consider it an > anti-pattern. > > Regards, > > *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.net | twitter: @raulvk > -- Sergey Kozlov

Re: EA versioning

"-rc1" part gets stripped. > > > > 5. I would prefer EA versions being available through maven. I know that > > there are different opinions on this and I know the reasoning for > opinions, > > but from my standpoint this will save us from managing additional repos > and > > make everything transparent. > > > > > > Thanks! > > > > --Yakov > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > -- Sergey Kozlov

Ignite camel streamer

a look and fix it? Thanks! -- Sergey Kozlov

Re: Javadoc warnings at Ignite 1.5

> >> > >> I've checked output of prerelease build of Ignite 1.5 and found javadoc > >> warnings like > >> CamelStreamer.java:51: warning - Tag @link: malformed: > >> "StreamMultipleTupleExtractor)" > >> > >> Raul, seems that was your changes. Could you please fix it? > >> > > > -- Sergey Kozlov

Re: Update scala to 2.11.7 and spark to 1.5.2

t; > If no I will create issue and update. > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > -- Sergey Kozlov

Re: MS VS 2010 for platforms

with .NET 4, but, because we > support VS2010, we have to stick to C# 4. > This is unfortunate, because C# 6 does offer many nice improvements. > > On Wed, Jan 13, 2016 at 1:38 PM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > > Hi Igniters > > >

MS VS 2010 for platforms

Hi Igniters I found that build of platforms (both .Ner and C++) requires Visual Studio 2010 Professional. Could someone explain: - Why we do not suggest to use Visual Studio Community? - VS 2010 seems a bit outdated.What's about VS 2015? -- Sergey Kozlov

HTTP Rest API: increment/decrement or append/prepend are candidates to deprecate?

for 1.8. Any such operation should be implemented via SQL level. Thoughts? -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Ignite Download links broken

te.apache.org/download.html#binaries> >> >> Thanks, >> >> Christos > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Ignite REST API is not actually RESTful

caches/partitionedCache/keys/myKey/ > > DELETE /ignite/caches/partitionedCache/keys/myKey/ > > > > > > I think we should deprecate current API and provide a new one that > follows > > the guidelines. > > A good writeup on a proper REST API design can be found t

Re: Add key type detection for REST HTTP GET command

mon built-in types such as Integer, Long, UUID,... and user classes that > a valid JavaBeans? > > Sample: http://host:port > /ignite?cmd=get=1=myCache=Long > > Thoughts? > > -- > Alexey Kuznetsov > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Add key type detection for REST HTTP GET command

nal key type in REST HTTP get command > https://issues.apache.org/jira/browse/IGNITE-3345 > > On Tue, Jun 21, 2016 at 8:13 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > I also like the idea. Should we file a ticket? > > > > On Mon, Jun 20, 2

Re: IGNITE-3337

t; > > Hello, > > > > I have raised the PR[1] for the following Jira ticket[2]. > > > > Please review and let me know any feedback > > > > Regards > > Saikat > > > > [1] https://github.com/apache/ignite/pull/816 > > [2] https://issues.apache.org/jira/browse/IGNITE-3337 > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Full API coverage enhancement

e* combinations? > > I forgot about custom BinaryConfiguration at IgniteConfiguration for > BinaryMarshaller. So, at least 6 IgniteConfigurations. > > -- Artem -- > > On Mon, Feb 8, 2016 at 5:17 PM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > > Hi Artem > >

Re: Full API coverage enhancement

branch under hard development and > you > > > it > > > > > can > > > > > > not work (have compilation or test errors) at some moments. > > > > > > > > > > > > Good luck! > > > > > > > > > > > > -- Artem -- > > > > > > > > > > > > On Tue, Feb 2, 2016 at 9:45 PM, Dmitriy Setrakyan < > > > > dsetrak...@apache.org > > > > > > > > > > > > wrote: > > > > > > > > > > > >> Artem, > > > > > >> > > > > > >> This is great. I have noticed from the ticket that you have > > created > > > > some > > > > > >> initial suite already. Is there a branch I can look at it? > > > > > >> > > > > > >> D. > > > > > >> > > > > > >> On Tue, Feb 2, 2016 at 10:02 AM, Artem Shutak < > > ashu...@gridgain.com > > > > > > > > > >> wrote: > > > > > >> > > > > > >> > Igniters, > > > > > >> > > > > > > >> > I'm working on an enhancement of Full API coverage [1] [2]. > > > > > >> > > > > > > >> > Ignite already has Full API test, but currently it's hard to > > test > > > > all > > > > > >> > configuration combinations. > > > > > >> > > > > > > >> > Feel free to add comments in the jira if you have any thought. > > > > > >> > > > > > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-2521 > > > > > >> > [2] > > > > > >> > > > https://cwiki.apache.org/confluence/display/IGNITE/Implementing+Tests > > > > > >> > > > > > > >> > Thanks, > > > > > >> > -- Artem -- > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: ODBC processor default behaviour

second node fails to start because ODBC port is > already > > taken > > by the first node. > > > > Does anyone has ideas what is the best way to fix that? > > > > Best Regards, > > Igor > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Ignite 1.6 release timelines

GNITE-2948 < > https://issues.apache.org/jira/browse/IGNITE-2948 > > > > > > - > > > > > > > > Optimize usage of GridCacheConcurrentMap > > > > > > > > IGNITE-1786 < > https://issues.apache.org/jira/browse/IGNITE-1786 > > > > > > - > > > > > Need > > > > > > > to > > > > > > > > implement ODBC driver for Ignite > > > > > > > > > > > > > > > > Once these issues are resolved, we can move to the testing > > phase > > > > > > > (probably > > > > > > > > a week), and then send it for the vote. > > > > > > > > > > > > > > > > D. > > > > > > > > > > > > > > > > On Fri, Apr 29, 2016 at 3:12 AM, Yakov Zhdanov < > > > > yzhda...@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > > > > >> I think we are almost done with odbc support and I hope that > > we > > > > can > > > > > > > >> release > > > > > > > >> about mid or second half of May. > > > > > > > >> > > > > > > > >> --Yakov > > > > > > > >> > > > > > > > >> 2016-04-27 11:13 GMT+03:00 sssow <ss...@hotmail.com>: > > > > > > > >> > > > > > > > >> > Hi, > > > > > > > >> > When will you release 1.6? > > > > > > > >> > Thank you, > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > -- > > > > > > > >> > View this message in context: > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-1-6-release-timelines-tp7388p8618.html > > > > > > > >> > Sent from the Apache Ignite Developers mailing list > archive > > at > > > > > > > >> Nabble.com. > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Data compression in Ignite 2.0

e > implement > > > support for compression on Ignite core level SQL engine will be able to > > > detect that data is compressed and properly handle such data. > > > > > > What do you think? > > > If community consider this feature useful I will create issue in JIRA. > > > > > > [1] > > > > > > > > > http://www.ibm.com/developerworks/data/library/techarticle/dm-1205db210compression/ > > > > > > -- > > > Alexey Kuznetsov > > > > > > > > > -- > Alexey Kuznetsov > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Ignite 2.0 tasks/roadmap

Would be nice to > > assign > > > >> a > > > >>>> release manager for Ignite 2.0 and document all the discussed > > features > > > >> on > > > >>>> the Wiki. > > > >>>> > > > >&

Re: Ignite 2.0 tasks/roadmap

> > 2016-08-11 17:24 GMT+03:00 Sergey Kozlov <skoz...@gridgain.com>: > > > HI > > > > Due to approach to disable to store more than one type per cache the > cache > > use becomes similar the table use for databases. > > So I suppose would be good to int

Re: Ignite 2.0 tasks/roadmap

t;? > > How grouping will help? > To do some operation, for example, clear on group of cashes at once? > > 11 Авг 2016 г. 22:06 пользователь "Sergey Kozlov" <skoz...@gridgain.com> > написал: > > > I mean not only SQL features for caches. Single type per

Re: Ignite 1.7 RELEASE_NOTES

t; > > > > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me. > > > There > > > > are likely more noteworthy changes since 1.6. > > > > > > > > Let's discuss the changes to be included in release notes and fix > them. > > > > > > > > Please reply to this email with your proposals. > > > > > > > > Pavel. > > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: DML data streaming

concrete columns/fields > > lost - this is analogous to > > https://issues.apache.org/jira/browse/IGNITE-4489, but hardly can be > > fixed as long as probably it would hit performance and would be > > unresonably complex to implement. > > > > I suggest that we drop all except INSERT and introduce optional flag > > for its totally correct semantic behavior as described above. > > > > - Alex > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: DDL implementation details

t; > > > >> > > > > > > > >> If we want to limit the user with having single type > > descriptor > > > > per > > > > > > > >> cache (i.e. cache has only one type of stored entities - > BTW, > > > > w

Re: [VOTE] Apache Ignite 1.9.0 RC1

; works fine. > > Look at "*New --allow-script-in-comments option for javadoc":* > http://www.oracle.com/technetwork/java/javase/8u121-relnotes-3315208.html > > > > 2017-03-02 10:53 GMT+03:00 Sergey Kozlov <skoz...@gridgain.com>: > > > Hi > > > > I

Apache Ignite 1.9 testing

ould someone take a look? -- Sergey Kozlov

Re: Ignite 2.0 tasks/roadmap

er > > and > > > that the constraints will not be violated. > > > > > > However, I think this is not a very clean way to achieve the result. > > > Probably we should just provide better support for this use case in > 2.0. > > > Basically, we somehow need to

Re: Ignite 2.0 tasks/roadmap

7, 2016, at 3:58 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > > wrote: > > > > > > Sergey, I don't think we can fit redesigning of HTTP/REST into our 2.0 > > > release. The 2.0 already looks pretty packed. Perhaps we should plan it > > for > >

Re: Ignite 2.0 tasks/roadmap

additional requirements to the next generation > of REST API implementation. > > Does it make sense to you? > > — > Denis > > > On Sep 9, 2016, at 1:56 AM, Sergey Kozlov <skoz...@gridgain.com> wrote: > > > > Vova, > > > > There are more issues t

Re: Ignite 2.0 tasks/roadmap

//issues.apache.org/jira/browse/IGNITE-961 > > > > — > > Denis > > > > > On Sep 8, 2016, at 1:54 AM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > > > > > I agree with Alexey. > > > > > > The key point is a chance to don't

Re: Support for Spark 2.0

> error: not found: value logError > > [ERROR] logError("Failed to start Ignite.", e) > > [INFO] ^ > > [ERROR] > > /home/spark/code/ignite/modules/spark/src/main/scala/ > org/apache/ignite/spark/IgniteContext.scala:164: > > error: not found: value logInfo > > [ERROR] logInfo("Will stop Ignite nodes on " + workers + " > > workers") > > [ERROR] ^ > > [ERROR] 6 errors found > > [INFO] > > > > Thanks! > -- Sergey Kozlov GridGain Systems www.gridgain.com

Yardstick benchmark roadmap

/ideas/objections are welcome. -- Sergey Kozlov

Re: Ignite 2.0 tasks/roadmap

ion. > > — > Denis > > > On Nov 10, 2016, at 1:27 AM, Sergey Kozlov <skoz...@gridgain.com> wrote: > > > > Hi > > > > It seems the Spring dependency looks outdated for now. Apache Ignite > still > > uses 4.1.0 released two years ago. Could we inclu

Re: Ignite 2.0 tasks/roadmap

Magda <dma...@gridgain.com>: > > > I’ve created an umbrella ticket for REST > > https://issues.apache.org/jira/browse/IGNITE-3879 < > > https://issues.apache.org/jira/browse/IGNITE-3879> > > > > And I wouldn’t deprecate anything until the next version gets

Re: TX savepoints

n objects > - rollback implementation for different types of transactions - drain local > tx buffers, release remote locks for pessimistic transactions, etc. > > 5 days - testing, benchmarking, fixing issues. > > Please leave your comments here. I will file a ticket after we discuss this > and put our summary to it. > > Thanks! > > --Yakov > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Create separate thread pool for query execution

s email please notify us immediately and do not copy it or use it for > any purpose, nor disclose its contents to any other person. This email does > not constitute the commencement of legal relations between you and Misys. > Please refer to the executed contract between you and the relevant member > of the Misys group for the identity of the contracting party with which you > are dealing. > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Apache Ignite 1.8 Release

>> >>> > > >>> >>> Do you think it will be possible to complete all the .NET > usability > > >>> >>> tickets [2] under 1.8 and roll them out to the Apache Ignite > users? > > >>> >>> > > >>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-3921 < > > >>> https://issues.apache.org/jira/browse/IGNITE-3921> > > >>> >>> [2] https://issues.apache.org/jira/browse/IGNITE-4114 < > > >>> https://issues.apache.org/jira/browse/IGNITE-4114> > > >>> >>> > > >>> >>> — > > >>> >>> Denis > > >>> >>> > > >>> >>> On Nov 9, 2016, at 6:55 AM, Denis Magda <dma...@gridgain.com > > > >>> dma...@gridgain.com>> wrote: > > >>> >>> > > >>> >>> Do we have a branch for ignite-1.8? Is there anyone who can take > > over > > >>> the > > >>> >>> release process of 1.8? > > >>> >>> > > >>> >>> — > > >>> >>> Denis > > >>> >>> > > >>> >>> On Nov 8, 2016, at 9:01 PM, Alexander Paschenko < > > >>> >>> alexander.a.pasche...@gmail.com <mailto:alexander.a.paschenko@ > > >>> gmail.com>> wrote: > > >>> >>> > > >>> >>> Current status on DML: > > >>> >>> > > >>> >>> - Basic data streamer support implemented (basicness is mostly > > about > > >>> >>> configuration - say, currently there's no way to specify > streamer's > > >>> >>> batch size via JDBC driver, but this can be improved easily). > > >>> >>> > > >>> >>> - Fixed all minor stuff agreed with Vladimir. > > >>> >>> > > >>> >>> - There are some tests that started failing after binary hash > codes > > >>> >>> generation rework made by Vladimir in ignite-4011-1 branch, I > will > > ask > > >>> >>> him to look into it and fix those. Failing tests live in > > >>> >>> GridCacheBinaryObjectsAbstractSelfTest, and are as follows: > > >>> >>> - testPutWithFieldsHashing > > >>> >>> - testCrossFormatObjectsIdentity > > >>> >>> - testPutWithCustomHashing > > >>> >>> I added them personally during working on first version of auto > > >>> >>> hashing few weeks ago, and what they do is test these very > hashing > > >>> >>> features. Again, prior to Vlad's rework those tests passed. So > > could > > >>> >>> you please take a look? > > >>> >>> > > >>> >>> - Working on Sergey V.'s comments about current code. > > >>> >>> > > >>> >>> - Alex > > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > > >>> >> > > >>> > > > >>> > > > >>> > > >>> > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Apache Ignite 1.8 Release

gt;>>>> [2] https://issues.apache.org/jira/browse/IGNITE-3825 < > > > >>>> https://issues.apache.org/jira/browse/IGNITE-3825> > > > >>>>>> > > > >>>>>> On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda <dma...@apache.org > > > >>>> <mailto:dma...@apache.org>> wrote: > > > >>>>>> > > > >>>>>>> *Alexander P., Igor S.,* > > > >>>>>>> > > > >>>>>>> When will your merge all DML and ODBC (PDO) related changes > into > > > 1.8 > > > >>>>>>> branch? I’m looking forward to go through PDO [1] documentation > > > and be > > > >>>> sure > > > >>>>>>> that everything works as described on my side. > > > >>>>>>> > > > >>>>>>> *Pavel,* > > > >>>>>>> > > > >>>>>>> Do you think it will be possible to complete all the .NET > > usability > > > >>>>>>> tickets [2] under 1.8 and roll them out to the Apache Ignite > > users? > > > >>>>>>> > > > >>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-3921 < > > > >>>> https://issues.apache.org/jira/browse/IGNITE-3921> > > > >>>>>>> [2] https://issues.apache.org/jira/browse/IGNITE-4114 < > > > >>>> https://issues.apache.org/jira/browse/IGNITE-4114> > > > >>>>>>> > > > >>>>>>> — > > > >>>>>>> Denis > > > >>>>>>> > > > >>>>>>> On Nov 9, 2016, at 6:55 AM, Denis Magda <dma...@gridgain.com > > > > > >>>> dma...@gridgain.com>> wrote: > > > >>>>>>> > > > >>>>>>> Do we have a branch for ignite-1.8? Is there anyone who can > take > > > over > > > >>>> the > > > >>>>>>> release process of 1.8? > > > >>>>>>> > > > >>>>>>> — > > > >>>>>>> Denis > > > >>>>>>> > > > >>>>>>> On Nov 8, 2016, at 9:01 PM, Alexander Paschenko < > > > >>>>>>> alexander.a.pasche...@gmail.com <mailto:alexander.a.paschenko@ > > > >>>> gmail.com>> wrote: > > > >>>>>>> > > > >>>>>>> Current status on DML: > > > >>>>>>> > > > >>>>>>> - Basic data streamer support implemented (basicness is mostly > > > about > > > >>>>>>> configuration - say, currently there's no way to specify > > streamer's > > > >>>>>>> batch size via JDBC driver, but this can be improved easily). > > > >>>>>>> > > > >>>>>>> - Fixed all minor stuff agreed with Vladimir. > > > >>>>>>> > > > >>>>>>> - There are some tests that started failing after binary hash > > codes > > > >>>>>>> generation rework made by Vladimir in ignite-4011-1 branch, I > > will > > > ask > > > >>>>>>> him to look into it and fix those. Failing tests live in > > > >>>>>>> GridCacheBinaryObjectsAbstractSelfTest, and are as follows: > > > >>>>>>>- testPutWithFieldsHashing > > > >>>>>>>- testCrossFormatObjectsIdentity > > > >>>>>>>- testPutWithCustomHashing > > > >>>>>>> I added them personally during working on first version of auto > > > >>>>>>> hashing few weeks ago, and what they do is test these very > > hashing > > > >>>>>>> features. Again, prior to Vlad's rework those tests passed. So > > > could > > > >>>>>>> you please take a look? > > > >>>>>>> > > > >>>>>>> - Working on Sergey V.'s comments about current code. > > > >>>>>>> > > > >>>>>>> - Alex > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> > > > >>>>>> > > > >>>>> > > > >>>>> > > > >>>> > > > >>>> > > > > > > > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Apache Ignite 1.8 Release

tional) module because of Kryo based > serializers may bring not needed dependency. > > Igor, could you confirm this? > > On Fri, Nov 25, 2016 at 6:58 PM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > >> Hi >> >> Could someone explain why Cassandra module

Re: Apache Ignite 1.8 Release

in pull > requests/reviewed/fixed/merged (no issues unapproached/not fixed). > > - Alex > > > > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov <skoz...@gridgain.com>: > > Hi > > > > I found two issues for 1.8: > > IGNITE-4304 ClusterTopologyChecked

Re: Apache Ignite 1.8 Release

NITE-4323> On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov <akuznet...@apache.org> wrote: > Vladimir, > > IGNITE-3443 Implement collecting what SQL statements executed on cluster > and their metrics. > > -- > Alexey Kuznetsov > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Apache Ignite 1.8 Release

Hi The list of issues found today: IGNITE-4334 DML: INSERT INTO SELECT FROM statement fails if copy from partitioned to replicated cache <https://issues.apache.org/jira/browse/IGNITE-4334> On Tue, Nov 29, 2016 at 9:56 PM, Sergey Kozlov <skoz...@gridgain.com> wrote: > Denis

Re: Major release 2.0 and compilation

approach and decide whether to > > keep deprecation or not separately for every piece of API, depending on > > possible impact on both users and Ignite developers. But normally I would > > leave deprecation unless there is a strong reason to remove it. > > > > Thoughts? > > > > Vladimir. > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: ignite-spark module in Hadoop Accelerator

ibs should not > be > > included into hadoop-accelerator download. Spark integration is not part > of > > Ignite Hadoop Accelerator and should be included only into the Ignite > > fabric download. > > > > D. > > > > > > > > On Tue, Dec 6, 20

Re: Apache Ignite 1.8 Release

andle it this time? > https://ignite.apache.org/download.cgi#docker <https://ignite.apache.org/ > download.cgi#docker> > > Sergey K., Nikolay T., are you aware about this? > > — > Denis > > > On Dec 3, 2016, at 12:54 PM, Sergey Kozlov <skoz...@gridgain.com>

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

nabble. > com/VOTE-Apache-Ignite-1-8-0-RC1-td12754.html > <http://apache-ignite-developers.2346864.n4.nabble. > com/VOTE-Apache-Ignite-1-8-0-RC1-td12754.html>* > > Ignite 1.8.0 will be released soon. Woohoo! > > Vladimir. > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

ip < >>>>> http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip> >>>>> http://apache.osuosl.org/ignite/1.8.0/apache-ignite- >>>>> >>>> fabric-1.8.0-bin.zip >>> >>>> < >>>> >>&

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

e presented in the Maven. Say geospacial is only published up to > 1.2.0, etc. > > It looks weird to me as well. Could you start a separate discussion on the > dev list in order to trigger attention of the guys who usually take care > about Ignite’s build system? > > — > Denis -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Extend TcpDiscoveryVmIpFinder functionality

e.g. 127.0.0.1:47500..47509, > but > > we don't have this for addresses. If we implement this I would suggest > the > > same approach, e.g 192.168.0.1..5:47500 > > > > Thoughts? > > > > --Yakov > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: DDL implementation details

ve, I think we should start > working on DDL implementation to use the default settings, as specified in > Alexander's email. > > Also agree with the stop-the-world on the cache for index creation. We can > always improve on it in future. > > D. > > On Wed, Jan 11, 2017

Re: Extend TcpDiscoveryVmIpFinder functionality

possible we can support ranges for every byte > applying a format like the one below. > > 10.0.0.[1-10] > [10-11].0.0.[1-10] > 128.[165-165].10.[1-100] > > What do you think? > > — > Denis > > > On Jan 10, 2017, at 3:08 AM, Sergey Kozlov <skoz...@gridgain.

Re: DDL implementation details

ll be against it) or > > > introduce some kind of name prefix that would tell SQL engine that > > > certain column is a key field column. > > > > > > Of course, this problem disappears is key is of SQL type. > > > > > > Regarding CREATE INDEX: probably at first we will have to implement > > > this in "stop-the-world" manner, i.e. all cache will be blocked during > > > the index's initial buildup. > > > > > > Any thoughts? > > > > > > Currently I'm working on parsing of those commands as that will be > > > needed anyway and does not affect further implementation. > > > > > > - Alex > > > > > > > > > > > -- > > Alexey Kuznetsov > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Apache Ignite 1.8 Release

l as all in all. > > What's the status of release vote guys? > > > > - Alex > > > > 2016-12-03 2:08 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > >> Alexander, thanks for making the fixes to DML. Are you adding JUnits for > >> all the fix

Re: Apache Ignite 1.8 Release

; > > On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov <voze...@gridgain.com> > wrote: > > > > Folks, > > > > I need to create RELEASE NOTES. Please advise which notable tickets you > > completed as a part of 1.8 release. > > > > Vladimir. >

Re: ignite-spark module in Hadoop Accelerator

gt;>>>>> a separate delivery. > >> >>>>>> What if we start releasing the accelerator as a part of the > >> standard > >> >>>>>> fabric binary putting hadoop-accelerator libs under ‘optional’ > >> folder? > >> >&g

Re: ignite-spark module in Hadoop Accelerator

gt; > >> https://issues.apache.org/jira/browse/IGNITE-3822 > >> > >> — > >> Denis > >> > >> On Nov 19, 2016, at 1:26 PM, Valentin Kulichenko < > >> > >> valentin.kuliche...@gmail.com> wrote: > >> > >> > >> Hadoop Acce

Re: Dedicated readme.io documentation for Ignite integrations

the > integrations > > >> were > > >>>> documented on our main readme.io <http://readme.io/> making the > > overall > > >>>> documentation a bit messy. > > >>>> > > >>>> I’ve decoupled the integrations from the core modules by moving them > > to > > >> a > > >>>> new documentation domain “Apache Ignite Integrations” < > > >>>> https://apacheignite-mix.readme.io/docs>. As a result integrations > as > > >>>> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the > > streamers > > >>>> reside there. > > >>>> > > >>>> Dmitriy, looks like we have to upgrade readme.io subscription to > > >>>> “Developer Hub” for the new documentation domain because now there > is > > >> now > > >>>> way to change the appearance. Appearance themes settings are poor. > > Could > > >>>> you handle this? > > >>>> > > >>>> — > > >>>> Denis > > >> > > >> > > > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: Apache Ignite 1.8 Release

t;>> > >>> DML is done as for now, example is done too, currently there's no open > >>> issues related with it (besides documentation which I'm working on). > >>> Yesterday's problem turned out to be binary/SQL engine (pre DML) > >>> related

Re: Apache Ignite 1.8 Release

t;>> > >>> Alexander P. and Igor S. please pull together and fix this issue before > >>> 1.8 is sent for vote. > >>> > >>> The second issue is related to ODBC and affects the usability only. > Igor > >>> S., please try to address it as

Extend TcpDiscoveryVmIpFinder functionality

of the netmask 10.0.0.1/255.255.255.0:48500 2) with using of the network prefix 10.0.0.1/24:48500 Any comments/objections are welcome -- Sergey Kozlov

Re: Extend TcpDiscoveryVmIpFinder functionality

- should we support range notation for each > byte in IP address? I think we should. > > --Yakov > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

> > ignite-yardstick module in the apache-ignite binary assembly? We can > > put > > > it > > > > in the libs/optional along with an others optional libraries, or we > can > > > > create a new directory named "tools" in the root directory and put > > > > "ignite-yardstick" in it, or we can find another solution. > > > > > > > > Best regards > > > > Oleg > > > > > > > > > > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

gt; Is there anyone else who is concerned about “libs/optional”? If there’re > > not, I would agree on this and get down to the implementation. > > > > — > > Denis > > > > > On Dec 19, 2016, at 1:10 AM, Sergey Kozlov <skoz...@gridgain.com> > wrote

  1   2   3   4   >