В Пт, 28/06/2019 в 19:10 +0300, Nikolay Izhikov пишет:
> Hello, Maksim.
>
> I will take a look shortly.
>
> В Пт, 28/06/2019 в 19:02 +0300, Maksim Stepachev пишет:
> > Hello, Igniters.
> >
> > I see that the ticket - "[IGNITE-11848] New Monitoring. Phase1&q
; practice in industry?
>
> Also, looking at a line like "cache.my-cahe.GetLatency=50,100,250,500"
> I cannot tell much from scratch. My first thought is that having named
> parameters can be more readable, e.g. (roughly):
> cache.my-cahe.GetLatency={
> inte
Guys.
I've prepared PR to fix this issue.
Who want to review it?
https://github.com/apache/ignite/pull/6656
В Пн, 01/07/2019 в 15:17 +0300, Nikolay Izhikov пишет:
> Hello, Igniter.
>
> I think we should fix the issue with slight changes in internal API (was not
> released y
Fix merged to master.
Guys, thanks for the help!
В Вт, 02/07/2019 в 18:25 +0300, Alexey Goncharuk пишет:
> Hello Nikolay,
>
> I will take a look shortly.
>
> вт, 2 июл. 2019 г. в 14:30, Nikolay Izhikov :
>
> > Guys.
> >
> > I've prepared PR to
Hello, Denis.
Who can contribute to gridgain/h2?
Who are commiters of gridgain/h2?
В Чт, 04/07/2019 в 19:26 +0300, Dmitriy Pavlov пишет:
> Hi Denis,
>
> As you know, some time ago I've started a discussion about removing
> dependence from gridgain:shmem. Ignite community seems to be not so muc
ey Gura wrote:
> >
> > Nikolai,
> >
> > Metric is disabled if it doesn't allocate any memory and doesn't
> > update any variable because doesn't have any value. Ideally disabling
> > metrics for some cache should be equal to cache stopping.
>
to tell users that any changes in configuration file have no
> > effect on Ignite configuration after first start?
> >
> > I think there are too many open questions and (at least at now) we should
> > provide only JMX API until all of the questions are clarified.
> >
> &
Igniters,
I made a PR for metrics configuration.
Please, review
https://github.com/apache/ignite/pull/6676/files
В Вт, 09/07/2019 в 12:27 +0300, Nikolay Izhikov пишет:
> Hello, Alex.
>
> OK, Let's go with the simplest solution.
> I will provide API and JMX method for metr
Hello, Denis.
> Nickolay, as for that fork which is in GG codebase - GridGain is a major
> contributor and maintainer but the others are welcomed to send
> pull-requests.
Can we make this fork maintained by Ignite Community?
With all respect to Grid Gain as an author of Apache Ignite I don't lik
if later on some problems with
> that appear we can clone it and use that new fork without much
> trouble, can't we?
>
> ср, 10 июл. 2019 г. в 09:52, Nikolay Izhikov :
> >
> > Hello, Denis.
> >
> > > Nickolay, as for that fork which is in GG codebas
g version X and version Y of the same
> library. Version Y might be better.
>
> > I think all Ignite commiters should have write priveledges to H2 fork.
> I agree, it is quite natural. Actually, my only point is that we can
> do it at any point later, cannot we?
>
> ср, 10 июл.
> > > Could you please elaborate why is it "closed source"?
> > > >
> > > > > What the difference for the Ignite community?
> > > >
> > > > The difference is similar to using version X and version Y of the same
> > >
Anton,
> - metrics are better for monitoring, but the Event is enough for my wish to
> cover AI with consistency check,
Can you clarify, do you have plans to add metrics of RR events?
I think it should be count of incosistency events per cache(maybe per
partition).
В Чт, 11/07/2019 в 09:53 +
I did the review.
пн, 15 июля 2019 г., 16:15 Dmitriy Pavlov :
> Igniters, who did a review of
> https://issues.apache.org/jira/browse/IGNITE-10663 before the merge? I've
> checked both PR https://github.com/apache/ignite/pull/5656 and Issue,
> and dev.list thread and didn't find any LGTM.
>
>
+1.
Nikita, please, go ahead.
вт, 16 июля 2019 г., 11:45 Nikita Amelchev :
> Hello, Igniters.
>
> I suggest to add some useful metrics about the partition map exchange
> (PME). For now, the duration of PME stages available only in log files
> and cannot be obtained using JMX or other external t
1 simple metric: are operations blocked?
> Just a true or false.
> Lest start from this.
> All other metrics can be extracted from logs now and can be implemented
> later.
>
> On Tue, Jul 16, 2019 at 12:46 PM Nikolay Izhikov
> wrote:
>
> > +1.
> >
> >
e of this.
> The goal it so show exactly blocking period.
> When PME cause no blocking, it's a good PME and I see no reason to have
> monitoring related to it :)
>
> On Tue, Jul 16, 2019 at 2:50 PM Nikolay Izhikov wrote:
>
> > Anton.
> >
> > Why do we need t
Hello, Igniters.
Dmitriy, can you, please, create an Ignite Jira ticket from your internal? [1]
Or change link to existing Ignite ticket.
There is other link to GG ticket through the code bringed by your merge.
```
@Ignore("https://ggsystems.atlassian.net/browse/GG-20800";)
```
[1]
https:
+1
пт, 19 июля 2019 г., 19:17 Denis Magda :
> Thanks Dmitry, this looks good to me.
>
> -
> Denis
>
>
> On Fri, Jul 19, 2019 at 9:08 AM Dmitriy Pavlov wrote:
>
> > Hi Igniters,
> > Please review following announce email for 2.7.5. I would like to send an
> > email during the weekend.
> > {{{
> >
Dmitriy, thanks!
сб, 20 июля 2019 г., 12:10 Dmitriy Govorukhin :
> Nikolay, my fault, already fixed.
>
> https://issues.apache.org/jira/browse/IGNITE-11998
>
> On Thu, Jul 18, 2019 at 4:06 PM Nikolay Izhikov
> wrote:
>
>> Hello, Igniters.
>>
>> Dmitriy,
much time we
> >> wait for
> >> >> > resuming cache operations instead of instant boolean indicator.
> >> >> >
> >> >> > пт, 19 июл. 2019 г. в 14:41, Nikita Amelchev >:
> >> >> >
> >> >> > > Anton, Nikolay,
> &g
Hello, Akhil.
There are no specific dates for now.
But, as always, you can easily build distr from sources.
We try to keep Ignite master release ready.
пн, 22 июля 2019 г., 19:37 apada...@kent.edu :
> Hello Ignite team ,
> I am looking for 2.8 version release, specifically for automatic baselin
t;
>
> On Mon, Jul 22, 2019 at 9:41 AM Nikolay Izhikov wrote:
>
> > Hello, Akhil.
> >
> > There are no specific dates for now.
> > But, as always, you can easily build distr from sources.
> > We try to keep Ignite master release ready.
> >
> >
&
gt; >
> > > > Hi igniters,
> > > >
> > > > I can see a question on SO
> > > > http://apache-ignite-developers.2346864.n4.nabble.com. The question is
> > > > related to encryption.
> > > > Nikolay I
> >> >
> > >> > вт, 23 июл. 2019 г. в 11:42, Nikita Amelchev < nsamelc...@gmail.com
> >:
> > >> >
> > >> >> Folks,
> > >> >>
> > >> >> All previous suggestions have some disadvantages. It can be se
tionsBlockedDuration.
> >
> > No other changes will require.
> >
> > WDYT?
> >
> > On Wed, 24 Jul 2019 at 14:02, Nikita Amelchev wrote:
> > > Nikolay,
> > >
> > > The сacheOperationsBlockedDuration metric will show current blocking
anov :
> >
> >
> >
> > > On 11 Dec 2018, at 10:10, Nikolay Izhikov wrote:
> > >
> > > Hello, Ivan.
> > >
> > > Personally, I keep my PR's clear.
> > > So, I don't have dozens of opened PR.
> > >
&g
Yes.
Do someone have permission to close my(or any other contributor) PR to
apache/ignite?
В Чт, 25/07/2019 в 11:05 +0300, Павлухин Иван пишет:
> NIkolay,
>
> Do you mean technical ability?
>
> чт, 25 июл. 2019 г. в 10:33, Nikolay Izhikov :
> >
> > Hello, Iv
em will be superfluous.
> 1. The totalCacheOperationsBlockedDuration metric that will accumulate
> all blocking durations that happen after node starts.
> 2. Blocking duration histogram. Based on the HistogramMetric class.
> User will be able to configure bounds.
>
> ср, 24 июл. 2019 г. в 18:26, Nikolay Izhi
июля 2019 г., 18:55 Pavel Kovalenko :
> Nikolay,
>
> Could you please explain deeper what structure will be of PME histogram?
>
> чт, 25 июл. 2019 г. в 11:56, Nikolay Izhikov :
>
> > Hello, Nikita.
> >
> > I think
> >
> > > 1. The totalCacheOp
ram do you know how we can find exact time e.g. when PME
> with time > 1s happened?
>
> чт, 25 июл. 2019 г. в 19:24, Nikolay Izhikov :
>
> > Pavel
> >
> > Do you have a chance to see HistogramMetric source?
> > It in master now.
> > Look in source woul
+1 to revert.
В Пт, 26/07/2019 в 09:48 +0300, Павлухин Иван пишет:
> Alexey,
>
> Actually the commit [1] is very suspicious:
> 1. Commit message "[ML] Hyper-parameter tuning via Genetic Algorithm
> (#6713)" does not refer to a ticket.
> 2. Is there a ticket? Consequently it is not easy to underst
gt; I just want to add that currentPmeTime is also useful alerting systems, not
> only for eye observing. If the time become too long and exceeds some
> threshold appropriate alert firing can help to early determine a critical
> problem.
>
> On Thu, 25 Jul 2019 at 21.12, Nikolay Izh
name addition) is enough to finish this issue?
> >
> > Thanks a lot for the clarification
> >
> > пт, 26 июл. 2019 г. в 18:28, Dmitriy Pavlov :
> >
> > > +1 to revert. Some day we should learn this process. Maybe this day is
> > > today.
>
Thanks!
В Пн, 29/07/2019 в 06:02 -0500, nsvistov пишет:
> Hi all,
> service ci.ignite.apache.org is available
> We will try to backup our connection with second internet provider
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
signature.asc
Description: This is
Hello, Pavel.
I think we shouldn't reduce flexibility of NodeFilter.
So, I am -1 to remove it in Ignite 3.
Instead, Ignite can provide NodeAttributeFilter implementation of NodeFilter.
Seems, it will resolve all described issues.
В Чт, 01/08/2019 в 19:33 +0300, Ilya Kasnacheev пишет:
> Hello!
>
) code involved?
>
> Also I it is quite interesting for me what flexibility you are
> thinking about? I think that the topic is quite important and it would
> be great to collect use cases and describe best practices in
> documentation.
>
> пн, 5 авг. 2019 г. в 15:38, Nikolay Izhikov
.
>
> So I think we should drop this change and idea about runtime
> histrogram and hit rate configuration.
>
> Thoughts?
>
> On Tue, Jul 9, 2019 at 2:06 PM Nikolay Izhikov wrote:
> >
> > Igniters,
> >
> > I made a PR for metrics configuration.
>
problems
> described in the topic.
> I don't see yet any practical cases with NodeFilter that can't be resolved
> using just labels.
>
>
>
> пн, 5 авг. 2019 г. в 16:28, Nikolay Izhikov :
>
> > Ivan,
> >
> > ~Mail~ Talks a
exponential bounds' values for histograms.
> Anyway, in current solution it looks ugly and not usable.
>
> > Ignite has dozens of use-cases and deployment modes, seems,
> > we can't cover it all with the single predefined buckets/rateTimeInterval
> > set.
>
>
Hello, Denis.
Thanks for starting this discussion.
I think we have to write proper javadoc for all production classes, including
internal.
We should fix useless javadoc you provide.
We should not accept patches without good javadocs.
As for the tests, seems, we can make javadoc optional.
What
Maxim, thank you!
Great job!
PR looks good to me.
Who else want to take a look?
В Ср, 07/08/2019 в 17:01 +0300, Maxim Muzafarov пишет:
> Igniters,
>
> I think the PR [2] of the issue [1] is ready to be merged.
> Thanks to Nikolay Izhikov for the great review!
> The IEP-28 con
Hello, Deni.
> Nickolay, could you check if that's a quick upgrade?
Yes, I will take a look.
В Чт, 08/08/2019 в 11:08 -0700, Denis Magda пишет:
> Dmitry,
>
> Please add this BTree corruption fix to the scope:
> https://issues.apache.org/jira/browse/IGNITE-11953
>
> Plus, I would upgrade our S
Hello, Igniters.
Looks like TC has the issues with the free disk space [1]
Can someone take a look?
```
[19:13:00]Free disk space requirement
[19:13:00][Free disk space requirement] Removing files to meet 3 GB of free
disk space required for directory /opt/buildagent/temp (only 122.05 MB is
free
Hello, Igniters.
Looks like TC has the issues with the free disk space [1]
Can someone take a look?
```
[19:13:00]Free disk space requirement
[19:13:00][Free disk space requirement] Removing files to meet 3 GB of free
disk space required for directory /opt/buildagent/temp (only 122.05 MB is fr
Hello, Maxim.
I think backup is a great feature for Ignite.
Let's have it!
Few notes for it:
1. Backup directory should be taken from node configuration.
2. Backup should be stored on local node only.
Ignite admin can write sh script to move all backuped partitions to one storage
by himself.
27;ll give you a detailed
> answer in an appropriate discussion topic [1] a bit later.
>
> [1]
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Hot-cache-backup-td41034.html
>
> On Wed, 14 Aug 2019 at 16:40, Nikolay Izhikov wrote:
> >
> > Hello, Maxim
> > > > > > > unexpressive/misleading comment.
> > > > > > > > - Even classes may not require javadocs, e.g. simple DTOs.
> > > > > > > >
> > > > > > > > ср, 7 авг. 2019 г., 13:39 Denis Garus :
> > > > > > &g
gt; >
> > > > See https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > > for
> > > > more details.
> > > >
> > > > пн, 12 авг. 2019 г. в 16:37, Zhenya Stanilovsky
> > > > > > > > :
> > > &
Dmitriy, Thanks!
В Чт, 22/08/2019 в 15:09 +0300, Dmitriy Pavlov пишет:
> Hi Igniters,
>
> A number of updates were applied to the process description. Feedback is as
> always welcomed.
>
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>
> I can't name it final cause I find
Hello, Dmitriy.
Seems, we have some issue here.
I also run this suite and got informative error [1]. You can find it in log:
```
[15:07:05] : [Step 6/8] [Maven Watcher]
[15:07:05]E: [Step 6/8] Failed to execute goal on project ignite-jta: Could
not resolve dependencies for project org.a
gt;
> > >
> > > also, it may be the same issue with
> > >
> > > http://apache-ignite-users.70518.x6.nabble.com/Fail-to-compile-apache-ignite-1-7-0-td7458.html
> > >
> > > Did you check release locally?
> > >
> > > пт, 23 авг. 2
Hello, Igniters.
There are plenty of options to store application files in linux:
* /usr/local/ignite
* /var/ignite
* /var/lib/ignite
* ~/.ignite/
* /opt/ignite/
Seems, ~/ignite/work (without a dot in the beginning) is not a Linux-way naming.
Postgresql use '/usr/local/pgsql/`
Mysql use '/var/l
Ilya,
> We are talking about development scenario where you have embedded database
> in your project and it has to write data somewhere.
Why it should differs from production case?
I think we should be as close to production setup as we can.
> /var/lib/ignite is certainly not writable by user's
Ilya,
> In development environment one can just run Java from /var/lib/ignite
Actually, I doesn't understand you.
Are you talking about development of some application that uses Ignite or
contribution to Ignite code base?
If we are talking about some application that uses Ignite then we should
)/var/ignite
> > 7)/var/lib/ignite
> > 8)/opt/ignite/
> >
> > +1 for '~/.ignite/work'
> >
> > --
> > Best regards,
> > Anton Kalashnikov
> >
> >
> > 26.08.2019, 12:39, "Nikolay Izhikov" :
> > > Ilya,
> > >
Yes, of course.
В Пн, 26/08/2019 в 13:58 +0300, Petr Ivanov пишет:
> Does this parameters intended to be overridden (for tests purposes for
> example) or it will be permanently sticked to this new directory without
> ability to change?
>
>
> > On 26 Aug 2019, at 13:58, N
changes completed. You can try to enable java-9+
> maven profile.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> пн, 26 авг. 2019 г. в 10:43, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > I tried to build Ignite locally from sources on java 1
gt; > 8. I could find a ticket if it is necessary.
> > >
> > > There are some changes which should help to bypass IgniteLinkTaglet
> >
> > issue,
> > > but I couldn't call these changes completed. You can try to enable
> >
> > java-9+
> >
Hello, Ilya.
We can't have discussion if you only make statements, but don't answer the
questions :)
I repeat my own statements and questions to you.
*How do you think, what is primary usage scenario for Ignite with PDS enabled
cache?*
If we are talking about some application that uses Ignite
AFAIK server admin expects software will store it's data in /var/ directory,
not in /home directory.
> In Docker age, packages are becoming extinct.
I don't agree with that, but seems, it's not a subject of discussion. :)
> we don't even have very good packages today
Why do you think we don't
Anton,
Can we create channels for ticket, IEP discussions in ASF slack?
В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет:
> Igniters,
> I'd like to propose you to register at the ASF Slack [1] (committers seems
> to be already registered) and join the Ignite channel [2].
> This should sim
t;? :)
How do you see support of several Spark version?
В Ср, 28/08/2019 в 14:29 +0300, Alexey Zinoviev пишет:
> Dear Nikolay Izhikov
> Are you going to update the Ignite-Spark integration for Spark 2.4. But the
> compatibility with Spark 2.3 will be broken, isn't it? Do you have any
of separate repository I could help, for example
>
> ср, 28 авг. 2019 г. в 14:57, Nikolay Izhikov :
>
> > Hello, Alexey.
> >
> > > But the
> > > compatibility with Spark 2.3 will be broken, isn't it?
> >
> > Yes.
> >
> >
Hello, Igniters.
I pushed 2 commits in master by mistake(already reverted).
Sorry to anyone who bothered by that.
https://github.com/apache/ignite/commit/44d30bf0464a4e76fe66b45fc49f12c88c667573
https://github.com/apache/ignite/commit/0c125f635e62ce4b7801798e703895d610245bbf
https://github.com/a
mas
* SQL queries
* Continuous queries
* Text queries
* Transactions
* Cluster nodes
* Client connections(JDBC, ODBC, Thin)
[1] https://github.com/apache/ignite/pull/6845
[2] https://github.com/apache/ignite/pull/6790
пн, 10 июн. 2019 г. в 13:49, Nikolay Izhikov :
> Hello, Igniters.
>
>
Hell, Amit.
You can write you question here, on the dev-list or in the ticket.
I think, Ignite community will help you with this and ongoing contribution.
Welcome!
В Пн, 09/09/2019 в 11:14 -0700, Amit Chavan пишет:
> Hello,
>
> I need some help on the ticket
> https://issues.apache.org/jira/bro
Hello, Alexey.
Why do we need distributed metrics in the first place?
It seems, there are many metric processing system out there: Prometheus,
Zabbix, Splunk, etc.
Each of then can aggregate metrics in many ways.
I think, we should not use Ignite as an metrics aggregation system.
What do you t
javadocs for base interfaces aren't clear, too brief and doesn't
> give any imagine about whole picture.
>
> At present it is very hard to understand the purposes of new
> interfaces and walker generator, and design itself.
>
> On Fri, Sep 6, 2019 at 3:16 PM Nikolay I
should have public API for it, SQL API and JMX. There is
> no need any exporters.
>
>
> What do you think about it? Also it would be great to involve more
> people to this discussion.
>
> [1] https://reviews.ignite.apache.org/ignite/review/IGNT-CR-1065
>
&
we can use REST for access
> to this API. Also you can use public API directly. What is the reaal
> life uses cases for exporting views? Is there any database which
> exports some lists to somewhere? Especially on push based model, not
> on demand.
>
> On Fri, Sep 13, 2019 at 4:36
First, views and metrics are entities from different worlds/domains.
> Second, we will have less conflicts on GridMetricManager because we
> are still working on metrics and views concurrently.
> We can live with one manager for absolutely all entities in the system
> but we don't do it, righ
don't propose that.
> > What I propose is to have one manager for the same entities.
>
> But views and metrics are not the same entities.
>
> > Please, don't overact my words.
>
> Just some hyberbole, no more.
>
> On Mon, Sep 16, 2019 at 4:46 PM Nikol
Hello, Alexey
> we have no chance to
> release the whole master branch
Why do you think so?
From my point of view, we should start discussion of 2.7 release, shortly(end
of September of similar)
В Ср, 18/09/2019 в 12:04 +0300, Alexey Zinoviev пишет:
> Dear Igniters, for the whole year I'm waiti
> of 2.7 release
It's 2.8, of course. Sorry, for typo.
В Ср, 18/09/2019 в 12:36 +0300, Nikolay Izhikov пишет:
> Hello, Alexey
>
> > we have no chance to
> > release the whole master branch
>
> Why do you think so?
> From my point of view, we should start dis
start a discussion about releasing Apache Ignite 2.8
> > version right after 2.7.6 will be announced.
> > Am I missing something?
> >
> > On Wed, 18 Sep 2019 at 12:33, Nikolay Izhikov wrote:
> > >
> > > > of 2.7 release
> > >
> >
Hello, Nikita.
Thanks for starting this discussion.
1. We should add prerequisites for "master key rotation process" in design.
Seems, it should be, "New master key available to EncryptionSPI for each server
node".
2. Please, use code formatting in wiki. It's make reading easier.
3. Please, cl
Hello, liyuj.
Please, clarify.
Do you want to contribute this to Ignite?
What explanation do you expect?
В Ср, 18/09/2019 в 22:46 +0800, liyuj пишет:
> Hi,
>
> Can anyone explain how difficult it is to implement ROWNUM?
>
> This is a very common requirement.
>
> 在 2018/1/23 下午4:05, Serge Puch
of ROWNUM if you want.
В Чт, 19/09/2019 в 08:20 +0800, liyuj пишет:
> Hi Nikolay,
>
> Because in the discussion below, there is a list describing that ROWNUM
> is not applicable to Ignite, and I want to know why.
>
> 在 2019/9/18 下午11:14, Nikolay Izhikov 写道:
> > He
. For instance, ML
> >
> > and
> > > Thin Clients optimizations with fixes for newly discovered critical
> >
> > issues
> > > can be released in 2.7.7 and 2.7.8.
> > >
> > > As for 2.8, what exactly are we planning to release there?
> > &
s
> > >
> > > and
> > > > > > regressions we need to address. It can easily slip to the next year,
> > > > > > especially considering the holiday season. An alternate solution can
> > >
> > > be a
> > > > > >
Hello, Igniters.
Examples suite on TC doesn't work correctly under java9+. [1], [2]
The reason is the Spark examples.
Spark 2.3(our current version) work with scala 2.11 and scala 2.11 support of
java9+ is "incomplete".
Can we stick example suite to jdk8 only?
[1]
https://ci.ignite.apache.or
21:39, Denis Magda :
> Nikolay,
>
> What needs to be done to ensure Java 9++ works with Spark Examples? Do we
> need to create another Spark module or drop some scala version?
>
> -
> Denis
>
>
> On Thu, Sep 19, 2019 at 9:23 AM Nikolay Izhikov
> wrote:
>
oments. [1]
>
> [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381
>
> ср, 18 сент. 2019 г. в 16:48, Nikolay Izhikov :
> >
> > Hello, Nikita.
> >
> > Thanks for starting this discussion.
> >
> > 1. We should add prerequisites for &qu
Hello, Andrey.
Thanks for starting this discussion.
> 1. There is no unified approach to adding metrics during development.
Yes, we have it.
Just call `MetricRegistry#longMetric` or other method and you got your counter.
> Now the logic is spread throughout the code base and there is now any
>
hod gets default master key id used
> on first cluster start.
>
> The specific implementation will be responsible for setting this value.
>
> What do you think?
>
> пт, 20 сент. 2019 г. в 10:44, Nikolay Izhikov :
> >
> > Hello, Nikita
> >
> > >
ious method:
>
> byte[] masterKeyDigest()
> byte[] encryptKey(Serializable key)
> Serializable decryptKey(byte[] key)
>
> If such implementation is more reasonable, I will do so.
>
> пт, 20 сент. 2019 г. в 13:04, Nikolay Izhikov :
> >
> > Why do we
Hello, Alex.
Good catch, thank you.
I will add enabling of JMX and SQL exporters for system views, by default.
В Ср, 18/09/2019 в 16:09 +0300, Alex Plehanov пишет:
> One more point to discuss: Wouldn't it be better to have enabled system
> views by default?
> To enable views admin must restart t
Hello, liyuj
Thanks for your interest in Igniter.
Feel free to assign ticket to yourself.
Looking forward for your contribution!
В Сб, 21/09/2019 в 19:31 +0800, liyuj пишет:
> Hi community,
>
> The issue is relatively simple, and I can contribute.
> Can someone assign this to me? My JIRA ID is
0/09/2019 в 14:22 +0300, Nikolay Izhikov пишет:
> Hello, Alex.
>
> Good catch, thank you.
>
> I will add enabling of JMX and SQL exporters for system views, by default.
>
> В Ср, 18/09/2019 в 16:09 +0300, Alex Plehanov пишет:
> > One more point to discuss: Wouldn't
+1 to start releasing 2.8 in November or even in the end of October.
Alex, can we schedule some quick meetings in the new Ignite Slack chat and
discuss all release date details?
Wendseday, 25 September is good for you?
В Пн, 23/09/2019 в 13:31 +0300, Maxim Muzafarov пишет:
> Alexey,
>
> Can yo
tion.
В Пт, 20/09/2019 в 14:06 +0300, Nikita Amelchev пишет:
> Nikolay,
>
> you are right in many ways. I updated the design on the wiki. [1]
>
> [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381
>
> пт, 20 сент. 2019 г. в 13:49, Nikolay
r release. So it would
> be great to return to this discussion later. It seems that beginning
> of November is good time for it.
>
> On Mon, Sep 23, 2019 at 5:37 PM Alexey Zinoviev
> wrote:
> >
> > Nikolay Izhikov, ok, let's arrange the talk in ASF slack between 1
ck planned changes somehow?
>
> We have too many not resolved tickets under IEP-35 label [1]. Also it
> makes sense to do some usability testing: JMX beans interfaces, system
> views, etc.
>
>
> [1] https://issues.apache.org/jira/issues/?jql=labels%20%3D%20IEP-35
>
> O
; > > >
> > > > > > From my point of view monitoring isn't ready for release.
> > > > > Can you clarify, what exactly is not ready?
> > > > > Can we track planned changes somehow?
> > > >
> > > > We have too many no
we
> > can.
>
> Please, read my proposal again. Main point is code structure changing
> in order to simplify adding new metrics for developer.
>
> > Developer of specific metric shouldn't change dozens of static interfaces,
> > implementations, enable/disable methods.
Hello, Igor.
Thanks for starting this discussion.
I think we should take a step back in it and answer the following questions:
1. What the exact issues with the H2 integration?
Can you send a tickets links?
Can we label all H2 integration issues in JIRA? I propose to use "h2" label.
2. What ar
se.
> E.g. with Apache Calcite.
> - Calcite is a framework and it is designed very flexible and extendable.
> - Every it's part can be replaced with our own implementation.
> - Apache License is out of the box =)
>
> So, summary:
> 1-st way of pain we have now and it slo
Hello, Roman.
> Also Apache Calcite is commonly used in popular Apache projects
I don't think it's a good point.
H2 is also commonly used.
But, it doesn't conform to Ignite requirements.
Can you, please, write down issues and engine requirements to the IEP?
So we can discuss each point separatel
Hello, Roman.
All I see is links to two tickets:
IGNITE-11448 - Open
IGNITE-6085 - Closed
Other issues described poorly and have not ticket links.
We can't discuss such a huge change as an execution engine replacement with
descrition like:
"No data co-location control, i.e. arbitrary data can
501 - 600 of 1145 matches
Mail list logo
