On Wed, May 30, 2018 at 2:09 PM, Peter Ivanov wrote:
> Dmitriy,
>
> What kind of Ubuntu installation do you have (and what version)?
> Is it WSL under Windows 10 or containerized (docker)?
>
>
Windows Ubuntu App -
https://docs.microsoft.com/en-us/windows/wsl/install-win10
D.
will be more compact and precise.
>
> There is no such option for YUM (as far as I am aware of).
>
>
>
> > On 30 May 2018, at 17:16, Dmitriy Setrakyan
> wrote:
> >
> > Petr,
> >
> > Can you tell me what this flag does: "--no-install-recommend
Dmitriy,
I think the behavior for offline and online iterator is fundamentally
different. I do not think it is OK to skip records during normal operation.
In my view, we should report an error and stop. However, when offline, it
is OK to report an error and continue in my view.
D.
On Wed, May 30
n-options <https://apacheignite.readme.
> io/docs/getting-started#alternative-installation-options>
> Snippet "DEB repository setup"
>
>
>
>
> > On 30 May 2018, at 16:59, Dmitriy Setrakyan
> wrote:
> >
> > Petr, can you provide a link to the Debi
On Wed, May 30, 2018 at 5:40 AM, Igor Sapego wrote:
> By the way, ODBC does not currently support streaming.
>
Igor, and when do you plan to add this support?
; https://ignite.apache.org/download.cgi#rpm-package>
> >> [2] https://apacheignite.readme.io/docs/getting-started#
> section-rpm-deb-packages-installation <https://apacheignite.readme.
> io/docs/getting-started#section-rpm-deb-packages-installation>
> >>
> &
Alex,
STREAMING command is definitely a DML command. And by the way, the DML page
is not a mess. It documents all DML commands we have. I think you were
looking at something else.
What is the major difficulty of implementing STREAMING command on Ignite
SQL API? It should be even simpler than JDBC
;> >
>> >
>> >
>> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
>> >
>> > > NuGet (.NET) packages pushed:
>> > > https://www.nuget.org/packages?q=Apache.Ignite
>> > >
>> > > On Tue, May 29, 2018 at 8:59 PM, Andrey
; if (tx.timeout() < 200)
> tx.rollback();
> ...
>
> So, tx will be rollbacked on creation and any commit attempt will cause
> TransactionRollbackException
>
> Full code listing available at
> https://github.com/apache/ignite/pull/4036/files
>
> Dmitriy, Yakov,
&
Dmitriy,
Thanks for initiating the discussion!
I am not sure I understand the issue fully, but in my view we should not
allow iteration through WAL if we cannot deserialize a portion of it. We
must require that ignite-index is in the classpath, so I would just fail
right away with exception.
D.
On Tue, May 29, 2018 at 9:08 AM, Andrey Gura wrote:
> RPM and DEB packages are published to bintray [1] [2]
>
> [1] https://bintray.com/apache/ignite-rpm
> [2] https://bintray.com/apache/ignite-deb
Thanks, Andrey! Can we update the download page on the website?
D.
As suggested before, please do not put blank ticket numbers into subjects
because no one understands ticket numbers. Please add titles or some other
context to the subject. This will improve the level of engagement from the
community.
I have changed the subject of this thread, let's continue the d
ed to the npmjs repository,
> > right? So, a JS developer can download the client from there without
> > touching the whole Ignite binary release.
> >
> > However, those who download the whole Ignite binary distribution will
> find
> > node.js there (as well as .NET,
On Thu, May 24, 2018 at 12:36 PM, Pavel Petroshenko
wrote:
> Fair enough. Consistency with the other clients is a good argument.
>
>
Pavel, I would discuss it a bit more. Does it really make sense for a
node.js user to download the whole Ignite distribution just to get a
node.js client?
On Thu, May 24, 2018 at 11:42 AM, Igor Sapego wrote:
> Well, all other clients have the same version as Ignite.
> Are there any reasons to make a Node.js client some
> kind of a special case?
>
>
I may have spoken too soon. Do we plan to include the node.js client into
Ignite build? If yes, then
I continuously ask not to provide naked ticket numbers in the subject.
Please also add titles or descriptions. I doubt anyone in the community can
tell what this is about just by looking at the number.
D.
On Thu, May 24, 2018 at 4:09 AM, Dmitry Pavlov
wrote:
> Hi Dmitriy,
>
> According to upsou
On Thu, May 24, 2018 at 10:03 AM, Pavel Petroshenko
wrote:
> Igor,
>
> Are you proposing to update the Thin Client versions on every Ignite
> release regardless of the changes made to them?
>
> I tend to think that an independent versioning scheme for the Thin Clients
> might be more flexible/mea
cess to Ignite
> cluster and there is no other way to setup tx cretion rules.
>
> Yakov,
>
> Could you please share your thoughts on that?
>
>
> чт, 24 мая 2018 г. в 8:58, Dmitriy Setrakyan :
>
> > On Wed, May 23, 2018 at 4:08 AM, Anton Vinogradov wrote:
> &g
On Wed, May 23, 2018 at 4:08 AM, Anton Vinogradov wrote:
> Dmitriy, Yakov
>
> Are there any objections to updated design taking into account the comments
> I provided?
>
Anton, I do not like an additional validator. I think you can accomplish
the same with a transaction event. You just need to d
; IgniteConfiguration setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
>
> Any objections?
>
>
>
> On Fri, May 4, 2018 at 10:01 PM, Dmitriy Setrakyan
> wrote:
>
> > I do not like the name "current" on the methods. I think we should just
> > remove
Igniters,
It will be great if someone in the community would pick this up. The amount
of changes are minimal and many of them only have to do with clarifying the
documentation. However, removing JSR 107 license confusion in 1.1 would be
great for Ignite.
D.
On Tue, May 22, 2018 at 3:04 PM, Denis
Anton,
The change looks very questionable. We cannot be adding configuration
validators for every piece of Ignite API. What is it you are trying to
achieve?
D.
On Mon, May 21, 2018 at 7:22 AM, Anton Vinogradov wrote:
> Yakov, thank's for deep check.
>
> >> I think that we should think about so
Great docs! Any chance we could add some pictures to illustrate the concept
better.
On Fri, May 18, 2018 at 2:15 AM, Denis Magda wrote:
> Igniters,
>
> With the help of Stanislav Lukyanov and Ivan Rakov, we could make our
> baseline topology documentation much better and vivid. Check up the new
bloody
> tears.
> > > > > > > > >
> > > > > > > > > I think we should really consider YAML as our additional
> > > approach
> > > > > to
> > > > > > > > > configure Ignite with full replacement instead of XML in
> > > future.
;
> > On 15 May 2018, at 01:55, Dmitriy Setrakyan
> wrote:
> >
> > Thanks Petr,
> >
> > How about Java 10? Do we support it for SqlLine as well?
> >
> > D.
> >
> > On Mon, May 14, 2018 at 1:53 PM, Petr Ivanov
> wrote:
> >
>
I still do not understand *why* do we need to add additional formats for
the configuration. Can you please show me some users on the user@ list or
stack overflow who asked for it? I just want to make sure that if we are
creating work for ourselves, then someone actually needs it.
D.
On Tue, May 1
kes sense.
>
> Thanks,
> p.
>
> [1] http://php.net/supported-versions.php
> [2] https://legacy.python.org/dev/peps/pep-0373/
> [3] https://www.jetbrains.com/research/python-developers-survey-2017/
>
>
> On Sat, May 12, 2018 at 6:21 AM, Dmitriy Setrakyan
> wrote:
>
:35, Petr Ivanov mr.wei...@gmail.com>> wrote:
> >>
> >> Filed the ticket [1], will fix.
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-8478 <
> https://issues.apache.org/jira/browse/IGNITE-8478>
> >>
> >>> On 12 M
On Mon, May 14, 2018 at 3:55 PM, Vladimir Ozerov
wrote:
> Hi Dima,
>
> This is not that simple unfortunately. We need to build the whole
> infrastructure for cache-less SQL queries. This is not very complex, but
> require considerable efforts. Let's do that in AI 2.6 scope.
>
Got it, thanks!
Igniters,
Any reason SqlLine tool shipped with Ignite does not work with Java 9? This
is the error I got.
> *The version of JAVA installed in C:\Program Files\Java\jdk-9.0.1 is
> incorrect.*
> *Please point JAVA_HOME variable to installation of JDK 1.7 or JDK 1.8.**You
> can also download latest
Igniters,
Jhipster is a very popular Spring Boot + Angular framework. Many caching
frameworks integrate with it, including EhCache, Hazelcast, and Infinispan:
https://www.jhipster.tech/using-cache/
I think the integration is fairly simple and we should provide our own.
Thoughts?
D.
Igniters,
I just noticed this horrible ticket:
https://issues.apache.org/jira/browse/IGNITE-6677
Apparently, a couple of releases back the community added support for
"CREATE TABLE" command and for some reason nobody checked that query
metrics on the created tables do not work.
Do we have any id
Pavel,
Can you suggest what would be the advantages and disadvantages of
supporting different versions?
D.
On Sat, May 12, 2018 at 7:21 AM, Pavel Petroshenko
wrote:
> Igniters,
>
> Are there any strong opinions on which language versions should the Thin
> Clients written in Python and PHP supp
ent/jdbc/
> con1491-3961036.pdf
> [2] http://mail.openjdk.java.net/pipermail/jdbc-spec-discuss/
> [3] https://github.com/oracle/oracle-db-examples/tree/master/java/AoJ
> [4] https://github.com/pgjdbc/pgjdbc/issues/978
>
> On Fri, May 11, 2018 at 9:48 PM, Dmitriy Setrakyan
>
On Fri, May 11, 2018 at 7:46 PM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> I will edit IGNITE-8475, and remove all part that belong to the public api.
> Is it acceptable for you?
>
Everything is acceptable, as long as the public API is safe :)
On Fri, May 11, 2018 at 7:23 PM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Dmitriy S,
>
> If it will be in the internal package, and only for internal usage, are you
> agree with changes?
>
Yes, but please be careful not to create deadlocks for ourselves.
Can you please close t
On Fri, May 11, 2018 at 6:49 PM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Dmitriy S,
>
> It is not broke existing code, because for use this ability you must use
> decorator "withFairSycn()".
>
> What about the argument of Vladimir?
>
Here is Vladimir's quote:
*This would als
On Fri, May 11, 2018 at 6:38 PM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Dmitriy S,
>
> Why method named as "async" but does not work as async? This is misleading.
>
> getAllAsync() is a special case. Not always you can use getAllAsync()
> instead
> of multiple getAsync().
> In
On Fri, May 11, 2018 at 6:29 PM, Dmitry Pavlov
wrote:
> IMO you can complete async operations one before another if these
> operations are related to independent data.
>
> It is strange why Ignite users are not confused by current API. So I
> support Dmitriy's G. suggestion.
>
Again, this is a s
Guys,
I am not sure I like this approach, especially for this code:
f1=cache.getAsync(key1);
f2=cache.getAsync(key2);
You cannot complete f2 before f1. If you do, the code is unusable and it is
impossible to predict anything. If you need to get 2 elements
asynchronously, use getAllAsync() instea
On Fri, May 11, 2018 at 9:14 AM, Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com> wrote:
> Not yet. Need a help with that.
>
I think we definitely need a load test before we merge to master. Can
anyone in the community assist Alexey?
This is great! Finally a native NodeJS client for Ignite.
Alexey, in addition to the functional tests, were you able to perform any
load tests?
D.
On Fri, May 11, 2018 at 12:07 AM, Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com> wrote:
> Folks,
>
> The next version is ready -
> in the pull r
Would be nice to have a TC run on Graal, just to have an understanding
whether we support it or not.
D.
On Wed, May 9, 2018 at 4:28 PM, Denis Magda wrote:
> The performance might become better just by replacing HotSpot with Graal,
> but something suggests me that Ignite has to be adopted for th
On Tue, May 8, 2018 at 6:23 PM, Denis Magda wrote:
> Dmitriy,
>
> Presently this information is scattered and presented under sections named
> differently. Agree with the format proposed by you.
> https://issues.apache.org/jira/browse/IGNITE-8455
>
> In addition, we should cover another mode whic
Igniters, let's make sure we add ticket description to the email subject in
future, so the community will know what the ticket is about. Not everyone
has time to look for the ticket, especially when the link is not even
provided in the email.
For example, the subject of this thread should have bee
gt; > implementation.
> >
> > Pros: Persistent users will not be facing with disabled rebalancing in
> case
> > of node left - (BL)AT will be changed automatically. This also be handled
> > by cluster shrink policy for both in-memory and durable cases.
> >
> > S
Is this list on the Wiki?
On Mon, May 7, 2018 at 7:26 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> This is the checklist I have at the moment. Please let me know if you have
> any comments on existing items, or want to add or remove anything. It looks
> like we may have not only strict rules, but
Great progress and thanks to everyone contributing! I can hardly wait for
the 0-failed-tests day. Hope it is coming some time in future :)
On Mon, May 7, 2018 at 3:38 AM, Dmitry Pavlov wrote:
> Hi Folks,
>
> I've started mass run-all last weekend. In short - 361 tests failed, and
> 12 suites we
On Mon, May 7, 2018 at 2:09 AM, Vladimir Ozerov
wrote:
> Hi Dima,
>
> Update with indexes would definitely be slower than update without them.
> The question is how much slower. For now the slowdown comes mostly from
> excessive data page reads ([1] and [2] in my previous email) leading to
> page
ost.
>
> [1]
> https://issues.apache.org/jira/browse/IGNITE-8385
> [2]
> https://issues.apache.org/jira/browse/IGNITE-8384
> [3]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 20%3A+Data+Compression+in+Ignite#IEP-20:DataCompressioninIgnite-
> IndexP
I have been going through the Ignite website today, and I have noticed that
nowhere on the website we mention various modes on how Ignite native
persistence can be used:
- no disk, data is in memory-only (potentially over a 3rd-party database)
- disk is a copy of the memory (only for recovery purp
Igniters,
One of the main complaints I hear from users is that whenever the
persistence is turned on, index creation can really slow down the
performance, because of massive amounts of writes to disk. The reason
Ignite is writing indexes to disk is to support fast restarts - nothing
needs to be re
I do not like the name "current" on the methods. I think we should just
remove it, e.g. currentAffinityTopology() -> affinityTopology()
D.
On Fri, May 4, 2018 at 6:17 AM, Eduard Shangareev <
eduard.shangar...@gmail.com> wrote:
> Igniters,
>
> With Vladimir's help, we analyzed another solution's
Hi Monil,
Welcome to the Ignite community! Please use dev@ alias going forward
instead of dev-owner@.
Ignite comes with lots of examples. You can also find documentation and
screencasts on the Ignite website. If you run into any questions, please
send them here.
D.
On Tue, May 1, 2018 at 7:44 P
On Wed, May 2, 2018 at 4:15 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Vyacheslav,
>
> There is already a warning for this:
> https://github.com/apache/ignite/blob/master/modules/
> core/src/main/java/org/apache/ignite/internal/processors/cache/store/
> GridCacheStoreManager
Igniters,
This is another usability issue that can be addressed quickly. Apparently,
setWriteBehindEnabled(true) is not enough to enable CacheStore, the
setWriteThrough(true) also needs to be enabled.
https://stackoverflow.com/questions/50118842/write-behind-and-write-through
Why not make it eas
Hi Mihkel,
I just added you to the Ignite contributors list in Jira. You should be
able to assign the ticket to yourself now.
D.
On Mon, Apr 30, 2018 at 6:42 AM, Mihkel Jõhvik
wrote:
> Hi
>
> I'd like to be added to the Apache Ignite contributors list to work on
> https://issues.apache.org/jir
Can someone explain what is the before and after effect for this change
from the usability standpoint. If we are changing BLT for the in-memory
mode, which is the default, then we must think through all the usability
consequences ahead of time. Otherwise, the perception will be that the
product sto
On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov wrote:
> Folks,
>
> I have a fix for a critical issue related to WAL compaction:
> https://issues.apache.org/jira/browse/IGNITE-8393
> In short, if part of WAL archive is broken, attempt to compress it may
> result in spamming warnings in infinite loop.
On Thu, Apr 26, 2018 at 9:09 PM, Vladimir Ozerov
wrote:
> It is impossible to estimate what is more critical because it would require
> prototypes for every idea to estimate the impact. Instead, we should start
> working on the simplest things, such as IGINTE-8386 [1] or IGNITE-8384 [2].
> And th
On Wed, Apr 25, 2018 at 5:45 PM, Vladimir Ozerov
wrote:
> Yakov,
>
> Thread-per-partition is hardly applicable for general SQL use case as user
> operates on arbitrary data sets. But in general we may track size deltas
> for partitions on transaction level. If transaction span one or several
> pa
Ed, how difficult is this fix? Are you suggesting it for 2.5?
On Thu, Apr 26, 2018 at 3:10 AM, Eduard Shangareev <
eduard.shangar...@gmail.com> wrote:
> Igniters,
> I have described the issue with current approach in "New definition for
> affinity node (issues with baseline)" topic[1].
>
> Now we
Thanks, Vladimir!
Looking at this IEP, it is not clear which tickets are more critical than
others. Also, the complexity of each ticket is unknown. Is there a way to
provide this information?
D.
On Wed, Apr 25, 2018 at 10:21 PM, Vladimir Ozerov
wrote:
> Igniters,
>
> I heard a lot of complains
Vova, what about maintaining the size as you go? This way you don't have to
count multiple versions, no?
D.
On Wed, Apr 25, 2018, 5:07 PM Vladimir Ozerov wrote:
> This is interesting question. Full-scan size may be tremendously slow
> operation on large data sets. On the other hand, printing to
On Wed, Apr 25, 2018 at 4:13 AM, Vladimir Ozerov
wrote:
> Right, as far as I understand we are not arguing on whether BLT is needed
> or not. The main questions are how to properly deliver this feature to
> users and how to deal with co-location issues between persistent and
> non-persistent cach
On Tue, Apr 24, 2018, 3:59 PM Denis Mekhanikov
wrote:
> Dmitriy,
>
> After the proposed changes are made the utility cache won't be needed at
> all.
>
I was rather talking about prioritization. In my view, first and foremost
we must fix deployment before anything else.
D.
Any chance we can add key-value support as well?
On Tue, Apr 24, 2018, 2:48 PM Pavel Tupitsyn wrote:
> Hi Aleksandr,
>
> This is awesome, thank you!
>
> However, let's make it clear that this client supports SQL only,
> and none of the other Thin Client protocol features.
>
> Pavel
>
> On Mon, A
org/jira/browse/IGNITE-5416 review?
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 6 июн. 2017 г. в 10:56, Dmitriy Setrakyan :
>
> > Thanks, Mike! Sounds great.
> >
> > On Tue, Jun 6, 2017 at 12:26 AM, Michael Griggs <
> > michael.gri...@gridgain.com
> > >
Dmitriy, who is a good candidate within the community to review this ticket?
On Mon, Apr 23, 2018 at 6:10 AM, Dmitry Pavlov
wrote:
> Hi Igniters,
>
> it seems ticket https://issues.apache.org/jira/browse/IGNITE-5565 is still
> in PA state. What are our next steps?
>
> Who did review of this patc
On Sun, Apr 22, 2018 at 10:16 PM, Denis Magda wrote:
> If a table is created with CREATE TABLE command then:
>
>- Ignite creates two custom binary types (one for the key and one for
>the value) the columns will be wrapped into. A primary key defines what
>goes into the key. It happens
rrect.
>
> --
> Denis
>
>
> On Sun, Apr 22, 2018 at 7:54 AM, Dmitriy Setrakyan
> wrote:
>
> > Igniters,
> >
> > Do we support write-through to a 3rd party database when performing SQL
> > inserts and updates? If yes, how does the mapping between SQL and
> > CacheStore key-value API happen?
> >
> > D.
> >
>
Igniters,
Do we support write-through to a 3rd party database when performing SQL
inserts and updates? If yes, how does the mapping between SQL and
CacheStore key-value API happen?
D.
>
> On Sat, Apr 21, 2018 at 3:04 AM, Dmitriy Setrakyan
> wrote:
>
> > I am not sure why we are discussing a potential removal of the "init"
> > method. I think it is useful, as the service may have to do some
> > initialization before it goes online. I
On Fri, Apr 20, 2018 at 4:50 AM, Anton Vinogradov wrote:
> P.s. Andrey Kuznetsov, corrected me that we have no warranty that failed
> node able to notify cluster.
>
> But,
>
> try{
>sendDiscoveryMessageWithFail(...);
> } catch(){
>// No-op;
> }
>
> is better than nothing, I think.
>
Agre
> > > > > > > > >> though.
> > > > > > > > > > >> > >
> > > > > > > > > > >> > > -Val
> > > > > > > > > > >> > >
> > > > > >
ve
> > >>>>>>>>>>> dependencies? Can it run stand-alone without writing code?
> > >>>>>>>>>>>
> > >>>>>>>>>>> Hope this helps,
> > >>>>>>>>>>>
&g
On Thu, Apr 19, 2018 at 8:19 AM, Yakov Zhdanov wrote:
> Guys,
>
> We have activity to implement a set of mechanisms to handle critical issues
> on nodes (IEP-14 - [1]).
>
> I have an idea to spread message about critical issues to nodes through
> entire topology and put it to logs of all nodes. I
On Tue, Apr 17, 2018 at 4:38 PM, Denis Magda wrote:
> Dmitriy,
>
> We don't want to disable the baseline topology for the scenario discussed
> here. The goal is to make it more flexible by triggering the rebalancing in
> some circumstances.
>
> As for the SAFE or AGGRESSIVE policies, haven't seen
On Tue, Apr 17, 2018 at 10:47 AM, Denis Magda wrote:
> Thanks, Pavel!
>
> Alexey, Ivan, could you check that there are no any pitfalls in the example
> and it can be used as a template for our users?
> https://issues.apache.org/jira/secure/attachment/
> 12919452/BaselineWatcher.java
Denis, I th
On Thu, Apr 12, 2018 at 9:45 AM, Ivan Rakov wrote:
> Dmitriy,
>
> fsync() is really slow operation - it's the main reason why FSYNC mode is
> way slower than LOG_ONLY.
> Fix includes extra fsyncs in necessary parts of code and nothing more.
> Every part is important - at the beginning of the thre
gt; core or optional?
> > >>>>>
> > >>>>> чт, 15 мар. 2018 г. в 22:09, Denis Magda :
> > >>>>>
> > >>>>>>>
> > >>>>>>>>
> > >>>>>>>>
This is what I see (attached)
On Wed, Apr 11, 2018 at 1:52 AM, Alexey Kuznetsov
wrote:
> I have no problems.
>
> Try other browser / or force refresh of page.
>
> On Wed, Apr 11, 2018 at 3:49 PM, Dmitriy Setrakyan
> wrote:
>
> > Igniters,
> >
> > The r
Igniters,
The readme documentation seems broken. Is it only for me, or others
experience the same thing?
https://apacheignite.readme.io/docs
Did anyone change anything in the docs settings?
D.
On Tue, Apr 10, 2018 at 11:57 PM, Ilya Suntsov
wrote:
> Dmitriy,
>
> I've measured performance on the current master and haven't found any
> problems with in-memory mode.
>
Got it. I would still say that the performance drop is too big with
persistence turned on. It seems like we did not just fi
On Tue, Apr 10, 2018 at 2:22 PM, Alew wrote:
> Hi!
>
> I use local cache and get a lot of warnings when execute ScanQueries.
>
> [13:26:25 WRN] Ignoring query projection because it's
> executed over LOCAL cache (only local node will be queried):
> GridCacheQueryAdapter [type=SCAN, clsName=null,
On Tue, Apr 10, 2018 at 2:03 PM, akurbanov wrote:
> Dmitry,
>
> Sorry for confusing topic. I I'm pretty sure that configuration for atomic
> caches is validated, will double-check this. I was referring only atomic
> data structures cache.
>
Got it. We should definitely add validation for the ato
oks perfectly ok to me provided that we compare correct
> implementation with incorrect one.
>
> вт, 10 апр. 2018 г. в 18:24, Dmitriy Setrakyan :
>
> > Ilya, can we find out why pure in-memory scenario also had a performance
> > drop and which commit caused it? It should no
gt;>>>>> +1 for accepting drop in LOG_ONLY. 7% is not that much and
> > > >>>>>>>>>>>> not a
> > > >>>>>>>>>>>>>> drop
> > > >>>>>>>>
Vladimir, sounds like a huge refactoring. Other than "cache groups are
confusing", are we solving any other big issues with the new proposed
approach?
(every time we try to refactor rebalancing, I get goose bumps)
D.
On Tue, Apr 10, 2018 at 1:32 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> Cache
On Tue, Apr 10, 2018 at 12:28 AM, Alexey Kuznetsov
wrote:
> Dmitriy,
>
> Yes, because we have a command "Add new user" and this command can be
> executed only with credentials of some "admin" user.
>
> It means, that in one command you need to specify name of new user and
> "admin" credentials at
Alexey, are you suggesting that we have "newUser" as command parameter, while
"user" is also a valid command parameter?
D.
On Apr 10, 2018, 12:00 AM, at 12:00 AM, Alexey Kuznetsov
wrote:
>I looked into code and I think that we could do the following:
>
>1) Use user and password for authenti
On Mon, Apr 9, 2018 at 6:29 AM, Ilya Lantukh wrote:
> Anton,
>
> Please do not use term "atomic cache" for system caches that hold internal
> data for atomic data structures. This is very confusing.
>
> You are right, currently there is no logic that will validate cache
> configuration. It defini
On Mon, Apr 9, 2018 at 5:42 AM, Alexey Goncharuk wrote:
> Guys,
>
> After the review in Upsource the configuration parameter was renamed
> to txTimeoutOnPartMapSync, and it makes sense to me because PME is an
> implementation detail and it may change in future, partition map sync is a
> more abst
I would say absolutely YES - we need to have configuration validation.
Igniters, why was the validation skipped in atomic caches?
D.
On Fri, Apr 6, 2018 at 1:43 PM, akurbanov wrote:
> Hello Igniters,
>
> I want to address a question on AtomicConfiguration validation. I've tested
> in ignite-1.
On Fri, Apr 6, 2018 at 9:13 AM, Dmitry Pavlov wrote:
> Hi Igniters,
>
> I like automatic redeploy which can be disabled by config if user wants to
> control this process. What do you think?
>
I do not think we should have anything automatic when it comes to
deployment, everything should be expli
Here is a correct link to IEP:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-18%3A+Transparent+Data+Encryption
On Thu, Apr 5, 2018 at 12:01 PM, Nikolay Izhikov
wrote:
> Hello, Igniters.
>
> Based on previous discussion [1] we've created "IEP-18: Transparent Data
> Encryption" [2]
> I've
Vladimir, my older email got kind of lost. Can you please clarify, will we
be able to support both, older and newer formats, to avoid a breaking
compatibility change between releases?
D.
On Thu, Apr 5, 2018 at 5:53 AM, Vladimir Ozerov
wrote:
> I think colon is not very good candidate as it clas
On Wed, Apr 4, 2018 at 5:27 AM, Alexey Goncharuk wrote:
> Denis,
>
> I think this particular metric should be deprecated. The most we can do
> about it is to return the actual allocated size when a cache is the only
> cache in a group and return -1 if there are multiple caches in a group.
> Howev
Here is the correct link:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Oil+Change+in+Service+Grid
I have looked at the tickets there, and I believe that we should not
support peer-deployment for services. It is very hard and I do not think we
should even try.
I am proposing closin
Igniters,
Dmitriy Pavlov is working very hard on making sure that we do not have
failing tests in Ignite. Let's help him in this effort. I would like to
encourage the committers responsible for the failing tests to either fix
them or remove them.
Please respond here.
D.
On Tue, Apr 3, 2018 at 5
201 - 300 of 2105 matches
Mail list logo