requirements so we can reach a
consensus on that and therefore move to the discussion of the implementation?
> 6 июля 2020 г., в 11:18, Max Shonichev написал(а):
>
> Yes, Denis,
>
> common ground seems to be as follows:
> Anton Vinogradov and Nikolay Izhikov would try to p
All checks just force rules we agreed on.
> Why this check is so important? Why do you think it is more important than
> all other tasks/tests?
Because any code style violations should be fixed before the merge.
Therefore after the fix, you must rerun TC.
This means that running heavy suites whe
compile but will not pass
>> Checkstyle. That's a blocker.
>
> This issue has also been discussed here:
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Separate-code-sanity-check-and-build-task-td47003.html
>
> Thanks,
> Slava.
>
>
> вт, 7 и
as is,
> however, I do not want to waste my time fixing all code style violations.
> Does this use-case look reasonable?
>
> Thanks,
> Slava.
>
> вт, 7 июл. 2020 г. в 11:07, Nikolay Izhikov :
>
>> Slava.
>>
>> All contributors should follow our code sty
gt; (By the way, even though if I just want to start Cache1 suite, the
>>> Code-Style check executes anyway).
>>>
>>>> If we don’t want to follow the code style or considered it as a «waste
>> of
>>> the time» we should change it.
>>> This is abso
>>>>
>>>> So, the first step is similar to rotating the master key when the new
>>>> key was set for writing on all nodes - that’s it, the cache group key
>>>> rotation is complete (this is what PCI DSS requires - encrypt new
>>>> updates with new keys
Hello, Vasiliy.
This messages are shown on the different nodes, isn’t it?
> 10 авг. 2020 г., в 18:34, Vasiliy Sisko написал(а):
>
> In case of errors in user computations the Ignite Compute Grid produces a
> lot of errors into the log.
> In the worst way it produces the next messages:
>1. F
> I propose to stick with a cache-group level metric (e.g.
> getIndexBuildProgress)
+1
> that returns a float from 0 to 1, which is calculated as [processedKeys] /
> [localCacheSize].
From my point of view, we shouldn’t do calculations on the Ignite side if we
can avoid it.
I’d rather provid
I propose to add removals of the legacy JMX bean and Java metrics
We should use new metrics framework and JMX exporter instead of it.
> 14 авг. 2020 г., в 10:40, Pavel Tupitsyn написал(а):
>
> Val,
>
> The list of removals looks good to me, except Messaging.
> I remember it had some implementat
+1
> 21 авг. 2020 г., в 12:17, Nikita Amelchev написал(а):
>
> Hello, Igniters.
>
> I would add the feature that allows skipping the distributed
> metastorage entries that can not be unmarshalled [1].
> These entries can be created by the product that built on Apache
> Ignite and incorporates a
Hello, Igniters.
For now, we have dozens of the `IgniteSystemProperties` [1] that can tweak
Ignite behaviour in the very wide limits.
But, the issue, for the administrator is the following
- Documentation about existing properties can be outdated.
- The only place of the truth is the source cod
Hello, Denis.
Thanks, for the support.
The name of the parameter is the matter of discussion, of course.
I just take the JVM approach as an example.
Let’s go with the -systemProps :)
> 21 авг. 2020 г., в 18:04, Denis Magda написал(а):
>
> Nikolay,
>
> I fully support the idea as well but won
Alexey.
This option should be on the server side, so server administrator can disable
stack trace for all clients.
Correct?
> 25 авг. 2020 г., в 12:47, Alexey Goncharuk
> написал(а):
>
> Zhenya,
>
> Stacktraces are considered to be able to expose sensitive information about
> code, see [1].
Hello, Sergey!
Thanks for the proposal.
Let’s have IEP for this feature.
> 27 авг. 2020 г., в 10:25, Sergey Chugunov
> написал(а):
>
> Hello Igniters,
>
> I want to start a discussion about new supporting feature that could be
> very useful in many scenarios where persistent storage is involv
Hello, Igniters.
Not sure if I understand the essence of the proposal at the moment.
Can you, please, describe the advantages of the proposed way from the user
perspective?
How the typical DevOps pipeline should look like with this enhancement?
How I as a user can create a fully functional inst
use Maven under the hood to
> include/exclude modules.
>
> Exact commands and steps are still under discussion though. It looks like
> Petr is going to create a prototype that can be used as a starting point,
> but if you have any suggestions or ideas in the meantime, please share th
Also, guys.
Can we make one step back and add some requirements to the IEP.
How we want to install and upgrade Ignite?
What specific issues we want to solve?
With this input we can be on the same page during solution discussion.
> 29 авг. 2020 г., в 11:41, Nikolay Izhikov написа
Hello, Igniters.
JFYI
Currently, we don’t test SSL mode for Python Thin Client.
I and Andrey Kuznetsov are working on IGNITE-12718 [1] «Python Thin Client add
an ability to specify keyfile password»
To test existed SSL support and new feature I need to update «ThinClient:
Python» job [2]
I
Hello, Igniters.
Let’s include in the 2.9 release IGNITE-12718 [1]
This is a closed scope feature of the python thin client.
It was requested by some of our users.
[1]
https://github.com/apache/ignite/commit/baf8c673c41a1790ef0a244862e6abfbd4eadbf5
> 31 авг. 2020 г., в 13:25, Alexey Goncharuk
Hello, Igniters.
Alexey, please, include one more Python thin client fix [1] into the 2.9 release
It fixes kinda major issue - "Python client returns fields in wrong order since
the 2 row when fields_count>10"
[1] https://issues.apache.org/jira/browse/IGNITE-12809
[2]
https://github.com/apache/
Hello, Mikhail.
Thanks.
Done.
https://ci.ignite.apache.org/viewLog.html?buildId=5579056&tab=queuedBuildOverviewTab
> 2 сент. 2020 г., в 11:41, Mikhail Petrov написал(а):
>
> Igniters,
>
> Not all tests from the IgniteOpenCensusSuite are currently running on
> TeamCity. It seems that it due t
Hello, Taras.
It a shame we don’t have a well-written guide for the development of the Ignite
management interfaces at the moment.
For now, we have dozen of some management APIs - java, JMX, SQL, control.sh,
visorcmd.sh, REST
I think we should support 3 manage interfaces for each new command:
nt not only set/get.
> In this case we can use distributed property without publish one via simpel
> cmd line interface.
>
> On 03.09.2020 10:05, Nikolay Izhikov wrote:
>> Hello, Taras.
>>
>> It a shame we don’t have a well-written guide for the development of the
f this option.
P.S. Should we add some CMD interface for system views?
[1] https://apacheignite.readme.io/docs/system-views
> 3 сент. 2020 г., в 10:37, Nikolay Izhikov написал(а):
>
> Hello, Taras.
>
>> I guess some properties (may be future properties) shouldn't be publ
+1
> 6 сент. 2020 г., в 21:43, Saikat Maitra написал(а):
>
> Hi,
>
> I observed that the Ignite Extensions build were failing as it was
> depending on 2.9.0-SNAPSHOT and it was not available in artifactory.
>
> https://ci.ignite.apache.org/buildConfiguration/Tests_IgniteExtensions_Build/557607
Hello, Igniters.
For now, experimental commands in control.sh can be enabled only via system
property
```
$ export IGNITE_ENABLE_EXPERIMENTAL_COMMAND="true"
$ ./bin/control.sh
```
I think we should add explicit argument for this.
```
./control.sh —enable-experimental
```
WDYT?
t commands? Are these commands not production-ready? I
> never heard about it and I can't find information about experiment commands
> in the product documentation.
>
> On Mon, Sep 7, 2020 at 12:08 PM Nikolay Izhikov wrote:
>
>> Hello, Igniters.
>>
>> For
> But what is experiment commands? Are these commands not production-ready? I
> never heard about it and I can't find information about experiment commands
> in the product documentation.
>
> On Mon, Sep 7, 2020 at 12:08 PM Nikolay Izhikov wrote:
>
>> Hello, Igniter
"Philipp Masharov" :
>> I will try it. Including information about experimental commands into
>> documentation sounds like a good idea. Am I need to create a Jira ticket?
>> Definitely I need to follow some process to enhance the product
>> documentation.
>>
>&
te a Jira ticket?
>> Definitely I need to follow some process to enhance the product
>> documentation.
>>
>> On Mon, Sep 7, 2020 at 12:42 PM Nikolay Izhikov wrote:
>>
>>> Hello, Philipp.
>>>
>>> Indeed, lack of the information about ex
Philipp, at least, we have tracing and binary meta commands in the master.
Please, take a look at current Ignite sources.
> 7 сент. 2020 г., в 13:34, Nikolay Izhikov написал(а):
>
> What is wrong with that?
>
> We just improve the way user enables experimental commands.
>
to -X) should
> instead be turned into configuration/metastore settings.
> All of IGNITE_ properties which are dangerous and/or useless should be
> removed.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 21 авг. 2020 г. в 16:50, Nikolay Izhikov :
>
>> Hell
line and others in IgniteConfiguration?
> It’s confusing for the user and makes maintenance harder.
>
> I’m not necessarily arguing against this change, though. Perfect being the
> enemy of good and all that.
>
>> On 7 Sep 2020, at 13:02, Nikolay Izhikov wrote:
>>
>> Hello
y are now.
>> Let's not make it look like they're there to stay.
>> - Explicitly mention in the -X output that these flags may be
>> removed/converted to configuration properties in the future, to remove any
>> expectation of forward compatibility.
>>
>>
> We can make a compromise here: we list flags explicitly *but then, we
> decide that we don't keep backward compatibility anymore*, since the user
> of a new version can check whether their flag is still supported by using
> control.sh.
>
> WDYT?
>
> Regards,
> --
>
;m just saying that we
> can make it possible as a general principle.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 7 сент. 2020 г. в 19:01, Nikolay Izhikov :
>
>>> We can make a compromise here: we list flags explicitly *but then, we
>>>
>>&
tedProperty we can
> store some mapping separately(it
> can be static mapping or it can be stored in some new DistributedProperty).
> But in this case, it is possible to lost permission after property renaming.
>
> --
> Best regards,
> Anton Kalashnikov
>
>
>
> 0
control.(sh|bat) --tracing-configuration set (--scope
> DISCOVERY|EXCHANGE|COMMUNICATION|TX [--label] [--sampling-rate Decimal
> value between 0 and 1, where 0 means never and 1 means always. More or less
> reflects the probability of sampling specific trace.] [--included-scopes
>
Thanks, Michael!
Congrats :)
> 10 сент. 2020 г., в 19:17, Michael Pollind написал(а):
>
> With some help from @Denis Magda , we were able to
> rework micronaut-ignite and a release candidate was approved. I'm pretty
> happy with this first pass and there is a lot more that can be added but
> t
Hello, Igor.
On the other hand, dedicated `ping` operation makes our API heavier without
adding new feature -
We can do the same with the other part of the API.
Moreover, response to the ping doesn’t mean that SQL or cache query can be
served.
> 14 сент. 2020 г., в 10:08, Igor Sapego написал
Hello, Alex.
We can’t restrict dot in the cache name because it will break backward
compatibility of Ignite.
> 15 сент. 2020 г., в 16:38, Alex Kozhenkov написал(а):
>
> Yeah, that would be even better for all cases.
>
> вт, 15 сент. 2020 г. в 15:51, Ilya Kasnacheev :
>
>> Hello!
>>
>> This
Hello, Denis.
> • @Nikolay Izhikov, is there any chance you can document the new
> management commands the next week? Use me as a reviewer.
Yes.
> 18 сент. 2020 г., в 02:24, Denis Magda написал(а):
>
> Folks,
>
> While Artem is unavailable, Mauricio and I keep
gt;> However if you have an idea of how to call the feature better to let
>>>>>> the
>>>>>> user easier distinguish it from other similar features please share
>> it
>>>>>> with
>>>>>> us. Personally I
Hello, Igniters.
Currently, mtcga bot is down - 502 bad gateway error.
Can someone help with it?
https://mtcga.gridgain.com/prs.html
pacheignite-net.readme.io/docs/sql-database
>>> [10] https://apacheignite-net.readme.io/docs/calling-java-services
>>> [11] https://apacheignite-net.readme.io/docs/plugins
>>> [12] https://apacheignite-net.readme.io/docs/logging
>>>
>>> On Fri, Sep 18, 2020
nager with
> maintenance parameters? In terms of original IEP it is parameters passed
> with MaintenanceRecord.
>
> --
> Thanks!
>
> On Mon, Sep 21, 2020 at 3:20 PM Nikolay Izhikov wrote:
>
>> Hello, Sergey.
>>
>>> At the moment I'm aware about two use
Hello, Igniters.
Crawled through the WAL code and wonder - do we really need WALPointer
interface?
As far as I can see it has only one implementation FileWALPointer.
And all usages of WALPointer expect FileWALPointer.
I propose to get rid of WALPointer.
WDYT?
https://issues.apache.org/jira/browse/IGNITE-13513 - ticket created.
> 2 окт. 2020 г., в 11:53, ткаленко кирилл написал(а):
>
> Kolya, hi!
> This seems to sound good!
>
> 02.10.2020, 11:43, "Nikolay Izhikov" :
>> Hello, Igniters.
>>
>> Crawled
-1 (binding)
We missed cherry-pick IGNITE-13200 [1]
It a blocker issue.
Moreover, it pointed to the 2.9 release in Jira.
Alexey, let’s
1. Include IGNITE-13200 into release.
2. Double check that all tickets from Jira that mapped to 2.9 are cherry-picked
in 2.9 branch
https://issues.apache.org/j
em Budnikov <
>>>>>>>>>> a.budnikov.ign...@gmail.com>:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Everyone,
>>>>>>>>>>>>>
>>>>>>>>>>
+1.
Saikat, can you, please, take a look?
> 9 окт. 2020 г., в 11:54, Nikita Amelchev написал(а):
>
> Mikhail,
>
> +1 for migrate
>
> чт, 8 окт. 2020 г. в 18:34, Mikhail Petrov :
>>
>> Igniters,
>>
>> I propose to migrate spring-data modules from ignite main repository to
>> ignite-extension
release is
> processed."
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 9 окт. 2020 г. в 12:10, Nikolay Izhikov :
>
>> +1.
>>
>> Saikat, can you, please, take a look?
>>
>>> 9 окт. 2020 г., в 11:54, Nikita Amelchev
>> на
ather a few months of feedback (or lack
> thereof) then we can go on with it.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 9 окт. 2020 г. в 12:42, Nikolay Izhikov :
>
>> Ilya, we should move modules that is not related to Ignite core to
>> extension.
>
ts. Presently, the docs are "frozen"
> for the 2.9 release, but I can scratch some time and take part in the docs
> review the next week.
>
> -
> Denis
>
>
> On Fri, Oct 9, 2020 at 12:40 AM Nikolay Izhikov wrote:
>
>> Hello, Igniters.
>>
Hello, Igniters.
It seems, fails of Cache (Restarts) suite not related to my changes.
I see a lot of failed rebalance tests.
So, maybe fails related to «IGNITE-13441 Fixes for TC stabilization» changes?
Alex, can you, please, take a look.
[1]
https://github.com/apache/ignite/commit/f45c470e12
Hello, Alexey.
> Nikolay, for spring autoconfigure, did you do this manually or does maven
> allow to granularly upgrade the modules' version?
Manually.
> I thought the extensions should be tested against the latest released Ignite
> version
It seems, we should try to keep extension Ignite
Hello, Igniters.
I want to start a discussion of the new feature [1]
CDC - capture data change. The feature allows the consumer to receive online
notifications about data record changes.
It can be used in the following scenarios:
* Export data into some warehouse, full-text search, or d
om/wal-g/wal-g
>> It's a well-known tool that is already used to stream WAL for PostgreSQL,
>> MySQL, and MongoDB.
>> The advantages are integration with S3, GCP, Azure out of the box,
>> encryption, and compression.
>>
>>
>> ср, 14 окт. 2020 г.
;> WAL-G project?
>>> https://github.com/wal-g/wal-g
>>> It's a well-known tool that is already used to stream WAL for PostgreSQL,
>>> MySQL, and MongoDB.
>>> The advantages are integration with S3, GCP, Azure out of the box,
>>> encryption, and co
+1 (binding)
> 14 окт. 2020 г., в 17:07, Pavel Tupitsyn написал(а):
>
> +1 (binding)
>
> - Checked .NET binaries, examples, documentation
> - Started a mixed cluster of .NET and Java nodes
> - Compiled Ignite from sources
>
>
> On Tue, Oct 13, 2020 at 10:48 PM Denis Magda wrote:
>
>> +1 (bi
Hello, Ilya.
> all the artifacts had the version "2.9.0-SNAPSHOT" instead of "2.9.0».
Good catch!
It seems we should officially cancel the vote and rebuild RC.
Alex, can you do it, please?
> 14 окт. 2020 г., в 18:29, Ilya Kasnacheev
> написал(а):
>
> Hello!
>
> -0.9 (binding)
>
> I have t
Hello, Yaroslav.
I support the idea.
But, we should carefully work with the release scope.
IGNITE-13477 - fix for a SQL tracing that will be available only in 2.10
IGNITE-13427 - fix for a new system view that exists in master only, we need to
include IGNITE-13409
Other tickets should be checke
Hello, Ilya.
This task already solved:
1. We have system view https://apacheignite.readme.io/docs/continuous_queries
2. We have ability to output any view via
`./control.sh —system-view continuous.queries`
> 30 окт. 2020 г., в 08:52, Ilya Kazakov написал(а):
>
> Hello, Igniters!
>
> We have
Hello, Alexey.
I think it will hurt our project more than help.
Developing new features for 2 separate branches with the different APIs and
internal structure is overwhelming
Maybe we should relax a bit requirements for Ignite3?
Maybe we should move step by step and make Ignite3 with new configu
г., в 13:35, Nikolay Izhikov написал(а):
>
> Hello, Alexey.
>
> I think it will hurt our project more than help.
> Developing new features for 2 separate branches with the different APIs and
> internal structure is overwhelming
>
> Maybe we should relax a bit requirements for
n Ignite 3.0, we should gradually cease the activity
>> on Ignite 2.x to mere bugfixes because such parallel development will be
>> overwhelming regardless of how we choose to proceed.
>>
>> пн, 2 нояб. 2020 г. в 13:38, Nikolay Izhikov :
>>
>>> To be clear
r community members
>>> think.
>>>
>>> пн, 2 нояб. 2020 г. в 15:52, Pavel Tupitsyn :
>>>
>>>> 1. Rewriting from scratch is never a good idea.
>>>> We don't want to follow the path of Netscape and lose all our users
>>>> by the t
8624049226 <18624049...@163.com>
>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I suggest that the remaining document issue in version 2.9.0 can
>> be
>>>>>>> solved in version
Time works for me.
> 3 нояб. 2020 г., в 12:40, Alexey Goncharuk
> написал(а):
>
> Nikolay,
>
> I am up for the call. I will try to explain my reasoning in greater detail
> and will be glad to hear the concerns. Will this Friday, Nov 6th, work?
>
> вт, 3 нояб. 2020
Hello, Saikat.
As far as I can see you changed artifactId of the extensions not only docs.
Do we have an agreement to name each extension as «{extension-name}-ext» like
«ignite-camel-ext» or similar?
We don’t have much extensions release, so maybe it will be better to have
naming like
groupId=
+1 to make extensions as independent as possible.
Doubt if we can do it for each module.
We have, ignite-hibernate_4.2, ignite-hibernate_5.1 modules that attached to
specific hibernate version by their name.
> 11 нояб. 2020 г., в 11:19, Alexey Goncharuk
> написал(а):
>
> Hello Mikhail,
>
>
ssues which are expected to be included in 2.10 with the unknown
> status:
>
> - Distributed environment tests [2] (Nikolay Izhikov, Anton
> Vinogradov, Ivan Daschinskiy)
> Will all related issues be included in the 2.10?
>
> - Native persistence defragmentation [6][7] (Anton
cts the *process*, not the set of
> > > > > changes
> > > > > > we had discussed before. Ignite 3.0 is our unique chance to make
> > > things
> > > > > > right.
> > > > > >
> > > > > > -Val
>
big to be implemented
in any reasonable time.
> 13 нояб. 2020 г., в 10:57, Nikolay Izhikov
> написал(а):
>
> Hello, Valentin.
>
>> Nikolay, Maxim, are you OK with this route?
>
> -1 to have another repo for Ignite3 development.
>
>> 13 нояб. 2020 г., в 03:
scope to the following:
>>>>>a. Delete all deprecated API and support of obsolete internal
>>>>> protocols.
>>>>>b. Implement IEP-61 - Common Replication Infrastructure
>>>>>c. Implement new Ignite management tool ignitectl as
&
nd our users to hell of endless rewriting
> their codebases. In the latter case we'll see users to be much more
> reluctant to upgrade to newer versions.
>
> Hope this makes sense.
>
> On Mon, Nov 16, 2020 at 2:24 PM Nikolay Izhikov wrote:
>
>>> Let'
Congrats!
> 18 нояб. 2020 г., в 11:00, Nikita Amelchev написал(а):
>
> Alex,
>
> My congratulations!
>
> ср, 18 нояб. 2020 г. в 05:38, Saikat Maitra :
>>
>> Congratulations Alex!!!
>>
>> On Tue, 17 Nov 2020 at 6:26 PM, Denis Magda wrote:
>>
>>> Igniters,
>>>
>>> The Project Management Com
+1
> 18 нояб. 2020 г., в 14:38, Mikhail Petrov написал(а):
>
> Hello, Igniters.
>
> Since the migration of Ignite Spring Data modules to extensions, thin client
> support for Spring Data integration was implemented. - [1].
>
> To make this feature available for users, I propose to start the r
Hello.
I think it’s up to the release manager to decide what extension he(or she)
wants to release.
Do we have a release manager who wants to release all extensions?
> 19 нояб. 2020 г., в 10:33, Denis Magda написал(а):
>
> 11+ separate votes is an overkill. We certainly want, and agreed, to b
Hello, Alex.
Do you have a reproducer for a Page memory issues, you described?
What is consequences of that types of issues?
Can we create some «benchmark» that will measure imrpovements of page
replacement algorithm?
May be we can use ducktape branch for it?
> 20 нояб. 2020 г., в 12:05, Alex
Hello, Alex.
> Perhaps we can implement a special benchmark for this case with manually
> triggered "batch page replacement" using yardstick (but I'm not sure if
> ducktape can help here).
I think we should carefully describe the issues with the current approach and
then we can choose right to
+1 to vote for complete MVCC removal.
MVCC is a great feature but we should implement it as a first-class feature and
not «something that pretends to be working»
> 2 дек. 2020 г., в 12:53, Maxim Muzafarov написал(а):
>
> Hello Slava,
>
> I think we should vote for MVCC termination of support
ental-td45669.html
>
>
> Thanks,
> S.
>
> ср, 2 дек. 2020 г. в 13:05, Nikolay Izhikov :
>
>> +1 to vote for complete MVCC removal.
>>
>> MVCC is a great feature but we should implement it as a first-class
>> feature and not «something that pretends
ty is needed here.
>
> Anyway, I think test suites can be disabled even today, while the fate of
> the MVCC feature can be (and should be) discussed separately.
> What do you think?
>
> Thanks,
> S.
>
> ср, 2 дек. 2020 г. в 15:38, Nikolay Izhikov :
>
>> He
on TC.
> 4. Create issues with full code removal.
>
> On Wed, 2 Dec 2020 at 16:03, Petr Ivanov wrote:
>>
>> How about:
>>
>>
>> 1. Disable MVCC with some patch.
>> 2. Turn off tests.
>> 3. Plan full code removal.
>>
>> ?
>>
xecution timeouts, flaky test, etc) and I haven't seen anyone who would
> like to fix this.
> Why should we waste every contributor's time? IMHO, MVCC suites are useless
> and everyone just pushes "re-run possible blockers" button and doesn't care
> about MVCC
een anyone who would
>>> like to fix this.
>>> Why should we waste every contributor's time? IMHO, MVCC suites are
>> useless
>>> and everyone just pushes "re-run possible blockers" button and doesn't
>> care
>>> about MVCC test
:
>>
>> Hi Nikita,
>>
>> The changes in this PR looks good.
>>
>> https://github.com/apache/ignite-extensions/pull/16
>>
>> Regards,
>> Saikat
>>
>> On Mon, Jun 22, 2020 at 12:03 PM Nikolay Izhikov
>> wrote:
>>
>&
+1 for using java 11.
> 8 дек. 2020 г., в 13:18, ткаленко кирилл написал(а):
>
> +1
>
> 08.12.2020, 12:48, "Philipp Masharov" :
>> Hello!
>>
>> Andrey's arguments are solid.
>>
>> On Tue, Dec 8, 2020 at 12:23 PM Pavel Tupitsyn wrote:
>>
>>> +1, Java 11 seems to be the only right choice at
Hello, Alexey.
Think we can extend our @IgniteExperimental annotation.
`@IgniteExperimental` - mark features that are truly experimental and can be
completely removed in future releases.
`@NotRecommended` - mark features that widely adopted by the users but
implemented wrong or have known issue
Hello, Igniters.
Currently, we have a lot of usages `Future.get` without a timeout in tests.
In case the test that uses `Future.get` is flaky it can lead to the whole suite
hang.
Is there any reason to use the get method without a timeout?
Can we
a. Replace all invocation of get with the timeou
+1
> 8 дек. 2020 г., в 21:54, Valentin Kulichenko
> написал(а):
>
> +1
>
> On Tue, Dec 8, 2020 at 8:31 AM Вячеслав Коптилин
> wrote:
>
>> Hello Igniters,
>>
>> I want to start voting on removing the public API (and eventually all
>> unused parts) related to the MVCC feature.
>>
>> This top
Hello, Zhenya, Ivan.
> Hello Nikolay, if i find out introduced features structure in some project, i
> would prefer to choose different one )
Many, of the real world users disagree with you.
Please, take a look at some examples from widely used projects:
Kafka -
https://github.com/apache/kafka
; which allows keeping ignite API in better quality(I hope at least)
>
> Nikolay, maybe is it better to discuss your question on a separate topic?
> Because looks like it is a pretty discussable topic.
>
> --
> Best regards,
> Anton Kalashnikov
>
>
>
> 09.12
erformance drop due to:
>> - Transferring tracing context over the network.
>> - Using ThreadLocal for spans
>> - Converting primitives and objects to string and vice versa. (API
>> supports only String-based tags and values)
>> - Generating span objects
>>
> @
+1 (binding)
> 16 дек. 2020 г., в 13:13, Yaroslav Molochkov
> написал(а):
>
> Denis, actually, i'm mistaken, totally forgot about these:
> * Added System view for binary metadata
> * Added System view for metastorage items
> * Added RebalancingPartitionsTotal metrics
>
> On Wed, Dec 16, 2020 a
Hello, Denis.
It’s a known issue for me.
Metastore is a private API, isn’t it?
AFAICU it can occur for two reasons:
* User migrates from custom Ignite fork that has private improvements or
plugins that write to the metastore.
* We have a blocker bug and just remove some internal class that can b
the set of allowed types that can
>> be stored in the metastorage? Instead of a POJO, a Map will be accepted.
>>
>> Denis
>>
>> On 18.12.2020, 13:59, "ткаленко кирилл" wrote:
>>
>> Hello everybody!
>>
>>
Perhaps,
> we can use Nikolay's fix. Only maybe, it makes sense to remove such records
> (with all history) instead of filtering them.
>
> --
> Best regards,
> Anton Kalashnikov
>
>
>
> 22.12.2020, 14:44, "Nikolay Izhikov" :
>> Hello, Anton.
&
Hello.
> If we want to make metastore more reliable we should provide some command to
> remove keys from it.
Ticket [1] to provide this feature created.
[1] https://issues.apache.org/jira/browse/IGNITE-13901
> 22 дек. 2020 г., в 17:57, Nikolay Izhikov написал(а):
>
&g
301 - 400 of 1145 matches
Mail list logo
