Re: [Discussion] Kanban board for quick start issues to join the community

I guess the same result could be achieved with simple labels, no? With regards, Cos On 22.01.2021 16:25, Saikat Maitra wrote: Hi, I was looking into our community page to find new open issues that I can contribute to and the easy and moderate tickets, tickets for beginners and SQL tasks

Re: [DISCUSSION] Renaming Ignite's product category

+1 With regards, Cos On 2020-09-21 20:35, Nikita Ivanov wrote: My vote is to just call ignite "IgniteDB". That's it. No other additional explanation is required as no amount of additional verbiage will help. Every DB is different: from MongoDB, to RedisDB, to CockroachDB, to Oracle - they

Re: Apache Ignite Hackathon: Open Source contribution is simple

It is a great idea, Dmitriy. Doing meetups is a great way to bring more contributors and developers on board. Besides, it helps the community's biding. I'd suggest to plan for a few solid hours of hackathon only: 3-5 hours would be a good idea, but it might need to be done on a weekend (depends

MD5 sums in the releases

Please be aware about the changes in the Foundation's release policy [1] * SHOULD NOT supply a MD5 checksum file [1] https://www.apache.org/dev/release-distribution#sigs-and-sums -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer:

Re: [DISCUSS] Ignite Update Checker

e to still send the > latest Ignite version back as a response? > > D. > > On Tue, Oct 31, 2017 at 11:30 AM, Konstantin Boudnik <c...@apache.org> wrote: > >> Looks like we are getting somewhere with this. Please check [1] for >> the latest comment from the Infra team. I

Re: [DISCUSS] Ignite Update Checker

c being able > to execute simple CGI scripts. The INFRA turned this request down. > > [1] https://ignite.apache.org/latest > [2] https://issues.apache.org/jira/browse/INFRA-15182 > > — > Denis > >> On Oct 24, 2017, at 11:57 PM, Konstantin Boudnik <c...@apache.org> w

Re: [DISCUSS] Ignite Update Checker

t;>>> >>>>>>>>>> D. >>>>>>>>>> >>>>>>>>>> On Fri, Aug 25, 2017 at 2:42 PM, Raúl Kripalani < >>>>>> raul@evosent.com >>>>>>> <javasc

Re: [DISCUSS] Ignite Update Checker

u share it some other way (google > drive, etc.)? I’ve never seen any commercial on the site. > > — > Denis > >> On Sep 28, 2017, at 7:23 AM, Konstantin Boudnik <c...@apache.org> wrote: >> >> I don't see an issue with node version either. >> >> Jus

Re: [DISCUSS] Ignite Update Checker

er, i.e. a UUID the node > > > creates > > > >> on > > > >> > > first startup or something. > > > >> > > > > > >> > > This endpoint would need some basic DDoS protection and > > blacklisting > > > >> to > > > >&

Re: Ignite Benchmarking Rules

Yes, we do. A team within AWS org wanted to contribute to the project and they are run a few machines for us. There's no money going back and forth, we are "just" using some of the resources. I guess the best way to get a few servers is to find people @Amazon, who'd be willing to make such

Re: Durable Memory and Ignite Persistence Tuning

Just to spice it up: in my experience, having a few hundred parameters one can tweak (I am making up the number here) is a tough UX call. In JVM, we had a team that worked on heuristics that would auto-tune a bunch of things during the VM startup. Hence, providing the best user experience in most

Re: [DISCUSS] Ignite Update Checker

> > Thoughts? > > D. > > > On Fri, Aug 25, 2017 at 11:29 AM, Konstantin Boudnik <c...@apache.org> wrote: > >> I agree with Raul. >> - providing a ping-back address to a 3rd party might be frown upon by some. >> And might have a consequences like stats coll

Re: [DISCUSS] Ignite Update Checker

I agree with Raul. - providing a ping-back address to a 3rd party might be frown upon by some. And might have a consequences like stats collection about users' infrastructure. - checking an ASF git-repo is easy and won't download any binary data: everything is clear text and could be easily

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

n Aug 8, 2017, at 10:55 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: >> >> I have tried to send a google invite to the dev list. Never done it before, >> so let's see if it works. >> >> D. >> >> On Tue, Aug 8, 2017 at 9:13 AM, Konstant

Re: release procedure

There's also #4: - providing an official environment, comprised of the toolchain, compilers, libs, etc,. The same environment (read "a container") could be used by an individual developer, RM, and/or in CI system for builds, tests, etc. And then you can have #3 pretty much for free! We are doing

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

A reminder to register for the webinar if you're interested. -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author

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

3 > Message: > Release 2.1.0-rc4 > > Deleted : /dev/ignite/2.1.0-rc4 > Added : /release/ignite/2.1.0 (Copy from path: /dev/ignite/2.1.0-rc4, > Revision, 20650) > > On Mon, Jul 31, 2017 at 8:37 PM, Konstantin Boudnik <c...@apache.org> wrote: >> >>

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

eleased >> >> - Site updated >> >> - Git tag added >> >> >> >> On Thu, Jul 27, 2017 at 4:24 PM, Anton Vinogradov <a...@apache.org> >> wrote: >> >> >> >> Igniters, >> >>> >> >>> Apache

Re: Apache Ignite Site Changed its Face

sense to generate extra > noise while that work is in progress. > > That's exactly what happened to the front page. The new memory architecture > and the persistent store was discussed on @dev before many times and the > site was updated accordingly. > > -- > Denis >

Re: Apache Ignite Site Changed its Face

se to generate extra > noise while that work is in progress. > > That's exactly what happened to the front page. The new memory architecture > and the persistent store was discussed on @dev before many times and the > site was updated accordingly. > > -- > Denis &

Re: сhecksum algorythm

That won't guarantee the right choice, unfortunately. Some of the popular projects are still using md5 ;( Why not going with sha-512? This is release checksum'ing - we don't care about computational difficulties nor efficiencies. It is done one every few months. And we care in this case is the

Re: SSL certificate for the CI server

weeks. > > http://reviews.ignite.apache.org - will setup for ssl using too. > > > > Konstantin Boudnik-2 wrote >> I have never heard about this provider, and it is great they are donating >> their resources to the FOSS. I quick glance on their site has reveiled a >> couple o

Re: [VOTE] Apache Ignite 2.1.0 RC4

my signature. > KEYS files (https://dist.apache.org/repos/dist/release/ignite/KEYS) was > updated as well. > > We already got 5 "+1" at RC3, so, is there any reason to wait 72 hours? > This vote will go for 72 hours but may be closed earlier if Konstantin > Boudnik confi

Re: [VOTE] Apache Ignite 2.1.0 RC3

ns bundles all the times. > >> - why every other RC Vote is started by a different person? > > > Summer time, vacations, day offs… > > — > Denis > >> On Jul 22, 2017, at 1:26 PM, Konstantin Boudnik <c...@apache.org> wrote: >> >> Retracting thi

Re: [VOTE] Apache Ignite 2.1.0 RC3

://people.apache.org/keys/committer/ [2] https://www.apache.org/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. > >

Re: [VOTE] Apache Ignite 2.1.0 RC3

Am I missing the location of the signing keys? I cannot verivy the signature of the archive. -1 (binding) until then. Thanks Cos On Thu, Jul 20, 2017 at 03:34PM, Denis Magda wrote: > Igniters, > > Setting off the vote one more time. Hope I’ll be successful this time, > keeping fingers

Re: SSL certificate for the CI server

ey Chetaev, please join the conversation and share your thoughts on > > this. > > > > — > > Denis > > > >> On Jul 19, 2017, at 9:44 AM, Konstantin Boudnik > > > cos@ > > > wrote: > >> > >> Hey guys. > >> >

SSL certificate for the CI server

Hey guys. I've noticed that https://ci.ignite.apache.org/ has two issues: - it has the invalid certificate - the CI server isn't responding on the https port (there's only ngnix) I don't about the rest of the group here, but all my browsers are enforcing HTTPS connections for the obvious

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

Won't the release manager be the "who"? -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 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

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

BTW, keep in mind that /dist ends up being sync'ed across a bunch of Apache mirrors. So, the experiments are better be kept to a less visible environment. Cos -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this

Re: Apache Ignite 2.1 scope

er build procedure, > release signing, and licensing. I do not see the community needing more > time than usual to verify this release. > > D. > > On Fri, Jul 7, 2017 at 8:14 PM, Konstantin Boudnik <c...@apache.org> wrote: > >> Fair enough, I will try to

Re: Apache Ignite 2.1 scope

and what is > > more important - persistent store has been merged only several days ago. We > > need some room for stabilization. I propose the following timeline: > > 16 July - code freeze > > 17-21 July - QA > > 21-24 July - vote and release > > > > On T

Re: Apache Ignite 2.1 scope

Thanks everyone for giving us enough time to take a look into the code and architecture of this new feature. The webinar was certainly quite helpful (thanks Denis!). It seems to be a good time to add the feature into the dot-release, so more users can have a taste of it "officially". I have a

Re: Distributed scheduling

Seems like a simple API for an external cron-like service to invoke an action in Ignite would suffice, no? There are about a million of scheduling services like that already, some have very good integration into orchestrators of all sorts. Perhaps a trivial REST would do instead of durable

Re: any secondary file system for swift

And just to be completely clear: are you referring to OpenStack Swift? Please pardon my ignorance, but I though Swift is a storage "solution" rather than a distributed file system. Are you referring to Ceph by any chance? I guess I am just confused a little bit and would appreciate if you can

Re: Configuration issues with IGFS in Ignite 1.9

of any company the author might be affiliated with at the moment of writing. On Fri, Jun 9, 2017 at 12:19 PM, Konstantin Boudnik <c...@apache.org> wrote: > Vladimir, > > one more issue - it seems that ignite script (bin/ignite.sh) doesn't > respond to 'stop' command anymore

Re: Configuration issues with IGFS in Ignite 1.9

with at the moment of writing. On Fri, Jun 9, 2017 at 11:05 AM, Konstantin Boudnik <c...@apache.org> wrote: > Yey! That did the trick, thank you for your help! It'd be great to > have this fix for sure! > -- > Take care, > Konstantin (Cos) Boudnik > 2CAC 8312 4870 D885 8616

Re: Configuration issues with IGFS in Ignite 1.9

13002.bigtop.apache.org:8020*/*". I'll > create a ticket for this. > > On Thu, Jun 8, 2017 at 9:28 PM, Konstantin Boudnik <c...@apache.org> wrote: > >> Thank you for your help, Vladimir. Unfortunately, I am still seeing >> the same behavior while attempting to bring

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

That'd be great! Thank you! -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 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

Re: Configuration issues with IGFS in Ignite 1.9

> /etc/hadoop/conf/core-site.xml > > > > > > > > > Vladimir. > > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik <c...@apache.org> wrote: > >> Guys, >> >> after upgrading the Bigtop stack from Ignite

Configuration issues with IGFS in Ignite 1.9

Guys, after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing a number of issues introduced by changed script interfaces and similar. However, the one which I still can not fix so far is this. The secondary file system is configured like this:

Re: Fwd: Persistent Distributed Store Metrics

On Mon, Jun 05, 2017 at 07:41PM, Dmitriy Setrakyan wrote: > On Mon, Jun 5, 2017 at 6:46 PM, Konstantin Boudnik <c...@apache.org> wrote: > > > Wow, hold on - as far as I remember there was a VOTE to accept the > > contribution of the code into the project _on a branch_. W

Re: Persistent Distributed Store Metrics

Wow, hold on - as far as I remember there was a VOTE to accept the contribution of the code into the project _on a branch_. We haven't vetted its inclusion into the next release, We are still at the phase of getting familiar with the code. And from what I am seeing in the discussions like this

[jira] [Created] (IGNITE-5413) Ignite shouldn't expose nor send (clear-text) env variables to a 3rd endpoint

Konstantin Boudnik created IGNITE-5413: -- Summary: Ignite shouldn't expose nor send (clear-text) env variables to a 3rd endpoint Key: IGNITE-5413 URL: https://issues.apache.org/jira/browse/IGNITE-5413

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

o move the code to a separate branch in Apache Ignite >> right now, especially given that the paperwork has already been taken care >> of. We can still decide within the Ignite community not to accept it down >> the road, in which case we can toss away the branch. >> >>

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

feature has already been integrated > and perfectly tested with recent AI 2.0 version. This is why, personally, I > don’t see any reason why this can affect the vote or potential release date. > Simply, we just need to move it from the private repo to the ASF one. > > — > Denis &

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

P Clearance page referring to the > template below but failed to commit the changes to ASF repo: > http://incubator.apache.org/ip-clearance/ip-clearance-template.html > > *Roman S.*, *Cos*, could you help me with this by granting karma or > committing the form from under your account? > >

Cloud deployment documentation is missing

Hi guys, I am looking at https://ignite.apache.org/features/deploy.html and all of the following links are broken http://apacheignite.readme.io/docs/aws-config http://apacheignite.readme.io/docs/gce-configuration http://apacheignite.readme.io/docs/generic-cloud-configuration They all

[jira] [Created] (IGNITE-5106) Website still contains links to to "incubator-ignite"

Konstantin Boudnik created IGNITE-5106: -- Summary: Website still contains links to to "incubator-ignite" Key: IGNITE-5106 URL: https://issues.apache.org/jira/browse/IGNITE-5106 Proje

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

On Tue, Apr 18, 2017 at 11:54PM, Dmitriy Setrakyan wrote: > > Would a standard SGA suffice here? > > I believe that ASF guidelines suggest that a discussion should happen > first. Once the community gets enough information, we will move to a PMC > vote. I was under the impression that once the

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

che Ignite 2.0 release. Presently, don’t > have time to wrap it up in a doc form. > > — > Denis > > > On Apr 18, 2017, at 10:44 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > > wrote: > > > > Cos, good questions! My answers are inline... > >

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

Great news indeed! Thanks for sharing! Before we jump on the voting and all that, can we have a chance to learn more about this new feature and its integration points with the rest of the platform? A few questions come to mind immediately: 1. This is an "optional disk layer", so it could be

Re: Move documentation from readme.io to GitHub pages

I hate to be that guy, but mentors warned this very project no to do this in the first place. At least once [1] on the dev@, and a few times off-line [1] https://is.gd/ZRPOrH Cos -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions

Re: Write access to Apache Ignite repository

+1 PMC members don't have _any_ special privileges when it gets to the code access Cos -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of

Re: Getting Access to Ignite's blog on ASF

gt; >> On Mar 4, 2017, at 7:19 PM, Konstantin Boudnik <c...@apache.org> wrote: >> >> Hi Denis. >> >> I reckon you'd need to register on the roller (that blog site) and >> share your account name with me, so I can add this to the ignite's >> blog. >&

Re: Ignite ASF Confluence edit rights

Yup, this is a contribution all right. Anyone with admin creds for the Ignite space should be able to go and add permissions to a person with Wiki account. Cos On Mon, Jan 23, 2017 at 11:43AM, Denis Magda wrote: > Dmitriy, Cos, > > Does contributors (not committers) have write permissions on

Re: Ignite ASF blog

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 >

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

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

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

I don't think INFRA has any control of how something is pushed into Maven central. Interestingly enough, looking thought the artifacts in Maven, I see a whole bunch of the component that are pulled from the latest releases yet are presented in the Maven. Say geospacial is only published up to

Re: [VOTE] Apche Ignite PMC Chair Election

yan <dsetrak...@apache.org> > > wrote: > > > > According to the discussion on the dev list [1], the following candidates > > were proposed for the Apache Ignite PMC Chair position: > > > > Vladimir Ozerov > > Konstantin Boudnik > > Valentin K

Re: [VOTE] Apche Ignite PMC Chair Election

On Sat, Dec 10, 2016 at 12:24PM, Dmitriy Setrakyan wrote: > According to the discussion on the dev list [1], the following candidates > were proposed for the Apache Ignite PMC Chair position: > > Vladimir Ozerov > Konstantin Boudnik > Valentin Kulichenko > Denis

Re: Blogging about new .NET features

Gents, I would encourage you to use https://blogs.apache.org/ as this place gets contant attention of the ASF media team and all the blogs here got quite a bit of the spot light. In fact, I would encourage this group to start using it. I'd be happy to help to set this up. Cos On Wed, Nov

Re: ignite-spark module in Hadoop Accelerator

; > > I’m thinking of if there is a need to keep releasing Hadoop Accelerator as > > 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? > > > > —

Re: [VOTE] Use Upsource for Code Review

at 12:21 PM, Konstantin Boudnik <c...@apache.org> wrote: > > > What are we voting for this? > > > > Fortunately, Apache isn't about democracy. [1] > > > > [1] https://www.apache.org/foundation/voting.html > > > > Cos > > > > O

Re: [DISCUSS] PMC Chair rotation time

Konstantin Boudnik Valentin Kulichenko Denis Magda Branko Čibej Considering the number of the candidates I propose to use First-past-the-post voting, with a single-round/single winner rules, where the candidate collecting the most votes (not the majority) wins. [1] Dmitriy, would you do

Re: [VOTE] Use Upsource for Code Review

What are we voting for this? Fortunately, Apache isn't about democracy. [1] [1] https://www.apache.org/foundation/voting.html Cos On Wed, Nov 16, 2016 at 01:08PM, Pavel Tupitsyn wrote: > Following the discussion on Upsource [1], > I would like to call a vote on accepting it as our official

Re: ignite-spark module in Hadoop Accelerator

What Denis said: spark has been added to the Hadoop accelerator as a way to boost the performance of more than just MR compute of the Hadoop stack, IIRC. For what it worth, Spark is considered a part of Hadoop at large. On the separate note, in the Bigtop, we start looking into changing the way

Re: new committer: Igor Rudyak

Congrats, Igor - well deserved! Welcome! On Mon, Nov 14, 2016 at 11:35AM, Igor Rudyak wrote: > Thanks. Will try to do my best for the project. > > Igor > > > On Mon, Nov 14, 2016 at 11:03 AM, Denis Magda wrote: > > > The Project Management Committee (PMC) for Apache Ignite

Re: Downloads on the web site

Interesting read, Denis, although there's more shades in it than SDtimes can be aware about. Dima, I was referring to this blog-post https://www.datastax.com/2016/10/take-a-bow-planet-cassandra but has posted a link to this very thread instead. THanks for catching that! Cos On Fri, Nov 04,

Re: [DISCUSS] PMC Chair rotation time

that the most proved candidate is Vladimir Putin :) But I want to > > nominate some more trusted guys to make sure that our election is true and > > representative: > > > > 1. I want to nominate Vladimir Ozerov, who plays a big role in our > > engineering efforts to m

[DISCUSS] PMC Chair rotation time

As per the [VOTE] we held back in 2015, I'd like to start a discussion about the PMC Chair for the next year. The original [VOTE] can be found in [1] Please make your nominations. Once we have the list of the candidates we'll start the [VOTE] to determine the "lucky" winner. [1]

Re: Release notes preparations...

ed to 1.8 yesterday when I released > 1.7 version in JIRA. > > For what it's worth, I've added a step to vote verification: > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > Pavel > > On Tue, Aug 9, 2016 at 9:37 PM, Konstantin Boudnik <

Re: Ignite 1.7 RELEASE_NOTES

o release notes. Well, a lot of other projects do. And some others don't ;) I guess it depends on what you want in the RN. Cos > On Tue, Aug 2, 2016 at 10:31 PM, Konstantin Boudnik <c...@apache.org> wrote: > > > Tracking the "Fixed in release" on the JIRA tickets w

Re: Ignite 1.7 RELEASE_NOTES

Tracking the "Fixed in release" on the JIRA tickets would take care about any gaps pretty much automatically. In general it's a good idea for an RM to run a spring-cleaning on the JIRA tickets to scope up the release. Then once all tickets are fixed, you can simply _generate_ the release notes

Re: kick off a discussion

On Wed, Jul 13, 2016 at 05:30AM, Dmitriy Setrakyan wrote: > Hi Alex, > > I believe most of your comments have to do with disk-based functionality, > especially in regard to backups, snapshots, etc. However, Ignite is > currently an in-memory system, at least for the nearest future. Let me know >

Re: Apache Ignite - New Release

Yup, looks like having a minor bump is totally warranted. On Mon, Jul 11, 2016 at 10:11PM, Sergi Vladykin wrote: > Yakov, > > Good idea. > > Alexey, > > Why not just bump it to 1.7 as we do usually? > > Sergi > > > > On Mon, Jul 11, 2016 at 9:21 PM, Alexey Goncharuk < >

Re: kick off a discussion

On Mon, Jul 11, 2016 at 08:15AM, Dmitriy Setrakyan wrote: > My answers are inline… > > On Sat, Jul 9, 2016 at 3:04 AM, Dmitriy Setrakyan > wrote: > > > Thanks Sasha! > > > > Resending to the dev list. > > > > D. > > > > On Fri, Jul 8, 2016 at 2:02 PM, Alexandre Boudnik

Re: Migration from json-lib 2.4 to Jackson

On Thu, Jun 09, 2016 at 04:37PM, Alexey Kuznetsov wrote: > And one more question: ignite-zookeeper module has 2 dependencies to > Jackson 1.9.13. > It is possible to replace them to Jackson 2.x dependencies? That's the huge problem the whole Hadoop ecosystem faces: every project is using

Dynamic (-like) byte-code modifications [Was: Documentation for AOP-based Grid Enabling]

Thanks for putting the docs together Prachi! I am also quite a bit surprised that Ignite has the support for AOP. As a side topic, and the one for an overall amusement: - do people think it might be a good time to revisit the use of "last century" programming techniques, which are build

Re: Ignite Release Schedules - a suggestion

On Tue, May 17, 2016 at 01:09AM, endianignite wrote: > With regard to branch structure, I took some time to think and have a > suggestion. Feel free to pick holes in it. > > Major feature releases would continue to have major version numbers: e.g., > 1.7, 1.8, 2.x and so on. Bug-fix releases

Re: Halfway to Ignite 1.6

You can still talk about the release even if it is in the final stages. What would be unfortunate is to miss some of the good features (like IGNITE-1371) just because of an arbitrary date of an even of some kind, which has no relevance to the project itself. For what it worth, rushing releases

Re: 1.5.0.final is breaking packaging: osgi dependency is non-existent

t. > > > > In case someone familiar with OSGI please have a look. > > > > > > > > On Wed, May 4, 2016 at 11:15 AM, Anton Vinogradov > > > > <avinogra...@gridgain.com> > > > > wrote: > > > > > > > > > Roman, Rau

Re: Ignite Release Schedules - a suggestion

I don't think the extrapolation works in this particular case, although it looks scary ;) However, I agree, shorter bug fix & smaller feature releases might make a lot of sense, considering how actively the userbase and community grow. However, major features take longer time to mature and be

Re: HDFS CacheStore

Cristian, Great idea! a couple of comments: - HDFS supports truncate since at least v. 2.7.0 (see HDFS-3107) - integration with HBase would increase the operational complexity, which is already high in HBase, to new levels. Besides, using HBase as the compaction mechanism shouldn't be

Re: 1.5.0.final is breaking packaging: osgi dependency is non-existent

, Anton Vinogradov <avinogra...@gridgain.com> > > wrote: > > > > > Roman, Raul, > > > > > > As far as I remember you're familiar with OSGI. Could you please have a > > > look at this? > > > > > > On Wed, May 4, 2016 at 6:09 AM,

1.5.0.final is breaking packaging: osgi dependency is non-existent

Hey guys For your information: adding osgi into the product is breaking the dependency matrix of the bigtop packages. For more info see https://issues.apache.org/jira/browse/BIGTOP-2421 -- Take care, Cos 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Cos' pubkey:

Re: a question about CLA and contributions to the project

Alexander, Having ICLA for contributors is 'nice to have' but isn't mandatory. Once when/if a person is invited to become a committer, the ICLA is the must. It is called ICLA for a reason: I == Individual If your employer is going to do a donation of existing code, it will have to go through the

Re: Switching back to review-then-commit process

It saddens me to see this coming to it ;( On Thu, Mar 03, 2016 at 02:54PM, Denis Magda wrote: > Igniters, > > I would propose to switch back to review-then-commit process. This > process has to be followed by both contributors and committers. > > There is a reason for this I have in mind.

Re: Apache Arrow and Apache Ignite

On Fri, Feb 26, 2016 at 09:22PM, Dood@ODDO wrote: > On 2/25/2016 11:06 AM, Konstantin Boudnik wrote: > >On Wed, Feb 24, 2016 at 02:02PM, Dood@ODDO wrote: > >>On 2/24/2016 1:31 PM, Konstantin Boudnik wrote: > >>>On Sat, Feb 20, 2016 at 02:13PM, Dood@ODDO wrote: &

Re: Apache Arrow and Apache Ignite

On Wed, Feb 24, 2016 at 02:02PM, Dood@ODDO wrote: > On 2/24/2016 1:31 PM, Konstantin Boudnik wrote: > >On Sat, Feb 20, 2016 at 02:13PM, Dood@ODDO wrote: > >>That's the million dollar question - I think we should approach the > >>Arrow people and get a conversation

Re: Apache Arrow and Apache Ignite

On Sat, Feb 20, 2016 at 02:13PM, Dood@ODDO wrote: > That's the million dollar question - I think we should approach the > Arrow people and get a conversation going. We want to be ahead of > the curve, not behind it - Arrow seems to be making quite a stir, > not to mention that it was fast-tracked

Re: Re: Ignite Readme.IO UX issue

And once again I would like to encourage this community to consider making the documentation as a part of the source code, which would solve many issues like that. Cos On Fri, Jan 29, 2016 at 10:58AM, 李玉珏 wrote: > Hi > > The following address: >

Re: Ignite Readme.IO UX issue

On Mon, Jan 25, 2016 at 09:28AM, Dmitriy Setrakyan wrote: > Hadoop/IGFS documentation is being refactored right now. Could be a side > effect of what you were observing. > > Btw, everyone with login to readme can file a support issue. However, I > would not do it yet, while Prachi is still

Re: Marking fixed JIRAs against releases

perhaps, someone with JIRA admin permissions need to rename the version number then to avoid the confusion? Cos On Fri, Jan 22, 2016 at 06:57PM, Dmitriy Setrakyan wrote: > I would say 1.5.0.final (the beta did not include all the fixes). > > On Fri, Jan 22, 2016 at 5:26 PM, Konstanti

[jira] [Created] (IGNITE-2437) Zeppelin interperet doesn't import external dependencies

Konstantin Boudnik created IGNITE-2437: -- Summary: Zeppelin interperet doesn't import external dependencies Key: IGNITE-2437 URL: https://issues.apache.org/jira/browse/IGNITE-2437 Project: Ignite

Re: Marking fixed JIRAs against releases

Another issue: JIRA has release 1.5, however to my knowledge the project had at least 1.5.0-b1 1.5.0.final Which one JIRA's version is related to? Cos On Thu, Jan 21, 2016 at 05:33AM, Konstantin Boudnik wrote: > There might be a way to enforce it on the JIRA side, I just have no i

Re: Marking fixed JIRAs against releases

ay to enforce it?) > > > > D. > > > > On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <c...@apache.org> > > wrote: > > > > > Guys, > > > > > > as a fall-out from another conversation I've ran the following search on > > >

Re: What is jdbc:ignite:cfg ??

will be thrown > > anyway. > > > > > > > > > > Thoughts? > > > > > > > > > > -Val > > > > > > > > > > On Mon, Jan 18, 2016 at 6:35 AM, Andrey Gura <ag...@gridgain.com> >

Marking fixed JIRAs against releases

Guys, as a fall-out from another conversation I've ran the following search on JIRA project = ignite and status in (Fixed, Closed) and fixVersion is null and we have 150 (yes, some of them are dups and won't fixes) closed/fixed tickets without explicit fixVersion on them. How do we keep

Re: Json support in Ignite

One other thing to keep in mind, that JSON data is often not-flattened ie coming with hierarchical structures. In which case, querying it from Ignite would be a non-trivial if at all possible. Cos On Thu, Jan 14, 2016 at 09:09AM, Dmitriy Setrakyan wrote: > I would consider a case for generating

  1   2   3   >