+1
--
Nikita Ivanov
On Fri, Sep 17, 2021 at 6:22 PM Valentin Kulichenko
wrote:
>
> Igniters,
>
> I think it's clear to all of us that Ignite 2.x and 3.x will coexist for a
> while. They are developed in separate Git repos, but we still accumulate
> the tickets for both version
+1
--
Nikita Ivanov
On Fri, Jun 25, 2021 at 3:31 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Dear Community,
>
> In the last several months, the development of Ignite 3 has been moving
> forward significantly. On top of what we already had in the firs
s.
3. And... common sense! None of the rules in (1) are axiomatic but rather a
guidance that requires common sense.
Code review culture takes time and organizational discipline to become
effective & productive. Rules alone or some fiat enforcement is unlikely to
work.
--
Nikita Ivanov
On Tue, Jun 22, 2
-level engineering discipline.
On a personal node - nothing screams "immaturity" louder that a code
that uses inconsistent naming, commenting, code style & organization,
etc.
--
Nikita Ivanov
On Wed, Jun 16, 2021 at 5:56 AM Andrey Gura wrote:
>
> Hi,
>
> I understand that
needs to debate fundamental
engineering issues like that...
--
Nikita Ivanov
On Wed, Jun 16, 2021 at 4:47 AM Andrey Gura wrote:
>
> Hi,
>
> I think that scope should be limited by public API for beginning.
> Also I don't sure that we should support specific tags like @apiNo
-1
- 'mvn clean package' fails on Win10 (at least)
- binary artifacts in release location (ignite.exe)
--
Nikita Ivanov
On Sun, Jan 3, 2021 at 4:00 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Dear Community,
>
> The release candidate is uploade
- but it doesn't make it a good idea...
The main goal of our CLI tool should be simplicity and usability.
My 2 cents,
--
Nikita Ivanov
On Mon, Dec 21, 2020 at 8:35 AM Kirill Gusakov wrote:
> Hey.
>
> 1. Sure, will remove demo suffixes.
>
> 2. I thought about it. Not sure why “node-s
+1 on having a separate repo. Make the work cleaner and more effective.
--
Nikita Ivanov
On Mon, Nov 2, 2020 at 11:09 PM Nikolay Izhikov wrote:
> Igniters, should we have a call for this topic?
>
> > 2 нояб. 2020 г., в 18:53, Pavel Tupitsyn
> написал(а):
> >
>
Let's try to simplify the project's messaging - not introduce new
sub-component naming or synthetic shelving to it :-)
--
Nikita Ivanov
On Thu, Sep 24, 2020 at 12:01 PM Denis Magda wrote:
> If "Apache Ignite" remains then another option is to keep defining Ignite
> as an in-
).
Or... we can go and rename the project to "Apache IgniteDB" which is a
longer process but the community has plenty of time to do it in "ignite
3.0" timeframe. I'd love to hear other's opinions on that.
Thanks,
--
Nikita Ivanov
On Thu, Sep 24, 2020 at 11:44 AM Denis Magda
around trying
to explain in one line what they do and how they are different.
"IgniteDB" is clear, concise and gives us the broadest initial acceptance
from the new user perspective.
Thanks,
--
Nikita Ivanov
On Sat, Sep 19, 2020 at 1:10 PM Saikat Maitra
wrote:
> Hi,
>
> My
...
Thanks!
1. https://issues.apache.org/jira/browse/INFRA-19929
--
Nikita Ivanov
Denis - looks very nice! I do indeed think we need to work on better
content (home page specifically).
Thanks!
--
Nikita Ivanov
On Thu, Mar 5, 2020 at 3:18 PM Denis Magda wrote:
> Folks,
>
> As many of you know, these days I mostly contribute by optimizing our
> website, prepari
rogramming with Scala and Ignite. You can ask me any questions afterwards
(I happen to know a thing or two about this project...)
Come join me and other Igniters!
--
Nikita Ivanov
Ignite PMC/GridGain founder.
+1 Alexey Goncharuk
--
Nikita Ivanov
> On Oct 21, 2019, at 10:21 PM, Denis Magda wrote:
>
> Igniters,
>
> It’s been almost 3 years since my election as the PMC Chair and I’d like
> the community to give other PMC members an opportunity to serve in this
> role. I
Yes, have a minimum set at Java 8 (ML contributors would greatly appreciate
that...).
--
Nikita Ivanov
On Tue, Sep 26, 2017 at 6:16 PM, Denis Magda <dma...@gridgain.com> wrote:
> You meant Java 7 drop I guess. That's a good question. Hope this happens
> soon.
>
> De
What about Java 8 to begin with?
--
Nikita Ivanov
On Tue, Sep 26, 2017 at 3:16 PM, Denis Magda <dma...@apache.org> wrote:
> Eventually now it’s time to put all the doubts aside on when Ignite should
> support JDK 9. The JDK is production ready and was released not lon
+1 on idea (long overdue) and +1 on using epics in JIRA for grouping IEPs.
--
Nikita Ivanov
On Wed, Sep 20, 2017 at 10:28 PM, Denis Magda <dma...@apache.org> wrote:
> Vladimir,
>
> I support your initiative because it sorts things out and brings more
> transparency t
Excellent work on this... This should be expanded and be prominently placed
in our docs/tutorials/javadocs/etc.
--
Nikita Ivanov
On Wed, Sep 13, 2017 at 12:29 PM, Ivan Rakov <ivan.glu...@gmail.com> wrote:
> Folks,
>
> We had some experience of benchmarking Ignite with persistent
My points was in support of auto-tune for Ignite's internals. As far as
environment, sure, we need to have a doc.
--
Nikita Ivanov
On Fri, Sep 1, 2017 at 1:23 PM, Denis Magda <dma...@apache.org> wrote:
> It doesn’t matter how many configuration parameters your platform,
> database
look for ways not to use it...
My 2 cents,
--
Nikita Ivanov
On Fri, Sep 1, 2017 at 12:02 PM, Konstantin Boudnik <c...@apache.org> wrote:
> 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.
General question: what is the process to ensure that code examples are
actually valid (compile and run properly)?
--
Nikita Ivanov
On Wed, Aug 23, 2017 at 6:28 PM, Denis Magda <dma...@apache.org> wrote:
> The task is completed from my side. Below you’ll find the brand new page
I looked briefly and I couldn't find any explanation on "template" at all -
the only unique caveat apart from standard SQL. Is this on purpose?
--
Nikita Ivanov
On Mon, Aug 21, 2017 at 9:36 AM, Prachi Garg <pg...@gridgain.com> wrote:
> Igor, Pavel
>
> On the website[1
Igniters,
Just a quick update. I haven't gotten response from ASF Legal on this
thread and I frankly don't know how to proceed here. What's the process to
arrive to a decision point here?
Thanks!
--
Nikita Ivanov
On Mon, Jul 10, 2017 at 3:11 PM, Konstantin Boudnik <c...@apache.org>
about. We should only be
interested in aggregated stats (community size, geo information, language
information, components usage).
Thoughts?
--
Nikita Ivanov
Founder & CTO
GridGain Systems
On Fri, Jul 7, 2017 at 8:17 PM, Konstantin Boudnik <c...@apache.org> wrote:
> Actually, that s
The idea so far is to have a single system property in configuration that
turns this off completely. I envision that this will be prominently
featured on Ignite website so that everyone who would like to disable it -
can do it in seconds.
Thoughts?
--
Nikita Ivanov
Founder & CTO
GridGain Sys
Roman,
Thanks for the feedback. What are those questions specifically? Are IP
addresses and OS is what causing it?
Thanks!
--
Nikita Ivanov
Founder & CTO
GridGain Systems
On Wed, Jul 5, 2017 at 6:15 PM, Roman Shtykh <rsht...@yahoo.com.invalid>
wrote:
> NIkita,
>
> While thi
was used)
Please let's discuss this idea. Everyone's comments and suggestions are
*extremely* welcome.
Thanks,
Nikita Ivanov.
Sounds like a good plan to tackle for 1.0 GA release sometime in the future.
--
Nikita Ivanov
On Fri, Apr 21, 2017 at 9:43 AM, Yury Babak <y.ch...@gmail.com> wrote:
> Guys,
>
> Since the first version of Ignite ML module was merged into ignite 2.0 we
> want to disc
+1!
--
Nikita Ivanov
On Thu, Apr 20, 2017 at 1:35 PM, Tom Diederich <tom.dieder...@gridgain.com>
wrote:
> I’d also like to propose an enhancement to the community that I believe
> would be helpful to new and experienced Igniters alike: "Apache Ignite
> University.”
&
Combining this with upcoming new SQL features should give Google Spanner a
run for its money...
--
Nikita Ivanov
On Tue, Apr 18, 2017 at 3:39 AM, christos <chris...@gridgain.com> wrote:
> This is fantastic news guys!! Finally a real solution that can cater for
> BIG
>
As the original developer/author of Scalar (and I already voiced this
opinion before) - I think we should deprecate Scalar. Ignite APIs can be
used from Scala as-is with minimal, if any, pimping. The custom DSL
introduced by Scalar proved to be not a popular option either.
--
Nikita Ivanov
on and prototype is to look close at Apache Mahout (
http://mahout.apache.org/). After a deep look at Mahout codebase I don't
believe the outright code-level integration is feasible at this points -
but we can certainly borrow as many ideas from it as possible.
Thanks!
--
Nikita Ivanov
Nikita Ivanov created IGNITE-4572:
-
Summary: Develop distributed algebra support for dense and sparse
data sets.
Key: IGNITE-4572
URL: https://issues.apache.org/jira/browse/IGNITE-4572
Project
...
--
Nikita Ivanov
On Tue, Jul 26, 2016 at 9:53 PM, Andrey Kornev <andrewkor...@hotmail.com>
wrote:
> Dictionary compression requires some knowledge about data being
> compressed. For example, for numeric types a range of values must be known
> so that the dictionary c
to the user.
--
Nikita Ivanov
On Mon, Jul 25, 2016 at 1:40 PM, Sergey Kozlov <skoz...@gridgain.com> wrote:
> Hi
>
> For approach 1: Put a large object into a partiton cache will force to
> update the dictionary placed on replication cache. It seeis it may be
> time-expense o
Igniters,
Aeron is gaining some significant traction (Fintech, etc.) and looks like a
very interesting transport for our Communication SPI implementation:
https://github.com/real-logic/Aeron
Does anyone have cycles and interest to tackle this?
--
Nikita Ivanov
Nikita Ivanov created IGNITE-3276:
-
Summary: Develop Cloudera Service Descriptor for PnP integration
with Cloudera Manager.
Key: IGNITE-3276
URL: https://issues.apache.org/jira/browse/IGNITE-3276
Pretty cool indeed. Does it basically use GitHub APIs underneath for the
stats?
--
Nikita Ivanov
On Mon, Dec 28, 2015 at 8:30 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:
> This is great! I especially like the contributors-per-month graph spiking
> up :)
>
> On Mon,
+1
--
Nikita Ivanov
On Tue, Oct 13, 2015 at 3:30 PM, Konstantin Boudnik <c...@apache.org> wrote:
> Hi!
>
> As discussed in the "[DISCUSS] PMC Chair rotation" thread last month, I
> propose
> that we adopt a rule allowing for a Apache Ignite Chair rotation on a
+1 on Sergey's idea too.
--
Nikita Ivanov
On Mon, Oct 12, 2015 at 10:10 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:
> I think I like Sergey's idea. Any way to make it backward compatible?
>
> On Mon, Oct 12, 2015 at 9:53 AM, Sergi Vladykin <sergi.vlady...@
I'm not sure how a file system concept corresponds to shared RDD or custom
MapReduce implementation... May we should have another "assembly" just for
in-memory file system?
--
Nikita Ivanov
On Tue, Sep 29, 2015 at 7:04 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:
>
Well, my thinking at this point is that none of these three modules would
interest in real life. So, I was thinking of giving users a clear direction
on getting a) fabric only, b) hadoop accelerator, and c) spark integration.
--
Nikita Ivanov
On Tue, Sep 29, 2015 at 5:29 PM, Konstantin Boudnik
Cos - why mixing the two? I think if we are embark on this route - why not
create two different assemblies, one for Hadoop bits, and another for Spark
integration? Two would rarely intersect IMHO.
--
Nikita Ivanov
On Mon, Sep 28, 2015 at 10:40 PM, Konstantin Boudnik <c...@apache.org>
Nikita Ivanov created IGNITE-1483:
-
Summary: Web console sign up via Google (i.e. via Google Identity
Platform).
Key: IGNITE-1483
URL: https://issues.apache.org/jira/browse/IGNITE-1483
Project
Nikita Ivanov created IGNITE-1484:
-
Summary: Allow to store configuration in Google Datastore.
Key: IGNITE-1484
URL: https://issues.apache.org/jira/browse/IGNITE-1484
Project: Ignite
Issue
46 matches
Mail list logo
