Upcoming Apache Ignite Events

Folks, Check up our the news page [1]! We’re approaching cool meetups and webinars to be conducted by our community members. Take an action - sign up and attend! And if you have anything to share the world about Ignite reach me out ;) * Webinar: Distributed ACID Transactions in Apache Ignite

Enabling memory and persistence metrics

Sergey, How do I enable MemoryMetrics and PersistenceMetrics metrics aggregation if a have only the default region set and don’t wanna use the JMX beans available? Struggling to find any API method to do that. Hope we didn’t forget to support such an obvious thing. — Denis

Re: Enabling memory and persistence metrics

ration.metricsEnabled, MemoryPolicyConfiguration. > metricsEnabled > > On Sat, Jul 8, 2017 at 2:55 AM, Denis Magda <dma...@apache.org> wrote: > >> Sergey, >> >> How do I enable MemoryMetrics and PersistenceMetrics metrics aggregation >> if a have only the de

Re: JIRA permissions

Hello Evgeniy, Granted you the required permissions. Please go ahead and pick a ticket of interest. Below is auxiliary info that might be useful to you. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Re: Hello.

Hi, Welcome to the Ignite community! Please subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on

Re: Apache Ignite 2.1 scope

not necessarily represent the views of any company the author >>>>>> might be affiliated with at the moment of writing. >>>>>> >>>>>> >>>>>> On Tue, Jul 4, 2017 at 3:20 AM, Vladimir Ozerov <voze...@gridgain.com >>>> >>

Fwd: [ignite] your /dist/ artifacts - 1 BAD signature

Igniters, Especially Sergey K., Ilya S and Alexey Chetaev, Could you explain what those “TEST” artifacts are doing in the dist folder? Are you trying out the new release procedure? In addition to the questions, please fix the issue following the issue brought out below. — Denis > Begin

Re: Ignite Teamcity email notifications

ite-2.* > +:pull/2296/head > And enable notifications on > - build fails (only first failing and/or including your changes), > - and successful build (optionally only first build after failed). > > Best Regards, > Dmitriy Pavlov > > пн, 3 июл. 2017 г. в 17:43,

Re: [VOTE] Apache Ignite 2.1.0 RC1

-1 Because of the lgpl libraries issue. Please fix the bug and restart the vote. Denis On Saturday, July 15, 2017, Ilya Suntsov wrote: > Lgpl binaries should not to be in svn. This build will be removed. > > 15 июля 2017 г. 1:52 PM пользователь "Sergey Kozlov"

Re: New blog post: Implementing Ignite.NET Plugin, interacting with Java

Pavel, the blog post is well deserved to be mentioned on this documentation page! https://apacheignite-net.readme.io/docs/plugins Please add it using a “callout” block of readme. — Denis > On Jul 17, 2017, at 3:31 AM, Pavel Tupitsyn

Re: [CANCEL] [VOTE] Apache Ignite 2.1.0 RC1

Guys, what’s the status? Who and when is going to send the next build for vote? — Denis > On Jul 17, 2017, at 5:50 AM, Vladimir Ozerov <voze...@gridgain.com> wrote: > > Officially cancelling the vote. > > -- Forwarded message ------ > From: Denis Magda <

Re: [VOTE] Apache Ignite 2.1.0 RC2

+1 (binding) — Denis > On Jul 17, 2017, at 9:42 PM, Vladimir Ozerov wrote: > > Igniters! > > We have uploaded a 2.1.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc2/ > > Git tag name is > 2.1.0-rc2 > > This release includes the following

Fwd: July 19 webinar: Distributed ACID transactions in Apache® Ignite™

Cross-posting to the dev list > Begin forwarded message: > > From: Dieds > Subject: July 19 webinar: Distributed ACID transactions in Apache® Ignite™ > Date: July 18, 2017 at 9:50:52 AM PDT > To: u...@ignite.apache.org > Reply-To: u...@ignite.apache.org > >

[VOTE] Apache Ignite 2.1.0 RC3

Igniters, Setting off the vote one more time. Hope I’ll be successful this time, keeping fingers crossed :) We have uploaded a 2.1.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/ Git tag name is 2.1.0-rc3 This release includes the following changes: Ignite: *

Re: [VOTE] Apache Ignite 2.1.0 RC3

;dreamx@gmail.com > <javascript:;>>: > > > > > > > > > > > +1 > > > > > > > > > > > > > 21 июля 2017 г., в 7:48, Valentin Kulichenko < > > > > > > valentin.kuliche...@gmail.com <java

Meetup/Live Streaming: An Intro to Ignite

Igniters, If you live in London or close to it, stop by the meetup Akmal is giving there tomorrow: https://ignite.apache.org/events.html#Brighton-Java-241395191 Rest of us can grasp an opportunity of the live streaming. Find the link on this page:

Re: [VOTE] Apache Ignite 2.1.0 RC3

g/dev/new-committers-guide.html#set-up-security-and-pgp-keys > > On Sat, Jul 22, 2017 at 01:00PM, Konstantin Boudnik wrote: >> Am I missing the location of the signing keys? I cannot verivy the signature >> of the archive. >> >> -1 (binding) until then. >> >&g

Re: [VOTE] Apache Ignite 2.1.0 RC3

> Disclaimer: Opinions expressed in this email are those of the author, > and do not necessarily represent the views of any company the author > might be affiliated with at the moment of writing. > > > On Mon, Jul 24, 2017 at 10:46 AM, Denis Magda <dma...@apache.org> wrote: &g

Re: Cache Metrics

Guys, What if we calculate it on both sides? The client will keep the total time needed to complete an operation including network hoops while a server (primary or backup) will count only local time. — Denis > On Jul 17, 2017, at 7:07 AM, Andrey Gura wrote: > > Hi, > > I

[ANNOUNCE] Apache Ignite 2.1.0 Released

The Apache Ignite Community is pleased to announce the release of Apache Ignite 2.1.0 [1]. https://blogs.apache.org/ignite/entry/apache-ignite-2-1-a This release incorporates a tremendous feature that was donated to the project - Ignite Persistent Store that altogether with the Durable Memory

Re: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

honov (binding) >> - Alexey Kuznetsov (binding) >> - Yakov Zhdanov (binding) >> - Konstantin Boudnik (binding) >> - Andrey Gura (binding) >> - Denis Magda (binding) >> >> Vote thread: >> >> http://apache-ignite-developers.2346864.n4.nabble. >> com/VOTE-Apache-Ignite-2-1-0-RC4-td19969.html >> >> Ignite 2.1.0 will be released soon. Woohoo! >>

Tomorrow, July 27: Apache Ignite Meetup in Silicon Valley

Folks of the valley, Bay Area and San-Francisco come over to community’s meetup (https://www.meetup.com/Bay-Area-In-Memory-Computing/events/241381155/) to learn more about the internals of durable memory architecture and Ignite Persistent Store that will be released in Apache Ignite 2.1

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 (binding) — Denis > On Jul 24, 2017, at 6:32 AM, Anton Vinogradov wrote: > > Igniters, > > This vote based on same files as RC3. > Only one change is that I signed zips with my signature. > KEYS files (https://dist.apache.org/repos/dist/release/ignite/KEYS) was > updated

Re: Ignite 2.1?

Keep an eye on the voting threads named like this one "[VOTE] Apache Ignite 2.1.0 RC2”. One the vote is passed and all the issues are resolved the release is to be rolled out. In any case, an announcement will be sent to the @dev list as well. — Denis > On Jul 19, 2017, at 10:26 AM, Muthu

Re: SSL certificate for the CI server

Hi Cos, Alexey Chetaev, please join the conversation and share your thoughts on this. — Denis > On Jul 19, 2017, at 9:44 AM, Konstantin Boudnik wrote: > > Hey guys. > > I've noticed that https://ci.ignite.apache.org/ has two issues: > - it has the invalid certificate > - the

Re: Brand new JMH and Yardstick benchmarks

Alexander, Sounds like a useful addition, thanks! Does it make sense to document the usage and specificities you are mentioning on an Ignite wiki page? — Denis > On Jul 20, 2017, at 9:59 AM, Александр Меньшиков wrote: > > Hi, guys. I have written benchmarks for

Re: My first contribution.

Congrats! Keep the pace ;) — Denis > On Jul 20, 2017, at 10:28 AM, Vitaliy Biryukov > wrote: > > Guys, I've finished my first issue (IGNITE-5452). > > > It contained 2 issues: > > 1. GridTimeoutProcessor can't be stopped if TimeoutObject eats >

Re: "not null" constraint support

Hi Sergey, That will be an excellent addition to DDL features set. The proposed changes look good to from the public API standpoint. Alexander P., Sergi, Vovan, please share your thoughts. — Denis > On Jul 20, 2017, at 12:27 PM, Sergey Kalashnikov > wrote: > > Hi

Re: Ignite Teamcity email notifications

What’s about c...@ignite.apache.org ? If there are no objections I’ll create the alias. — Denis > On Jun 29, 2017, at 11:53 AM, Dmitry Pavlov wrote: > > Hi Dmitriy, > > At the first step we need some email address to send notifications

Re: Distributed scheduling

Hi Alex, A similar topic was raised and discussed some time ago: http://apache-ignite-developers.2346864.n4.nabble.com/Tasks-Scheduling-and-Chaining-td14293.html Probably, we need to reincarnate

Re: Get a ticket

Hello Andrei, Done. Please go ahead and pick a ticket of interest. — Denis > On Jun 29, 2017, at 10:46 AM, Elen Code wrote: > > Dear Ignite team, > Could you please add me to the contributor list. My username is: Litanontaru. > > Kind regards,Andrei > >

Re: Ignite Teamcity email notifications

Trigged the alias creation. Will let you know once it’s ready for usage. — Denis > On Jun 29, 2017, at 3:51 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > I like this alias. > > On Thu, Jun 29, 2017 at 3:43 PM, Denis Magda <dma...@apache.org>

Re: golang client for Ignite

upport of transactions via ODBC... > > Yes, I would like to develop true native client. > How can I get protocol specification to develop client BinaryMarshaller with > pure golang? > > Thanks, > Aleksandr > > From: Denis Magda > Sent: 28 июня 2017 г. 2:00 > To: dev@ign

Re: [External] Triggering cache updates in Ignite

> On Jun 28, 2017, at 4:34 AM, Bosko Devetak <bosko.deve...@booking.com> wrote: > > Hi Denis, > > On Wed, Jun 28, 2017 at 12:13 AM, Denis Magda <dma...@gridgain.com > <mailto:dma...@gridgain.com>> wrote: > > Hello Daniel, > > That looks promis

Re: Request for contributor permission

Hi, Added you to the contributors list. Please go ahead and assign the tickets on yourself. — Denis > On Jun 30, 2017, at 12:10 AM, Александр Метерко > wrote: > > Dear Ignite team, > > I would like to start contributing to your project starting with ticket >

Re: Ignite Persistent Store: Ready for merge?

any outstanding bugs and merge it to > master. > > D. > > On Tue, Jun 27, 2017 at 3:35 PM, Denis Magda <dma...@apache.org> wrote: > >> Guys, >> >> According to the discussions I see on the @dev list the donated Ignite >> Persistent Store [1] is stab

Re: Apache Ignite 2.1 scope

ted in 2.1. >>> >>> >>> >>> On 01.06.2017 18:43, Vladimir Ozerov wrote: >>> >>>> Folks, >>>> >>>> We are almost reached proposed feature-complete date (June 2), Could you >>>> please share current sta

Re: Supported and Unsupported SQL

Fully support this idea. That’ll help a lot our users and make things clearer for us. — Denis > On Jul 3, 2017, at 8:41 AM, Dmitriy Setrakyan wrote: > > Igniters, > > Vladimir pointed out that PostgreSQL has a very detailed list of supported > and unsupported features:

Re: JIRA Access - Ignite

Welcome! Added you to the list. — Denis > On Jul 2, 2017, at 11:11 PM, Ankur Kumar wrote: > > ankurkuma...@gmail.com is my JIRA Id. Please grant the permission. > > On Tue, Jun 27, 2017 at 2:16 PM, Alexey Kuznetsov > wrote: > >> Hi Ankur, >>

Re: Ignite Teamcity email notifications

On Jun 29, 2017, at 4:10 PM, Denis Magda <dma...@apache.org> wrote: > > Trigged the alias creation. Will let you know once it’s ready for usage. > > — > Denis > >> On Jun 29, 2017, at 3:51 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: >> >>

Re: Apache Ignite 2.1 scope

1 release >> to >>> this branch. The rest commits should go to master. >>> >>> Vladimir. >>> >>> On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov <voze...@gridgain.com> >>> wrote: >>> >>>> Hi Denis, >>>&g

Re: abbrevation rules plugin

nload. > > D. > > On Wed, Jul 5, 2017 at 3:19 PM, Denis Magda <dma...@apache.org> wrote: > >> Guys, >> >> Let’s make things simple and attach the jar of the plugin to the wiki page >> that refers to it: >> https://cwiki.apache.org/confluence

Re: abbrevation rules plugin

ul 5, 2017 at 4:35 PM, Denis Magda <dma...@apache.org> wrote: > >> Dmitriy, >> >> I’m not suggesting to add the JAR to the source code or to any binary >> package but rather treat it as a third party plugin developed by someone >> for Ignite’s development si

Re: abbrevation rules plugin

Dmitriy P., Does it sound good to you? If yes, please make sure the plugin is available via a public GitHub repo and refer to it from the doc. — Denis > On Jul 5, 2017, at 4:43 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > On Wed, Jul 5, 2017 at 4:41 PM, D

[CVE-2017-7686] Apache Ignite Information Disclosure

Severity: Important Vendor: The Apache Software Foundation Versions Affected: * Apache Ignite 1.0.0-RC3 to 2.0 Impact: Apache Ignite Might Transfer Sensitive Information to 3rd Party Domain Description: Apache Ignite uses an update notifier component to update the users about new project

Ignite Persistent Store: Ready for merge?

Guys, According to the discussions I see on the @dev list the donated Ignite Persistent Store [1] is stable and ready to be rolled out to our users. Considering that we’ve been already getting to know the donation for a while and had the webinar dedicated to the functionality trying to answer

Re: cannot build ignite 2.1.0

Aleksey, What’s the command you use to trigger the build? — Denis > On Jun 23, 2017, at 9:24 AM, ALEKSEY KUZNETSOV > wrote: > > Cannot build apache ignite 2.1.0 package. Build fails on ignite-hadoop > module : > Could not find artifact

Re: Replace Cron4J with Quartz for ignite-schedule module.

Yakov, No, the mentioned discussion didn’t turn into a JIRA ticket. Alex K., please follow to some thoughts from there and wrap them up in a form of the ticket. — Denis > On Jun 26, 2017, at 2:58 AM, Yakov Zhdanov wrote: > > Guys, I remember we discussed this some time

Re: DataStreamer Transactional and Timestamp Implementation

Faith, Thanks for sharing it with us. In general, we can always wrap this code up in a form of an example to be delivered with every Ignite release. But probably it makes sense to add it to the core streaming functionality. *Igniters*, what’d you think? — Denis > On Jun 27, 2017, at

Re: golang client for Ignite

Hi Aleksandr, That looks really interesting to me. Personally, I would like to see a dedicated Go module in Ignite. Do you support SQL API right now? If it’s so then you might want to switch to Ignite JDBC driver instead that should outperform the REST protocol. Otherwise, if the goal is to

Re: abbrevation rules plugin

Guys, Let’s make things simple and attach the jar of the plugin to the wiki page that refers to it: https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules This should be fine from ASF standpoint. — Denis >

Re: Apache Ignite 2.0 Release

ITE-1794 > [2] https://issues.apache.org/jira/browse/IGNITE-3481 > [3] https://issues.apache.org/jira/browse/IGNITE-3487 > ]4] https://issues.apache.org/jira/browse/IGNITE-5024 > [5] https://issues.apache.org/jira/browse/IGNITE-5072 > [6] https://issues.apache.org/jira/browse/IGNITE-47

Re: Ignite ML, DSL/Scripting (IGNITE-5065)

Folks, Isn’t it to early to dig into DSL implementation? I would take this path only after Ignite supports basic algorithms used for ML and predictive analysis so that people can use it somehow. Then depending on a feedback we might need to start on this task. — Denis > On Apr 25, 2017, at

Re: Null cache names

; in future, as Vladimir suggested. As Igor pointed out, probably for memcached > too. > I'll create another JIRA issue for that. > > Roman > > > > On Wednesday, April 26, 2017 1:16 PM, Denis Magda <dma...@apache.org> wrote: > > > > So it is approach

Re: MemoryMetrics interface inconsistencies

t; overall architecture of metrics gathering in Ignite, how they are exposed > to users or what are use cases. And I still don't have a full picture of > this. > So if there are any experts who know more than me, I think it is a must for > them to share their knowledge with community somewh

Re: IGNITE-4763 - ready for review.

Nikita, I don’t see a single test that validates your fix works and no one will break it in the future. Please address this. — Denis > On Apr 27, 2017, at 1:56 AM, Nikita Amelchev wrote: > > Hello. I done it. > > Please, review. > >

Re: Contributions

elating to Java to begin is there a > way to filter the defects > > Thanks In Advance > Sanjay > > On Wed, Apr 26, 2017 at 10:44 PM, Denis Magda <dma...@apache.org> wrote: > >> Hello Dmitriy, >> >> Welcome to the Ignite community! >> >> I

Re: MemoryMetrics interface inconsistencies

a feedback and improve > documentation if necessary. > > Thanks, > Sergey > > On Wed, Apr 26, 2017 at 8:08 PM, Denis Magda <dma...@apache.org> wrote: > >> Sergey, >> >>> There is no such thing as a "whole page memory", just look at the code.

Re: Apache Ignite 2.0 Release

Guys, How close are we for the voting? What exactly are we waiting for to initiate it (H2 release, TC tests, CREATE INDEX)? — Denis > On Apr 19, 2017, at 4:03 PM, Denis Magda <dma...@apache.org> wrote: > > Roman, > > If we squeeze your contribution into 2.0 please add

Re: Usage of Enums in SQL (Ignite 2.0)

person WHERE job = 'BOSS' or job = 2 > > Previously you had to always use ? parameters and set enum as a Java object > there, but this is impossible for any usual SQL console. Now we will be > able to use constant name or ordinal as a literal. > > Sergi > > 2017-04-

Re: Optimizations on titles and h1

Hi Mauricio, I’ll review your improvements the next week, thanks! — Denis > On Apr 20, 2017, at 8:55 PM, Mauricio Stekl wrote: > > Hi Igniters, > I am attaching a patch with keyword optimizations on several page titles and > H1 across the website. > > I would

Re: Windows XP support

+1 for the discontinuation. Igor, please update C++ readme doc once this feature is implemented. I think it’s still fine to claim that Windows XP, Vista are supported for Ignite Java lib. Pasha, what’s about .NET? Do we still support these ancient Windows versions or the doc has to be altered

Re: Expiration Policy and Page Memory (Ignite 2.0)

s. > > 2017-04-21 2:17 GMT+03:00 Denis Magda <dma...@apache.org>: > >> Alex G., Igniters, >> >> What’s a scope of expiration policy applicability in Ignite 2.0? Does it >> work for all the entries in the page memory or only for those that end up >> in the optional on-heap cache of the page memory? >> >> — >> Denis

Re: Null cache names

Copying Roman S. in the discussion. — Denis > On Apr 21, 2017, at 4:17 AM, Seliverstov Igor wrote: > > Hi Roman, > > As far as I inderstand you're the author of the Redis protocol > implementation. > > Currently I'm working on a task to prohibit null names for caches

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Yakov, Sasha, Are you ready to merge all the changes and close the ticket? As far as I understand, we plan to freeze 2.0 branch the next week. — Denis > On Apr 11, 2017, at 8:59 AM, Denis Magda <dma...@apache.org> wrote: > > Yasha, > > I’v

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

m class loader via > IgniteConfiguration.setClassLoader. If this class loader is ignored during > deserialization of cache objects, then I believe it's a bug. > > -Val > > On Tue, Apr 25, 2017 at 7:36 PM, Denis Magda <dma...@apache.org> wrote: > >> Nick, >> >> This deserializat

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

Nick, This deserialization issue is related to cache objects. You will get the same kind of exception if you try to deserialize a cache entry inside of a compute task which class was preloaded using the peer-class-loading feature. Frankly, this is not treated as an issue on Ignite side. We

Re: MemoryMetrics interface inconsistencies

Totally agree with all Pavel’s and Vovan's suggestions and concerns, especially, with the following: > 2) MemoryMetrics has methods that modify state, like enableMetrics > and rateTimeInterval > (IgniteCache.metrics() returns a read-only serializable snapshot) > > 3) getSize method returns size

Re: Cluster metrics - review for PageMemory

Personally, Total and Committed metrics look confusing to me. Moreover, looks like they interfere with the rest of the metrics this or that way. So, +1 for the changes proposed by Alex G. — Denis > On Apr 25, 2017, at 6:53 AM, Alexey Goncharuk > wrote: > >

Re: Optimizations on titles and h1

Mauricio, thanks! I’ve merged all your changes except the ones from CSS files. Why do we need to change the background? Please elaborate and attach a screenshot that shows what the changes will affect. BTW, these sort of changes have to be reviewed by Prachi Garg. --- css/all.css (revision

[VOTE] Apache Ignite 2.0.0 RC1

Igniters! We have uploaded a 2.0.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc1/ Git tag name is 2.0.0-rc1 This release includes the following changes: Ignite: * Introduced new page memory architecture. * Machine Learning beta: distributed algebra support for

Re: Cloud deployment documentation is missing

Cos, I’ve fixed the broken links. — Denis > On Apr 27, 2017, at 3:53 PM, Konstantin Boudnik wrote: > > Hi guys, > > I am looking at > https://ignite.apache.org/features/deploy.html > > and all of the following links are broken >

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

Nick, Internally, binary marshaller supports as many class loaders as needed. Even more, it can store different versions of the same class loaded by different loaders. It’s a responsibility of an Ignite component to pass a valid class loader to it at deserialization time. The cache component

[CANCEL][VOTE] Apache Ignite 2.0.0 RC1

All the spotted issues have been successfully fixed. Officially closing the vote for Apache Ignite 2.0.0. RC1 candidate. A vote for the next release candidate is to be initiated shortly. — Denis > On Apr 29, 2017, at 2:01 PM, Sergey Kozlov wrote: > > Thanks Alexey. >

Re: Apache Ignite Site Changed its Face

n this email are those of the author, > and do not necessarily represent the views of any company the author > might be affiliated with at the moment of writing. > > > On Thu, Jul 27, 2017 at 2:32 PM, Denis Magda <dma...@apache.org > <javascript:;>> wrote: > >

Pentaho BI tool documentation for Ignite

Igniters, Slava Kopltilin contributed a new documentation that shows how to hook up Pentaho SQL tool with Ignite via the JDBC driver. Thanks, Slava! https://apacheignite-tools.readme.io/docs/pentaho Prachi, could you review the language and improve it whenever is needed? — Denis

Re: Geo-spatial and full-text indexes support in Ignite 2.x

Vladimir, We need to consider that these two types of indexes are not stored off-heap either. It expands the task a bit — the indexes have to be fully integrated with the new durable memory architecture supporting both off-heap and persistence layers. — Denis > On Aug 1, 2017, at 3:26 AM,

[Webinar] Apache Process Overview, Aug 10, 2017 9.00 AM - 10.00 AM PT

Igniters, The practice shows that regardless of Ignite’s project maturity we as a community still miss some valuable points and principles on different occasions violating the ASF processes. Cos Boudnik as one of the oldest ASF and Ignite members agreed to conduct a global webinar reiterating

Re: [IGNITE-5717] improvements of MemoryPolicy default size

;>>> On Wed, Aug 2, 2017 at 7:27 AM, Vladimir Ozerov <voze...@gridgain.com> >>>> wrote: >>>> >>>>> Please see original Sergey's message - when persistence is enabled, >>>> memory >>>>> is not allocated incrementally, ma

Re: [IGNITE-5717] improvements of MemoryPolicy default size

gigs of memory, but it > cannot deal with it. > > > On Wed, Aug 2, 2017 at 4:58 PM, Denis Magda <dma...@apache.org> wrote: > >>> As far as allocating 80% of available RAM - I was against this even for >>> In-memory mode and still think that this is a wrong default. Lo

Re: Pentaho BI tool documentation for Ignite

d say at least > 10-20x from what we have now :-) > > On Tue, Aug 1, 2017 at 12:29 AM, Prachi Garg <pg...@gridgain.com> wrote: > >> Reviewed and made minor edits. >> >> -Prachi >> >> On Mon, Jul 31, 2017 at 1:58 PM, Denis Magda <dma...@apache.or

Re: SQL Getting Started Guide

in.com> > wrote: > > Denis, All: > > Jira account details: > > Username: abchaudhri > Email: akmal.chaudhri AT gridgain.com > Full Name: Akmal Chaudhri > > Thank you. > > On 31 July 2017 at 19:02, Denis Magda <dma...@apache.org> wrote: > >&g

Re: [IGNITE-5717] improvements of MemoryPolicy default size

Why 1 GB? For instance, if I end up having only 1 GB of free memory left and try to start 2 server nodes and an application I will face the laptop suspension again. — Denis > "We had this behavior before" is never an argument. Previous offheap > implementation had a lot

Re: Set default cache synchronization mode to FULL_SYNC

+1 for both suggestions but I’m not sure we can do the change till 3.0. — Denis > On Aug 2, 2017, at 1:27 AM, Vladimir Ozerov wrote: > > +1 for readFromBackup=false as well :-) Another example of default value > with subtle effects. > > On Wed, Aug 2, 2017 at 11:11 AM,

Re: Cluster auto activation design proposal

Sergey, That’s the only concern I have: * 5. User takes out nodes from cluster (e.g. for maintenance purposes): no rebalance happens until user recreates BLT on new cluster topology.* What if a node is crashed (or some other kind of outage) in the middle of the night and the user has to be

Re: Zeppelin, MyBatis and Vert.x update to AI 2.1

this week. >> -- Roman >> >> >>On Tuesday, August 1, 2017 5:23 AM, Denis Magda <dma...@apache.org> wrote: >> >> >> Andrey, Roman, >> As maintainers of the projects in the subject, could you please go ahead and >> update Ignite version to 2.1 >> there?https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations >> —Denis >> >>

Re: Ignite.close(), G.stop(name, true). Change flag cancel to false

I’m totally for the replacement of ‘crashed’ with ‘stopped’. As for the waiting of the checkpointing completion I would NOT do it the default behavior and would rather check the ‘cancel’ flag to make a decision. If the ‘cancel’ is ‘true’ (which is default) then we’re not going to wait for the

Re: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

significant: https://cwiki.apache.org/confluence/display/IGNITE/Release+Process — Denis > On Jul 27, 2017, at 12:27 PM, Denis Magda <dma...@gridgain.com> wrote: > > I’m preparing the docs and site for the release. You’ll not recall the front > page after it’s out. > > Ma

Apache Ignite Site Changed its Face

Igniters, In favor of the 2.1 release we’ve reworked and renewed the front page and some of the existing pages of the site: https://ignite.apache.org The front page reflects the main additions of 2.1, durable memory + persistent store, that opened new opportunities for Ignite. Please welcome

Re: Cache Metrics

how should we aggregate this metrics when user requests metrics for > cluster group. > > On Mon, Jul 24, 2017 at 8:48 PM, Denis Magda <dma...@apache.org> wrote: >> Guys, >> >> What if we calculate it on both sides? The client will keep the total time >> needed

Re: SQL Getting Started Guide

Igor, thanks a lot. Appreciate this! — Denis > On Aug 18, 2017, at 8:56 AM, Igor Sapego <isap...@apache.org> wrote: > > I've checked ODBC snippets and fixed all found issues. > > Best Regards, > Igor > > On Thu, Aug 17, 2017 at 11:16 PM, Denis Magda <dma

Marking and tracking usability issues

Igniters, Here and there we see usability issues bubbling up in the discussion on @dev and @user list, Stackoverflow, etc. Looking at them I would say that the majority is pretty straightforward to fix bringing the overall usability to a better level. Let’s keep using “usability” label for

Re: Ignite2.1: Page eviction is not compatible with persistence when startup

; Agree. If we remove the exception though, we need to make sure to print out > the warning that the eviction policy will be ignored with Ignite native > persistence enabled. > > On Thu, Aug 17, 2017 at 1:35 PM, Denis Magda <dma...@apache.org> wrote: > >> Dmitriy, >>

Re: Marking and tracking usability issues

gt; On Fri, Aug 18, 2017 at 1:42 PM, Denis Magda <dma...@apache.org> wrote: > >> Can not share the filter. That’s the query string to see the tickets: >> >> https://issues.apache.org/jira/browse/IGNITE-6116?jql= >> project%20%3D%20IGNITE%20AND%20status%20in%20(Open

Re: Marking and tracking usability issues

Aug 18, 2017, at 1:26 PM, Denis Magda <dma...@apache.org> wrote: > > Igniters, > > Here and there we see usability issues bubbling up in the discussion on @dev > and @user list, Stackoverflow, etc. Looking at them I would say that the > majority is pretty straightforward

Re: new website tickets

t; Thank you. > > On 11 August 2017 at 20:45, Denis Magda <dma...@apache.org> wrote: > >> Akmal, >> >> Thanks for stepping in! Considering that you’ve been working on the SQL >> getting started, I’ve reassigned the general getting guide task on y

Re: Ignite Add-on/Extension Request: Please add GA Grid (beta) to Ignite website

Hi Turik, Sure, we will do this with pleasure. Prachi, could you add the component to the mentioned page? — Denis > On Aug 16, 2017, at 9:16 PM, techbysample wrote: > > Forum Admin, > > Please add project: > > GA Grid (beta): Distributive in Memory Genetic Algorithm

Re: .sha Release Distribution Policy

:57 AM, Oleg Ostanin <oosta...@gridgain.com> > wrote: > >> Hi, Denis >> >> Yes, we have a ticket that already takes this into account: >> https://issues.apache.org/jira/browse/IGNITE-5817 >> I think we can create both sha-256 and sha-512 checksums. >> >&

Re: SQL usability issues

ith Val. I am OK with using DBeaver as an example, but the name of > the doc should be generic and the doc should be updated stating that > DBeaver is just one example of how Ignite can be used with generic SQL > viewer tools. > > D. > > On Wed, Aug 16, 2017 at 6:01 PM,

How a new index is built in runtime?

Alex P., Vladimir, Having CREATE INDEX command we can define indexes in runtime. However, it’s unclear how a new index is built. Let’s imagine I have a field “name” that was in Person’s model for a while and there are millions of such objects in the cluster. Now I turned the field into the

<    4   5   6   7   8   9   10   11   12   13   >