+1 (binding)
> On 10 Feb 2025, at 11:00, Alex Plehanov wrote:
>
> +1
>
> Built from sources. Checked several queries on the Calcite-based SQL engine.
>
> вс, 9 февр. 2025 г. в 21:05, Nikita Amelchev :
>>
>> Dear Community,
>>
>> The release candidate is ready.
>>
>> I have uploaded release
-1 (binding).
I don’t think we can release with absent dependencies.
Let’s rebuild it and double check dependencies for calcite.
I wondering - can we guarantee somehow (with the Maven?) that all calcite
dependencies included in release?
> It affects 5 built-in functions: EXTRACTVALUE, EXTRACT,
ou please specify the particular points related to phase 0 (code
> cleanup)?
>
> - MessageFactory.
> - IgniteDataTransferObject
>
>
> What should be done with IgniteDataTransferObject and why?
>
> Thanks,
> S.
>
> пт, 29 нояб. 2024 г. в 18:35, Nikolay Izhikov
Hello, Igniters.
Rolling Upgrade are crucial missing feature for Ignite.
I propose to implement it.
RU support are complex task and require some well thought out decisions to be
made.
Please, take a look at the IEP [1] and share your feedback.
[1] https://cwiki.apache.org/confluence/display/IGN
Hello, Igniters.
Planning to work on Ignite serialization and study current codebase.
I wonder - why we use different approaches to serialize communication and
discovery messages?
- MessageWriter/MessageReader pluggable implementations for Communication SPI
- java serialization (jdk marshaller)
+1
> On 8 Nov 2024, at 08:26, Nikita Amelchev wrote:
>
> Hello, Igniters.
>
> I propose to migrate the control.sh utility to a thin client. This
> will allow us to:
>
> - Remove the legacy GridClient, which is used only for control.sh;
> - Developers will support one thin client, instead of tw
> Then I suppose the behavior you describe should be enabled/disabled by flag.
Yes. This feature will change Ignite behavior.
It will be enabled by the flag.
> How do you plan to implement this?
Sent tx state to the node performing table/index scan and combine both Btree
and tx data there.
> W
Hello, Igniters.
About decade Ignite 2.x lacks of support of transactions aware queries.
This IEP [1] is tend to fill this gap.
Any comments are welcome.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-125+Transactions+aware+queries
This will prevent scanning all the classes in classpath and allow to load
> classes from 3-rd party extensions.
>
> [1] https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html
>
>
> On Fri, Nov 26, 2021 at 12:25 PM Nikolay Izhikov
> wrote:
>
te does not support the TRUNCATE command, it is necessary to
> provide a high-performance clear table data command.
>
> 在 2022/12/2 19:13, Nikolay Izhikov 写道:
> > THanks, Slava, Stephen.
> >
> > Ticket to reimplement cache scan created -
> > https://issues.apach
we can revise visor features, which are not supported by
> > control.sh, and create an umbrella ticket for supporting in control.sh.
> > Set this ticket either as 'required' for a 'dropping visor ticket', or
> as a
> > blocker for the next release if visor dro
moving its
> implementation.
> However, do we have a list of useful features that do not exist in our
> control utility?
> Perhaps, it makes sense to reimplement such functionality and provide it
> based on control.sh script.
>
> Thanks,
> Slava.
>
> чт, 1 дек. 2022 г
PR is ready for review - https://github.com/apache/ignite/pull/10411
чт, 1 дек. 2022 г. в 16:49, Taras Ledkov :
> Hi,
>
> +1 for remove Visor related code.
> Unfortunately we have to migrate `control-utility` to use IgniteClient
> (thin client) before drop GridClient. I guess we will do it in the
Hello, Igniters.
There are legacy modules - visor-console, visor-plugins, visor-console-2.10
Looks like that modules are not evolving by community and barely used by
the Ignite users.
I propose to remove it completely.
There are IEP [1] for this
It seems that removal of visor modules allow to u
Hello, Anton.
+1 to remove outdated logging library.
But, seems, we can’t do it right now, because of existing deployments.
Let’s mark this module as deprecated and remove it in 2.14?
> Not every deployment require to be secured.
Disagree.
We should update or workaround known security issues A
Hello, Maxim.
Thanks for investigation!
> 4. log4j-test.xml, tests.properties these files from the ignite-core module
> required to run tests and it seems they should be shared between projects
> also as tests resources.
As you may see most copies of these files are empty.
I think we should mo
Great news! Congratulations!
> 10 февр. 2022 г., в 18:26, Maksim Timonin
> написал(а):
>
> Hi Pavel,
>
> Congratulations!
>
> On Thu, Feb 10, 2022 at 6:16 PM Maxim Muzafarov wrote:
>
>> The Project Management Committee (PMC) for Apache Ignite has invited
>> Pavel Pereslegin to become a comm
> will definitely not be moved to JDK more than 8th.
I think is a matter to discuss :)
Why we should stay on JDK8 forever?
> 2 февр. 2022 г., в 15:23, Petr Ivanov написал(а):
>
> Hi, Davide!
>
>
> Ignite 3 will support at least 11th JDK but that can be changed (for the
> better) on initial
Hello, Sergey.
Welcome to the Ignite community.
I’ve added you to the contributor list.
> 18 янв. 2022 г., в 14:22, Sergey Korotkov
> написал(а):
>
> Hello, All
>
> I’d like to join the community and contribute to the Ignite.
>
> Would you please grant me the contributors permissions in Jira
+1 to have compute history.
@ткаленко кирилл Lets’add both - compute task and compute job history?
> 12 янв. 2022 г., в 16:32, Zhenya Stanilovsky
> написал(а):
>
>
> Ok, thanks, now it`s clear, seems we need additional documentation here and
> also property renaming.
>
>
>
>> Judging by
+1
> 11 янв. 2022 г., в 02:38, Vladimir Steshin написал(а):
>
> +1
>
> 10.01.2022 15:52, Nikita Amelchev пишет:
>> Dear Community,
>>
>> The release candidate (2.12.0-rc2) is ready.
>>
>> I have uploaded a release candidate to:
>> https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc2/
>> h
+1 (binding)
> 20 дек. 2021 г., в 16:20, Ivan Daschinsky написал(а):
>
> +1 from me
> Checked ODBC drivers (32-bit and 64-bit) installers on Windows with running
> locally Ignite with
> pyodbc and python 3.9 using this script [1]
>
>
> [1] -- https://gist.github.com/ivandasch/6cc0b56e055b826e5
.apache.org/jira/browse/IGNITE-16101
> [2] https://issues.apache.org/jira/browse/IGNITE-16068
>
> чт, 9 дек. 2021 г. в 12:44, Nikita Amelchev :
>>
>> Hello, Nikolay.
>>
>> I have cherry-picked the issue fix.
>>
>> Thank you.
>>
>> ср,
ode characters and particularly does
> it support more characters than UTF-8 (I am not saying here that java
> String uses UTF-8)?
>
> 2021-12-13 12:56 GMT+03:00, Ivan Daschinsky :
>> UTF-8 is already a default encoding in our BinaryObject format. So.... I am
>> for unificat
Hello, Ivan.
UTF-8 can’t encode all UNICODE characters.
> 13 дек. 2021 г., в 12:49, Ivan Daschinsky написал(а):
>
> Khm, maybe a better variant is to enforce all strings to be encoded in
> UTF-8?
> AFAIK multi OS cluster is a quite common case.
>
>
> пн, 13 дек. 2021 г. в 11:36, Mikhail Petr
;> is there a chance to add this issue to the release scope? [1]
>>>>> Currently, defragmentation of certain types of indexes can corrupt them.
>>>>> Fix is straightforward and should not cause any problems.
>>>>> Thank you!
>>>>>
>>
>
>> I think no one in this topic is against removing sys-cache. The question
>> is: is it suitable for the community to deprecate using system cache in
>> 2.13 and removing it in 2.14 || 2.15?
>> Am I missing something? Am I correct?
>>
>> Thanks,
>>
and can extend the programmatic API of
>> Ignite.
>
>
> Thanks,
> S.
>
>
> сб, 4 дек. 2021 г. в 14:54, Nikolay Izhikov :
>
>> Valentin
>>
>>> plugin framework allows to implement internal components and use the
>> internal API.
>>
> depend on the system cache via the plugin framework. Let's be respectful to
> those users, provide a reasonable documented alternative and give time.
>
> -Val
>
> On Fri, Dec 3, 2021 at 8:18 AM Nikolay Izhikov wrote:
>
>> I don’t understand how it possible.
&g
cache that is available through public api for the user. This does not
> cover the case when the plugin developer wants to hide such cache and
> protect it form the end user (at least, via public api).
>
> Thanks,
> S.
>
> пт, 3 дек. 2021 г., 14:15 Nikolay Izhikov :
>
&
Vyacheslav, Val, can you please clarify - What is the issue if third-party
plugins will create «ignite-sys-cache» from the code?
Like just replacing `Ignite#cache` with the `Ignite#getOrCreateCache`.
> 2 дек. 2021 г., в 16:13, Вячеслав Коптилин
> написал(а):
>
> Hello Maxim,
>
>> I don't und
Hello, Maxim.
Thanks for the IEP.
I support the intentions and design of the IEP in general but have some
comments:
> AnnotationCommandScanner, PackageCommandScanner, URICommandScanner
Don’t think we should rely on auto scan class path capabilities.
1. How this automatic scanner will di
Hello, Andrei.
I will review your changes shortly.
> 25 нояб. 2021 г., в 14:31, Andrei Demidov
> написал(а):
>
> Hi!
>
> Could somebody please explain me.
> Should I do something for my changes to be merged?
> In contributing guide it's said that changes will be merged by any committer
> aft
, Nov 22, 2021 at 1:03 PM Mikhail Petrov
>>> wrote:
>>>
>>>> Igniters,
>>>> it seems that issues [1] and [2] that were discovered recently are
>>>> blockers for the 2.12 release.
>>>>
>>>> [1] https://issues.apache.org/
Hello.
One more tiny fix that will improve java thin client performance in certain
cases [1]
I think it worth to cherry-pick it to 2.12 release.
Any objections?
[1] https://issues.apache.org/jira/browse/IGNITE-15924
> 19 нояб. 2021 г., в 14:56, Nikita Amelchev написал(а):
>
> Vladimir, +1.
>
Hello.
> [2] https://issues.apache.org/jira/browse/IGNITE-15781
Cherry-picked to 2.12.
> 19 нояб. 2021 г., в 10:12, Pavel Tupitsyn написал(а):
>
> I'd like to add this simple fix as well [1]
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15954
>
> On Fri, Nov 19, 2021 at 9:50 AM Maksim
Hello, Andrei.
Welcome to the Apache Ignite community.
I’ve added you to the Contributors list.
You can assign JIRA to yourself.
> 15 нояб. 2021 г., в 15:26, Andrei Demidov
> написал(а):
>
> Hello Ignite Community!
>
> My name is Andrei. I want to contribute to Apache Ignite and want to star
ya Kasnacheev
>
>
> ср, 19 мая 2021 г. в 14:23, Nikolay Izhikov :
>
> > Ilya.
> >
> > Actually, current behaviour described even in documentation [1]
> >
> >
> > > Note that not all objects are converted to the binary object format.
> The
>
+1 (binding)
> 1 нояб. 2021 г., в 17:41, Denis Magda написал(а):
>
> +1 (binding)
>
> Support to release the integration and then bring in essential automation
> for testing.
>
> -
> Denis
>
>
> On Wed, Oct 27, 2021 at 4:48 AM Nikita Amelchev
> wrote:
>
>> Dear Ignite Community,
>>
>> I h
- https://github.com/apache/ignite/pull/9515
3. CacheConfiguration#rebalanceDelay
- https://issues.apache.org/jira/browse/IGNITE-15764
- https://github.com/apache/ignite/pull/9515
Please, review.
> 15 окт. 2021 г., в 16:23, Nikolay Izhikov написал(а):
>
> THanks, Maksim.
>
Hello.
In the scope of IEP-80 Breaking changes in Ignite-2.x PR for the following API
are prepared:
1. MVCC
- https://issues.apache.org/jira/browse/IGNITE-15757
- https://github.com/apache/ignite/pull/9516
2. LOCAL caches
- https://issues.apache.org/jira/browse/IGNITE-15756
Hello, Igniters.
As you may know, recently, Sberbank sponsored servers capacity to setup new
instance of Team City [1] to run Ignite tests.
Right now, ci2 is fully ready for daily usage.
We have exported and prepared Kotlin scripts [2] to keep TC settings as a code
[3].
I think we should adju
;>>>>
>>>>> I support #2, because we already have the ServiceContext. Having
>>>>> both ServiceContext and @ServiceRequestContextResource that injects
>> some
>>>>> function (or any other mechanism for that matter) will be VERY
>&
>:
>>>
>>>> Ivan,
>>>>
>>>> I'm a bit confused :) Unless I misread the initial suggestion, the
>> idea is
>>>> to provide a public API to create the context. In other words, it will
>> be
>>>> up to the end us
ps://issues.apache.org/jira/browse/IGNITE-14613
>
> On Fri, 15 Oct 2021 at 15:46, Anton Vinogradov wrote:
>>
>> +1
>>
>> On Fri, Oct 15, 2021 at 3:41 PM Nikita Amelchev
>> wrote:
>>
>>> +1 for deprecation in the 2.12 release
>
Hello, Igniters.
I’ve prepared IEP-80 [1] to track breaking changes that should be done in
Ignite 2.x.
We agreed on the following algorithm to deal with breaking changes:
- Ignite 2.[x] - deprecate the API + notification of the users.
- Ignite 2.[x+1] - API removal.
I propose to start
Maxim.
> Currently, they are copied from the optional
> directory of the ignite binary package but would be copied from an
> appropriate ignite extension binary package.
But how, the user will download this binary package?
Right now, all the user need is Ignite distributive.
> 13 окт. 2021 г.,
+1 to have service proxy context.
> 11 окт. 2021 г., в 09:43, Ivan Daschinsky написал(а):
>
> Val, Pavel both of you are right, but on the other hand there are some
> other tasks
>
> 1. Distributed tracing.
> 2. Custom metrics/measurements
> 3. Auth and some related tasks (i.e. ingests full Use
+1
> 5 окт. 2021 г., в 11:48, Nikita Amelchev написал(а):
>
> Folks, we should release the spring-data-commons module with the 1.1.0
> version to release spring-tx, spring-cache modules.
> It contains some proxies required for the new modules.
>
> I suggest:
>
> 1. Release the spring-data-comm
s related to Maven build? possible Gradle upgrade?
> — issues related to run scripts?
> — issues related to release and delivery processes and scripts?
>
> Are they going to be addressed during Apache Ignite evolution too?
>
>> On 29 Sep 2021, at 13:47, Nikolay Izhikov w
gt;>> shared the codebase.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> For the same reason, a bug filed for 2.x can't be just
>>>>>> transitioned
>>> versions of the same product, because, as you correctly
>>>> mentioned,
>>>>>>>>>>>> they
>>>>>>>>>>>> target "same users, community, use cases". At the same time,
>> they
>>>>
+1 (binding)
> 15 сент. 2021 г., в 12:24, Alex Plehanov написал(а):
>
> +1
>
> Checked sha512 and sign of archives, built from sources, started a cluster
> with a few nodes.
>
> вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn :
>
>> Ilya,
>>
>>> I'm still confused by this publish/ directory. Wh
+1
> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn написал(а):
>
> -1
>
> This may become an obstacle for some of the users and I'm not sure how it
> improves anything.
>
>> 3. Sometimes even maintainers forget to add test sources to VS projects
> [1]
> We can add an automatic check for this (in f
I proposed the following plan:
1. 2.12 - deprecation of LOCAL caches.
2. 2.13 - complete removal LOCAL caches from codebase.
> 13 сент. 2021 г., в 13:30, Ivan Daschinsky написал(а):
>
> I personally support deprecation, but we should at least have a plan.
> I suppose that putting annotations a
+1 to release ASAP.
> 9 сент. 2021 г., в 13:43, Ivan Daschinsky написал(а):
>
> TC build of release branch --
> https://tc.sbt-ignite-dev.ru/buildConfiguration/IgniteThinClients_Tests_ThinClientPython/6130289
>
> чт, 9 сент. 2021 г. в 13:40, Ivan Daschinsky :
>
>> Hi, folks.
>>
>> Unfortunate
+1 to ban Streams usage.
> 9 сент. 2021 г., в 02:59, Valentin Kulichenko
> написал(а):
>
> Pavel,
>
> Quite frankly, I think we used to lean into performance too much. We
> generally preferred it over data consistency, project modularity and code
> readability. Performance, of course, plays
Atri.
Right now code can’t be tested because it doesn’t compile.
> 3 сент. 2021 г., в 17:42, Atri Sharma написал(а):
>
> I am not sure why is it can be tested by few members?
>
> Anyone with azure account should be able to test it
>
> On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, wrote:
>
>> F
+1 (binding)
> 26 июля 2021 г., в 21:11, Pavel Tupitsyn написал(а):
>
> +1
>
> On Mon, Jul 26, 2021 at 11:36 AM Igor Sapego wrote:
>
>> +1 from me
>>
>> Best Regards,
>> Igor
>>
>>
>> On Fri, Jul 23, 2021 at 3:32 PM Ivan Daschinsky
>> wrote:
>>
>>> +1 From me
>>> 1. Checked binary packag
Hello, Igniters.
We have many beautiful images [1] in documentation.
I want to create images that have similar style with other to keep docs
consistent.
Do we have some guides or styles I can use?
[1] https://ignite.apache.org/docs/2.10.0/images/ignite_clustering.png
+1 (binding)
> 1 июля 2021 г., в 08:35, Petrov Mikhail написал(а):
>
> +1
>
> Checked on Ubuntu 20.04. Created separate Spring Applications for each
> version of Spring Data Integrations using the Maven RC repository and
> following the documentation. Tested common use cases. Checked archive
+1 (binding)
> 1 июля 2021 г., в 09:29, Petrov Mikhail написал(а):
>
> +1
>
> Checked on Ubuntu 20.04. Checked built-report and print-statistics scripts
> for the custom Ignite application. Checked archive signs. Built from the
> sources.
>
> On 01.07.2021 00:24, Sergei Ryzhov wrote:
>> +1
>
Hello.
As one of the authors of PR fully support merge of this module.
Have plans to use it during development of other features.
Guys, please, share your feedback.
Do we need to improve something prior merge?
> 24 июня 2021 г., в 14:41, Denis Magda написал(а):
>
> Anyway, it's much more comm
es like that
>>> -- common sense is required.
>>>
>>> Also, in general, the impression I get from your PR is that the code
>>> becomes less readable. So many abbreviations simply make it look cryptic
>>> and weird -- this might easily confuse a newcomer. A
;>> aware of any exceptions.
>>>
>>> In this PR there are 5 classes which licenses with AL 2.0, but IP owner is
>>> 3rd party company.
>>>
>>> I'm a bit concerned about having such code in the project. I'd rather
>>> reverted
Hello, Igniters.
Recently huge commit was merged [1].
Taras, Alexander, can you, please, explain what is purpose of the commit?
What feature it implemented?
Looked inside the ticket and found no explanation.
Description is "Add statistics collection and usage.»
Do we have plans to document this
the transactions or PME codebase. It's darkness and
>> no
>>> abbreviations for "consistency" will help to understand that code.
>>>
>>>>> and attract new members
>>> Who can tell me at least 5 contributors with 10+ commits who are not
+1 (binding)
> 18 июня 2021 г., в 14:41, Shishkov Ilya написал(а):
>
>> in-memory cluster 3x servers
>
> I forgot to write about the Ignite version: checked with Ignite-2.10 binary
> release.
>
> пт, 18 июн. 2021 г. в 14:37, Shishkov Ilya :
>
>> +1 from me.
>>
>> Checked on Win10:
>> - Pytho
ew comments like "use future
>>>>>>> instead of fut". So my proposal is to change rule from "required" to
>>>>>>> "recommended".
>>>>>>>
>>>>>>> On Wed, Jun 16, 2021 at 2:49 PM Valentin Kulichenko
>>
+1
> 9 июня 2021 г., в 09:48, Ivan Daschinsky написал(а):
>
> Hi, folks!
>
> I suppose, that it's time to release the next version of python thin
> client, because we are ready to ship new cool features.
>
> 1. Expiry policy (TTL) support (merged to master) [1]
> 2. Transactions (patch availab
;>
>>> I also support removing this requirement. It’s not the first time someone
>>> brings this up, and so far we haven’t been able to fix it. Not worth it
>> in
>>> my view.
>>>
>>> -Val
>>>
>>> On Sat, Jun 5, 2021 at 11
like a waste of time. freq or frequency, cnt or count, it is fine
>> either way.
>>
>> On Fri, Jun 4, 2021 at 7:39 PM Nikolay Izhikov wrote:
>>
>>> Hello, Igniters.
>>>
>>> Right now, we have the rule to use some predefined list of
Hello, Igniters.
Right now, we have the rule to use some predefined list of abbrevation for
variable names [1].
Some of the reviewers ask to follow this rule strictly.
> It is required to use abbreviated form for code consistency.
I tried to implement this rule in form of checkstyle check [2] a
totally OK to start returning the "better" ConcreteType[] instead.
>
> I think you can just fix the bug while preserving accessibility of old
> (pre-bugfix) data as it was pre-2.11.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 19 мая 2021 г. в 14:08, Nikolay I
get()
> This way we may not even need any changes to storage format, if binary
> marshaller does not mind.
>
> Regards,
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 19 мая 2021 г. в 13:33, Nikolay Izhikov :
>
>> Igniters.
>>
>> Just to clari
put(1, new TestClass1[] {new TestClass1(), new TestClass1()});
TestClass1[] obj = cache.get(1); //This will fail with
ClassCastException.
assertEquals(TestClass1[].class, obj.getClass());
}
}
```
> 19 мая 2021 г., в 13:04, Nikolay Izhikov написал(а):
>
> Thanks, Ilya.
&g
t; Ilya Kasnacheev
>
>
> ср, 19 мая 2021 г. в 12:56, Nikolay Izhikov :
>
>> Hello,
>>
>>> However, for internal platform and services implementations we should
>> fix the root cause:
>>> avoid extra deserialization->serialization pass completely.
r, it does seem questionable where we have a new wrapper class
> specifically for top level arrays. You can have this wrapper in your own
> client code and it should work OK.
>
> Bottom line, if we are to break compatibility, I would like to see it done
> for some really common pa
ose as java )
>>>> +1 for 140
>>>>
>>>>> Hi!
>>>>> Personally, I suppose that 120 chars per line is OK. Moreover, many
>>>>> codestyles suggests less chars per line.
>>>>> For example PEP8 recomm
munity members think.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 30 апр. 2021 г. в 17:16, Nikolay Izhikov :
>
>> Igniters,
>>
>> Want to clarify my proposal about new array store format.
>> I think we should store array in special binary
;
/** Raw data. */
private String compClsName;
/** Value. */
private Object[] arr;
// Further implementation.
}
```
> 30 апр. 2021 г., в 16:31, Nikolay Izhikov написал(а):
>
> Hello, Igniters.
>
> Currently, binary marshaller works as follows(Say, we hav
Hello, Igniters.
Currently, binary marshaller works as follows(Say, we have a class `User` then):
IgniteBinary#toBinary(User)` -> BinaryObject
IgniteBinary#toBinary(User[])` -> Object[]
IgniteBinary#toBinary(Object[])` -> Object[]
This means, that we lose array component type information during
Nikolay Izhikov created IGNITE-14592:
Summary: Incapsulate config modification logic into callback
Key: IGNITE-14592
URL: https://issues.apache.org/jira/browse/IGNITE-14592
Project: Ignite
Nikolay Izhikov created IGNITE-14585:
Summary: Ability to extend config files in spec
Key: IGNITE-14585
URL: https://issues.apache.org/jira/browse/IGNITE-14585
Project: Ignite
Issue Type
yle insists on 100.
>>
>> More than 120 chars is too long as for me and is not convenient for 3-way
>> merges.
>>
>> чт, 15 апр. 2021 г. в 12:28, Nikolay Izhikov :
>>
>>> Hello, Ilya.
>>>
>>> Thanks for the feedback.
>>>
>>
-
> Ilya Kasnacheev
>
>
> чт, 15 апр. 2021 г. в 11:30, Nikolay Izhikov :
> Hello, Igniters.
>
> Right now, we have a code style rule [1] - the line should fit in 120
> characters.
> But, this rule violated in many and many places through code.
> I have a plan t
Hello, Igniters.
Right now, we have a code style rule [1] - the line should fit in 120
characters.
But, this rule violated in many and many places through code.
I have a plan to add a check style rule to force maximum line length.
For me, personally, 120 characters a bit old-fashioned restrictio
Congrats! Well deserved.
> 13 апр. 2021 г., в 09:34, Zhenya Stanilovsky
> написал(а):
>
>
> Big deal ! Ivan, ignite it !)
>
>
>
>> The Project Management Committee (PMC) for Apache Ignite has invited
>> Ivan Daschinsky to become a committer and we are pleased to announce that
>> he has ac
Nikolay Izhikov created IGNITE-14516:
Summary: WAL can continue to log into archived segment if auto
rollover enabled
Key: IGNITE-14516
URL: https://issues.apache.org/jira/browse/IGNITE-14516
Nikolay Izhikov created IGNITE-14464:
Summary: Remove released version of Ignite from regular ducktests
Key: IGNITE-14464
URL: https://issues.apache.org/jira/browse/IGNITE-14464
Project: Ignite
Nikolay Izhikov created IGNITE-14463:
Summary: Support check Ignite-based products with ducktests
Key: IGNITE-14463
URL: https://issues.apache.org/jira/browse/IGNITE-14463
Project: Ignite
Nikolay Izhikov created IGNITE-14450:
Summary: Add Maximum CDC directory size configuration parameter
Key: IGNITE-14450
URL: https://issues.apache.org/jira/browse/IGNITE-14450
Project: Ignite
Nikolay Izhikov created IGNITE-14449:
Summary: Add binary meta change event to CDCCosumer
Key: IGNITE-14449
URL: https://issues.apache.org/jira/browse/IGNITE-14449
Project: Ignite
Issue
Nikolay Izhikov created IGNITE-14435:
Summary: Refactor PdsConsistentIdProcessor for reusage
Key: IGNITE-14435
URL: https://issues.apache.org/jira/browse/IGNITE-14435
Project: Ignite
Hello, Mikhail.
I'm +1 to follow your suggestion.
чт, 18 мар. 2021 г. в 17:53, Mikhail Petrov :
> Hello, Igniters.
>
> As of now, there are two independent APIs related to security:
> 1. IgniteSecurity - handle node/client authentication and authorize all
> operations.
> 2. IgniteAuthenticationP
Nikolay Izhikov created IGNITE-14368:
Summary: System view for DataStructures
Key: IGNITE-14368
URL: https://issues.apache.org/jira/browse/IGNITE-14368
Project: Ignite
Issue Type
Nikolay Izhikov created IGNITE-14367:
Summary: WAL reader. Read only specific Record Types
Key: IGNITE-14367
URL: https://issues.apache.org/jira/browse/IGNITE-14367
Project: Ignite
Issue
Nikolay Izhikov created IGNITE-14366:
Summary: Support separate JVM options for ignite-cdc.sh and
ignite.sh
Key: IGNITE-14366
URL: https://issues.apache.org/jira/browse/IGNITE-14366
Project
Nikolay Izhikov created IGNITE-14365:
Summary: CDC Documentation
Key: IGNITE-14365
URL: https://issues.apache.org/jira/browse/IGNITE-14365
Project: Ignite
Issue Type: Improvement
Nikolay Izhikov created IGNITE-14364:
Summary: Extension to write CDC data to other Ignite cluster
Key: IGNITE-14364
URL: https://issues.apache.org/jira/browse/IGNITE-14364
Project: Ignite
1 - 100 of 1145 matches
Mail list logo
