Welcome, Alexander !
Hi Alexander,
I've added you to the list of contributors. Now you can assign an issue
to
yourself.
Should you have any question, please do not hesitate to ask.
Welcome to the Apache Ignite Community!
Sincerely,
Dmitriy Pavlov
Couple links that can help you to onboard
+1 for all proposals.
+1, already make it by filers.
This was discussed already [1].
So, I want to complete this discussion with moving outside dev-list
GitHub-notification to dedicated list.
Please start voting.
+1 - to accept this change.
0 - you don't care.
-1 - to decline this change.
This vote will go for 72
Igniters, i found that ignite allow to create multiple case sensitive
indexes with equal fields collection, i.e. no exception and warn here:
CREATE INDEX \"title_idx\" ON books (title);
CREATE INDEX \"tiTLE_IDX\" ON books (title);
1. in this case will be created two different index structures.
Looks like this issue would be linked too.
https://issues.apache.org/jira/browse/IGNITE-5602
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
I think it would break backward compatibility, as Nikolay mentioned above
we would take exception here:
[1]
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/file/FilePageStore.java#L372
thats why i question for c
+1
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Kirill, is it good practice to have a metrics for internal use? Don`t think so.
+1 witk Nikolay size is more readable than abstract segments count.
>Hi, Nikolay!
>
>For internal use, leave the metric that I propose and also add the metric:
>Count of bytes logged in WAL. Why not "written" becau
I fill the ticket with drop problem, plz take a look [1]
[1] https://issues.apache.org/jira/browse/IGNITE-14205
>Ilya,
>
>Thanks!
>I've added this step to the Release Process wiki page also [1].
>
>[1]
>https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2I
Build from sources, run .net tests, looks good. +1
>+1 (binding)
>
>Downloaded binary packages, started nodes, .NET examples, .NET nodes.
>Downloaded source package, built Java and .NET parts.
>
>On Thu, Mar 11, 2021 at 4:24 AM Maxim Muzafarov < mmu...@apache.org > wrote:
>
>> Dear Communit
hi jjimeno, plz check your throughput once more by using
OPTIMISTIC, SERIALIZABLE options, hope it would be more faster than default.
>
>
>--- Forwarded message ---
>From: jjimeno < jjim...@omp.com >
>To: u...@ignite.apache.org
>Cc:
>Subject: Long transaction suspended
>Date: Thu, 04
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 accepted.
>
>Ivan made a lot of contributions to Apache Ignite.
>He helped a lot to improve our Python Thin Cl
Python is not so verbose 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 recommends 80 (but we use 120 in pyignite and flake8
>codestyle checks it). Google java codestyle insists on 100.
>
hello, can you try OPTIMISTIC SERILIZABLE tx`s ?
>Hello all,
>
>For our project we need a distributed database with transactional support,
>and Ignite is one of the options we are testing.
>
>Scalability is one of our must have, so we created an Ignite Kubernetes
>cluster in Azure to test it,
hello, can you recheck with OPTIMISTIC SERILIZABLE tx`s ?
>Hello all,
>
>For our project we need a distributed database with transactional support,
>and Ignite is one of the options we are testing.
>
>Scalability is one of our must have, so we created an Ignite Kubernetes
>cluster in Azure to
Igniters, i found some problems with running p2p tasks concurrently.
Description and patch available here, can someone review plz?
[1] https://issues.apache.org/jira/browse/IGNITE-14131
Ivan, if Petr can`t help here, how can we change it out own ?
May be we need some help from pmc chair or someone else ?
>
>>
>>Igniters. Almost half of a year passed since this thread begun. We
>>released 0.4.0, we adopted travis-ci and use it as primary source for
>>test results but nothing
Igniters, as previously was found [1] in some cases transactional cache can
contain unexpected data after node crash and further recovery. Short
explanation: it`s all due to ignite does not save transactional records into
the WAL.
The simplest example: 1 node cluster and transactional cache, if
Hi ! I found that very important issue [1] (already in master) is not planned
to be in 2.11, may be it still possible to take it into scope ?
thanks !
[1] https://issues.apache.org/jira/browse/IGNITE-14739
>Hi Folks,
>
>Branch divergence has been completed. Sorry for the delay, it was my f
+1 for reverting, can anybody (possibly ticket starter?) explain how jvm
settings will rise some security problems ?
>I suppose, that we should revert this particular line. I don't understand
>who ever considers vm options as sensitive info.
>
>ср, 30 июн. 2021 г., 22:52 Shishkov Ilya < shish
-1 for extra arg, +1 for Ivan`s upper proposal : @IgniteSystemProperty
annotation.
Look, someone will set some of IGNITE_* option and after possibly cluster
problems will give this logs into analysis and engineer can`t reproduce such a
case, cause no param is applied.
>An extra argument for I
Igniters, i understand that this is very long and fundamental story. but …
still want to rise up this discussion, we have 2 very strange inspections:
* «public» modifier in interface methods.
* Illegal ‘{}’ for one line statement. — i found it harmful.
I don`t want to link additional discussion
Guys, thank you very much !!
>Zhenya,
>
>Congrats!
>
>--
>Regards,
>Konstantin Orlov
>
>
>
>
>> On 30 Jul 2021, at 12:20, Вячеслав Коптилин < slava.kopti...@gmail.com >
>> wrote:
>>
>> Hooray!
>>
>> Congrats! May t
Andrey, seems we can use [1] it help us with point 1 in your comment, isn`t it ?
[1]
https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
>-1
>It is sad to say -1, as Guava has very useful stuff and it looks easier to
>add it as a dependency r
alexpolovtcev please clarify what do you mean under : «possibility of using
Guava in Ignite 3», using how necessary dependency of calcite or using like
«using in our code» ? If using in code, i -1 here.
thanks.
>Hello, dear Igniters!
>
>I would like to discuss the possibility of using Guava
jar hell here?
>Zhenya,
>
>My intentions are the following:
>
>1. Remove some copy-pasted code (like the "bytecode" module or some utility
>methods). Please see my original message for the links to the code.
>2. Explicitly pin the Guava version to avoid conflicts in
>> > > >
>> > > > On Fri, Aug 20, 2021 at 7:37 PM Alexander Polovtcev
>> > > > < alexpolovt...@gmail.com > wrote:
>> > > > >
>> > > > > Guys,
>> > > > >
>> > > > > Thanks again
Aleksandr, thanks for this activity.
-1 from my side, all my decisions are in linked discussion.
>Dear Igniters,
>
>In this thread
><
>https://lists.apache.org/thread.html/r4120a03a2bf32098e54e21ae02e509b0d68f413bc7cc1f8f6d85c93d%40%3Cdev.ignite.apache.org%3E
> >
>we've been discussing the prob
Pavel, thanks !
And what about stream usage not in a hot path ? I.e. create\drop table
operation, may be such a cases will leave for committer\contributor
consideration ?
>Igniters,
>
>Java streams are known to be slower and cause more GC pressure than an
>equivalent loop.
>Below is a simple f
Thanks Maxim !
I tries to compare this ver with 2.10 (some performance tests with persistence
and transactional\atomic payload) and seems all ok there.
+1 from me.
>
>
>Dear Community,
>
>
>The release candidate for the 2.11 version is ready.
>
>
>I have uploaded a release candidate to:
>https
I just dream up ) If some one have cached web session layer over ignite with
sticky cookie [1] and cross cache transaction logic through local and global
caches how this schema will transform without local ?
[1]
https://www.imperva.com/learn/availability/sticky-session-persistence-and-cookie
Ok, we can use node filters in such a case, i understand )
>I just dream up ) If some one have cached web session layer over
>ignite with sticky cookie [1] and cross cache transaction logic through
>local and global caches how this schema will transform without local ?
>
>[1]
>https://www.im
completely support !
>Igniters!
>
>Currently we have CMake build system, that works on Windows, Linux and
>MacOs flawlessly
>
>1. CMake is supported natively in VS 2019
>2. CMake can generate VS projects for about 20 years flawlessly.
>3. Sometimes even maintainers forget to add test sources to
Sergey, not so easy to recognize the problem, also with logs, plz fill the
ticket and append link to this message or duplicate all logs there.
thanks !
>From: "Sergey Korotkov" < serge.korot...@gmail.com >
>To: u...@ignite.apache.org
>Cc:
>Subject: [2.11.0]: 'B+Tree is corrupted' exception
Big deal, congrats Maxim !
>Igniters,
>
>The Project Management Committee (PMC) for Apache Ignite has invited Maxim
>Timonin to become a committer and we are pleased to announce that he has
>accepted.
>
>Maxim makes valuable contributions to the Apache Ignite code, helps
>actively to applicati
Wellcome Semyon !
Andrey what`s Ivan are you talking at the end of the message or this is some
kind of phraseologism that all russians are ivans ?:)
>Igniters,
>
>The Apache Ignite Project Management Committee (PMC) has invited
>Semyon Danilov to become a new committer and are happy to announce
+1 with Ivan, let`s store it in core product just because it looks like
inalienable functionality and release cycle of extensions a little bit
different.
>Anton, I disagree.
>
>1. This should be released with main distro.
>2. This should not be abandoned.
>3. There is not any release proces
Alex, great !
If someone wants to touch codebase somehow plz use this branch [1]
Test passed can be found here [2] [3]
[1] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite
[2]
https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/java/org/apache/ignite/in
Hi, seems ignite already contain such view [1], plz explain the difference?
thanks.
[1] https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#tasks
>
>>
>>>Hello everyone!
>>>
>>>I want to add a new system view to get the last N (configurable by system
>>>property, default
Ok, whats the purpose of END_TIME property in such a case?
>Thanks Zhenya, but here we can see only the current working tasks, after they
>are completed it is not possible to get the actual time of work, for example,
>for statistics.
Ok, thanks, now it`s clear, seems we need additional documentation here and
also property renaming.
>Judging by the code, this is the task session timeout.
Petr, how can you explain the lifecycle of product ? It managed by community.
I`m +1 for moving forward.
>
>>
>>>Adding ability to compile Ignite 2 with JDK11+ will require so much
>>>refactoring and, sometimes, rethinking of approaches, that it will become
>>>different project in some ways
Maxim, i think that more frequent releases are useful.
Ready to release branch means that it passed all known tests and also have an
appropriate votes.
More code changes creates more difficulties in final tests and sometimes
migration.
No need to switch between neighbor minor versions for user i
Ivan, thanks for this effort, as for me - looks good.
>Hi everyone,
>
>I'd like to continue the discussion. I created IEP with the attempt to
>summarize
>all the information above, you can find it here [1]. What do you think?
>
>[1]
>https://cwiki.apache.org/confluence/display/IGNITE/IEP-84%3A
x27;s discussable.
>> >
>> > But the 2.12 branch was cut on October 15, 2021. There are many fixes
>> > and features that were merged into the master during this period. The
>> > total time between branches cut is 5 months (if there is no delay
>> > happe
Nikita, thanks ! I found that below link is unavailable:
>TC [2] Compare w/ Previous Release
>https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6398741
>
Nikita thanks for your effort !
Download sources, run examples.
+1 from me.
>Dear Community,
>
>The release candidate is ready.
>
>I have uploaded a release candidate to:
>https://dist.apache.org/repos/dist/dev/ignite/2.13.0-rc2/
>https://dist.apache.org/repos/dist/dev/ignite/packages_2.13.0-rc2
Igniters, i found that new release of apache calcite was released (1.31) [1].
This release contains great improvement [2] which makes possible to resolve
[3], but also contains a bug [4] with natural join validation (possibly not
one, but apache ignite sql test suite highlight only this one).
Join the congratulations !
>Hi Igniters!
>
>The Project Management Committee (PMC) for Apache Ignite has invited
>Ivan Daschinsky to become a member of the PMC and we are pleased to
>announce that he has accepted.
>
>Ivan contributed the Ignite Python thin client. And he is still maintaining
l.com >:
>>
>> > I suppose that we are not in rush, because we have just cut off a release
>> > branch for 2.14. Let us wait for a new release of Calcite. By the way,
>> has
>> > that bug been already reported?
>> >
>> > вт, 30 авг. 2022 г.,
I think it`s important to mention that local caches are not supported since
this version [1].
[1] https://issues.apache.org/jira/browse/IGNITE-15759
>Dear Community,
>
>The release candidate is ready.
>
>I have uploaded release candidate to
>https://dist.apache.org/repos/dist/dev/ignite/
+1, thanks Ivan !
>Dear Igniters!
>
>Release candidate binaries for subj are uploaded and ready for vote
>You can find them here:
>https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.0.rc1
>
>If you follow the link above, you will find source packages (*.zip)
>and binary packages (wheel
+1 for remove.
>+1 This module seems to be completely abandoned
>
>чт, 1 дек. 2022 г., 00:46 Ilya Kasnacheev < ilya.kasnach...@gmail.com >:
>
>> Hello!
>>
>> Let's go ahead and remove what we don't use. Most of that stuff is deep
>> legacy, even if it contains some rare gems of functionality
+1 for Nikolay Izhikov.
>Среда, 30 октября 2019, 15:16 +03:00 от Alexey Zinoviev
>:
>
>+1 Dmitry Pavlov
>
>ср, 30 окт. 2019 г. в 13:50, Nikolay Izhikov < nizhi...@apache.org >:
>
>> +1 for Nikolay Izhikov (binding)
>>
>> В Вт, 29/10/2019 в 20:13 +0300, Pavel Tupitsyn пишет:
>> > +1 for Dmit
Ilya Kasnacheev, what a problem in Solr with Ignite functionality ?
thanks !
>Вторник, 26 ноября 2019, 13:50 +03:00 от Ilya Kasnacheev
>:
>
>Hello!
>
>I have a hunch that we are trying to build Apache Solr (or Solr Cloud) into
>Apache Ignite. I think that's a lot of effort that is not very
>can't match that.
>
>Maybe we could integrate with Solr/Solr Cloud instead, by feeding our cache
>information into their storage for indexing and relying on their own
>mechanisms for distributed IR sorting?
>
>Regards,
>--
>Ilya Kasnacheev
>
>
>
Roman just as fast remark, Phoenix builds their approach on already existing
monolith HBase architecture, most cases it`s just a stub for someone who wants
use secondary indexes with a base with no native support of it. Don`t think
it`s good idea here.
>
>
>--- Forwarded message ---
Big deal and huge responsibility.
Congrats Aleksei!
Hello Ignite Community,
The Project Management Committee (PMC) for Apache Ignite has invited
Aleksei Scherbakov to become a committer and we are pleased to announce
that he has accepted.
Aleksei investigated and fixed a lot of critical issue
Folks,
The issue [1] already in master, submit minor fix with performance enhancements.
i think it`s not risky to gather it too.
thanks!
[1] https://issues.apache.org/jira/browse/IGNITE-12442
>Пятница, 20 декабря 2019, 16:09 +03:00 от Maxim Muzafarov :
>
>Folks,
>
>The issue [1] has pinned
>> Is it become slower or faster?
>
>Very correct question! User saw "cache put time" metric becomes x2
>bigger. Does it become slower or faster? Or we just put into the cache
>values that 4x bigger in size? Or all time before we put values
>locally and now we put values on remote nodes. Or our op
Igniters, i`l try to compare 2.8 release candidate vs 2.7.6,
last sha 2.8 was build from : 9d114f3137f92aebc2562a
i use yardstick benchmarks, 4 bare machine with: 2x Xeon X5570 96Gb 512GB SSD
2048GB HDD 10GB/s
1 for client (driver) and 3 for servers.
this mappings for graphs and real yardstick
+1 here.
>Hi, All!
>
>I think that the best way is to do the following:
>1. Move controls.sh to separate module (this will allow us to use any third
>party libs for argument parsing, interactive mode, and other stuff).
>2. Move all colde from visorcmd to controls.sh
>3. Drop visorcmd
>
>On Thu,
load:1.3.2:*:*:*:*:*:*:*) :
>>>>>> CVE-2016-131
>>>>>>>>
>>>>>>
>>> storm-core-1.1.1.jar/META-INF/maven/org.apache.hadoop/hadoop-auth/pom.xml
>>>>>>>> (pkg:maven/org.apache.hadoop/hadoop-auth@2.6.1
hould not forget about thin client changes, since it will be strange if we
>> introduce some methods to thin client API and protocol and in the same
>> Ignite version deprecate these methods for servers and thick clients.
>>
>> [1]: https://issues.apache.org/jira/browse/IG
Maxim, performance fix issue [1] already in master, if no objections, can u
merge it into 2.8 ? Thanks !
[1] https://issues.apache.org/jira/browse/IGNITE-12547
>Igniters,
>
>
>Here is the actual list of BLOCKER release issues:
>
>IGNITE-12456 Cluster Data Store grid gets Corrupted for Load test
Looks like i found problem root cause, first run completed on TC, hope it would
be ok with other builds.
>
>
>--- Forwarded message ---
>From: "Ivan Pavlukhin" < vololo...@gmail.com >
>To: dev < dev@ignite.apache.org >
>Cc:
>Subject: Re: Cache 6 suite is broken
>Date: Fri, 20 Dec 2019
Igniters, i found that suggesting zero backup for performance improvements
sounds like malicious and further problems suggestion. May be it`s time to
remove it ?
Example:
[07:59:27] Performance suggestions for grid (fix if possible)
[07:59:27] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_D
-1, sounds confusing, i wan`t use deprecated API and @IgniteExperimental it`s
something unknown with undefined «time for support».
>Dear Apache Ignite community,
>
>We would like to conduct a formal vote on the subject of whether to allow
>or prohibit a joint existence of @deprecated annotati
I know guys who use this setting (may be erroneously) = MAX_INT for real
rebalance delaying (very small sla) grid without persistence. But i don`t know
further algo, may be if backup nodes become extremely small they creates the
same cluster near it. Can ignite simple disable rebalance?
>F
>>> Classification: Public
>>>
>>> Hi, Alexey.
>>> I believe it can't be done until in-memory caches will use baseline
>>> topology [1].
>>> In our case we are using rebalanceDelay for in-memory caches.
>>>
>>> [1] htt
, 12 февр. 2020 г. в 12:18, Zhenya Stanilovsky < arzamas...@mail.ru.invalid
>>:
>
>>
>>
>> But baseline, it`s about persistence [1] isn`t it? I wrote about
>> pure inmemory case.
>>
>> [1] https://apacheignite.readme.io/docs/baseline-topology
>> &
n Vinogradov" < a...@apache.org >
>To: dev@ignite.apache.org
>Cc: "Zhenya Stanilovsky" < arzamas...@mail.ru >
>Subject: Re: Excessive backups performance suggestion.
>Date: Thu, 06 Feb 2020 14:11:50 +0300
>
>>> most users do not want to lose data b
Hello, no objections found, plz who can merge it [1]?
[1] https://issues.apache.org/jira/browse/IGNITE-12725
Igniters, 2.8 version already released, but looks like TC bot [1] [2] still
using 2.7.6 ver. , who can update it ?
Thanks !
[1] https://github.com/apache/ignite-teamcity-bot
[2] https://mtcga.gridgain.com/
Igniters, i found that near idle check commands only shows partitions in MOVING
states as info in log and not take into account this fact as erroneous idle
cluster state.
control.sh --cache idle_verify, control.sh --cache validate_indexes --check-crc
for example command would show something li
Guys thank for quick response, Ivan what do you think about Vlad`s proposal to
add additional info like :
"Possible results are not consistent due to rebalance still in progress" ?
Thanks !
>Понедельник, 23 марта 2020, 12:30 +03:00 от Ivan Rakov :
>
>Zhenya,
>
&
new version to the server (since it is now sponsored by
>> GrigGain, we need someone who will deploy).
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> пн, 23 мар. 2020 г. в 08:59, Zhenya Stanilovsky < arzamas...@mail.ru >:
>>
>>> Igniters, 2.8 ve
Ivan, i found that mentioned problem correctly highlighted, if we still not
step on this rake, its probably due to some locks above, anyway it would be
correct to fix this part. Are you fill the ticket ?
>
>
>--- Forwarded message ---
>From: "Ivan Daschinsky" < ivanda...@gmail.com >
>
This ticket is very important too, as for me [1] Anton Kalashnikov, what do you
think ?
[1] https://issues.apache.org/jira/browse/IGNITE-12801
>Folks,
>
>I'd like to add ticket IGNITE-12805 "NullPointerException on node restart
>when 3rd party persistence and Ignite native persistence are used
+1 here.
Hi Igniters,
I have a very simple proposal. Let's set default TX timeout to 5 minutes
(right now it's 0 = no timeout).
Pros:
1. Deadlock detection procedure is triggered on timeout. In case user
will
get into key-level deadlock, he'll be able to discover root cause from
the
logs (
Good catch Steve ! I also think about that.
Ticket unassigned — you can proceed with it.
Also you need to ask your jira account for granting rights for further ticket
assignation.
High level review can make i (@zstan) and probably (@ivandasch).
Also you need to explain how to run new (ignite-6499
Thank you Sergey, as for me — very useful proposal huge +1 here.
>Четверг, 21 мая 2020, 0:51 +03:00 от Sergey Antonov
>:
>
>I've created the Ignite ticket for this improvement [1].
>
>[1] https://issues.apache.org/jira/browse/IGNITE-13047
>
>чт, 21 мая 2020 г. в 00:46, Sergey Antonov < anto
Ivan, does global timeout change through jmx in scope of this ticket ? If so,
can you add it ? Opposite we need additional ticket, i hope ? We still have no
somehow store for jmx changed params, every one need to remember that cluster
restart will reset this setting to default, in this case sys
I`m currently against this approach, everyone can previously compress Binary
Object for further using, no additional code need here. This discussion only
about currently not optimal null storing and looks like we can improve it
without performance pay.
>Понедельник, 25 мая 2020, 13:42 +0
Compress of whole binary inside ignite.
>Sorry I do not actual get what are you opposing? the compress of the binary
>or the null compaction or both?
>And can you ellaborate on why you are opposing it?
>
>
>
>--
>Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Nikolay, performance boost is always good news for all customers at all and for
me too )
Can you give more info (looks like in different mail thread) ? What kind of
benchmarks have been done, is it about persistence or both ?
thanks !
>+1 (binding).
>
>We made some internal benchmarking and foun
Ivan huge +1 with your proposal.
I had some problems with odbc tests building too, looks like cmake will make it
more easy.
>Hello Igniters.
>
>I’d like to discuss porting build process of Ignite.C++. I think that there is
>time to change it.
>
>*Motivation*
>Currently, it is hard to build Ignit
Of course, i just thinking about huge persistent installation and guys who not
carefully reads Release Notes )
In case of long tx timeouts by design, they can easily fix default timeout with
just one jmx call.
>Zhenya,
>
>Can you please elaborate?
>Why we need to change defaul
What about tests? I found one flag that must be
>> supplied to boost.tests.
>> This flag should fix JVM crash of C++ suites on Linux.
>>
>> Zhenya Stanilovsky and me have checked, that without this flag tests failed
>> with SIGSEGV early (boost catch this signal from
good catch ! it`s a little bit pain for now to working with it.
>Hi, Igniters!
>
>At the moment to work with the control.sh we need to know exactly what the
>name of the command and its options are and so the user can often make
>mistakes when using it. So I think it would be useful to do co
Sergey, changes looks good to me.
>Четверг, 4 июня 2020, 12:39 +03:00 от Sergey Antonov
>:
>
>Igniters, I faced several problems during write tests for the read-only
>mode:
>
> 1. You can create/destroy cache on the read-only cluster. Fixed in [1].
> 2. The read-only mode doesn't affect
Steve i place some comments in ticket, still have no response.
>
>
>--- Forwarded message ---
>From: " steve.hostett...@gmail.com " < steve.hostett...@gmail.com >
>To: dev@ignite.apache.org
>Cc:
>Subject: Re: Re[4]: IGNITE-6499 Compact NULL fields
>Date: Fri, 12 Jun 2020 16:15:37 +0300
request it, check for example [1]
also you need to run [2] tests.
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/Phani-Introduction-td47788.html
[2] https://mtcga.gridgain.com
>Hello,
>
>Look at the ticket and the only comment I can see is creating a branch on
>git in the main re
now its all ok, i rerun your pr here :
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=pull%2F7906%2Fhead&tab=buildTypeStatusDiv
>Hi Ivan,
>
>let me first apologize for the question, sure they are stupid and I am
>missing something ob
Alex, i also suggest to merge this
https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient leakage and
further TC OOM preventing.
>Ivan,
>
>It was already in release scope as discussed in this thread.
>
>вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
>
>> Hi,
Looks like we need additional func for static caches, for example:
warmup(List cconf) it would be helpful for spring too.
>
>--- Forwarded message ---
>From: "Вячеслав Коптилин" < slava.kopti...@gmail.com >
>To: dev@ignite.apache.org
>Cc:
>Subject: Re: [DISCUSSION] Cache warmup
>Date:
I`m currently working on cpp thin client transactions support [1] and need to
edit, for example this page [2].
Can someone grant me this privileges ?
thanks !
[1] https://issues.apache.org/jira/browse/IGNITE-13308
[2] https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features
Ilya, thanks !
full name : evgeny stanilovsky , short : zstan
>
>>
>>>Hello!
>>>
>>>Do you have a Wiki account? What's its username?
>>>
>>>Thanks,
>>>--
>>>Ilya Kasnacheev
>>>
>>>
>>&
may be jmx would be enough here ?
>Hello!
>
>Why not the Failure Handler then?
>
>(I'm only half-joking).
>
>Regards,
>
>--
>Ilya Kasnacheev
>
>
>ср, 12 авг. 2020 г. в 09:54, Oleg Ostanin < oleg.alex.osta...@gmail.com >:
>
>> Thank you for the response. Yes, we have a simple warning in log, b
Igniters, seems i complete with transactions in thin cpp client implementation
[1], part of iep-34 [2].
Can anyone review my decision ?
Failed test seems not mine, looks like after fresh master rebase it will gone.
[1] https://issues.apache.org/jira/browse/IGNITE-13308
[2]
https://cwiki.apa
1 - 100 of 162 matches
Mail list logo
