Hi All,
I will be taking a break from the Ignite community for an indefinite
period. During this period, I will not be available on the dev list or
looking at JIRA tickets.
If anything urgent comes up, please email me on my Apache email ID, or
reach out on Slack.
Atri
> > > How can we be sure that new changes in TCP discovery Ignite's
> > > component won't break the Azure module? I don't think we should allow
> > > such a practice at all, so the AWS and GCE is not a good example here.
> > > P
> mentioned in Jira), it passes successfully. But I'm not sure if this
> > is enough.
> >
> > пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov :
> > >
> > > Atri.
> > >
> > > Right now code can’t be tested because it doesn’t compile.
> > &g
t; I trust you all :-)
> But who can validate the patch [1]? This is a bad practice that only a
> few members be able to test the code.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15388
>
> On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote:
> >
> > It was extensive
tested the module in the cloud? If it works, then I don't
> see any reason why we need to have someone else double-checking this once
> again. This is the community, we need to trust each other.
>
> -
> Denis
>
> On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote:
>
&g
I would argue that the module Co exists with the other IP discovery modules
(such as GCP and AWS), which are part of core.
In terms of tests, the azure module has exactly the same type of tests as
the other two modules mentioned above.
On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, wrote:
> Folks,
I will review tonight.
On Wed, 1 Sep 2021, 19:54 Pavel Pereslegin, wrote:
> Hello, Igniters!
> I think the patch is ready [1].
>
> Ilya, Atri,
> could you help with the review?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15388
>
> пт, 27 авг. 2021 г. в 15:29, Maxim Muzafarov :
> >
> > F
I will look into 15388
On Fri, 27 Aug 2021, 18:16 Maxim Muzafarov, wrote:
> Folks,
>
>
> I've been faced these issues, which seems to be a blocker for the
> release. Please, take a look and share your thoughts.
>
> The server node fails when the client node with the higher java
> version connect
rd ones:
> 1. Do not implement FTS.
> 2. Create own implementation.
>
> Some of the strongest ones live without FTS [1].
>
> [1] https://github.com/cockroachdb/cockroach/issues/7821
>
> 2021-08-02 11:33 GMT+03:00, Atri Sharma :
> > Hi Ivan,
> >
> > Would you like to
wn clearly that "fastest feature implementation" is not usually
> the best. And one example of this are text queries. Are not we trying
> to do a same mistake again? FTS is a huge feature, I do not believe
> there is an easy win for it.
>
> 2021-07-27 19:18 GMT+03:00, Atri Sha
Query caching works on three levels - caching results, caching blocks and
caching query plans.
Prepared queries work by caching a plan for a query and reusing that plan
by changing the parameters for the incoming query. So the query remains the
same, but input values keep changing.
The problem wi
Hi Ilya,
Following up on this please.
On Tue, 27 Jul 2021, 22:20 Atri Sharma, wrote:
> Hi Ilya,
>
>
> > Frankly speaking, I do not see the value of having an extra layer of
> > indirection around *local* Quartz-based scheduler in Ignite. Can you
> > elaborate?
>
&
Hi Ilya,
> Frankly speaking, I do not see the value of having an extra layer of
> indirection around *local* Quartz-based scheduler in Ignite. Can you
> elaborate?
I didnt quite understand that. Are you referring to the
IgniteCombinedSchedulerProcessor?
>
> Our guidelines also recommend having i
ave.
> Lucene index may be non-transactional, but users never expect to see
> uncommited data.
> How does this connect with transactional SQL?
We could have the Lucene writes done as a part of transactions and ack
back only when it succeeds/fails. WDYT?
>
> On Tue, Jul 27, 2021 at
Hello,
I have raised a PR for the said JIRA:
https://github.com/apache/ignite/pull/9277
TC is green with the PR:
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/6105253
Please help in reviewing.
Regards,
Atri
h all of this, you can go with the IEP (or even some short summary) and
> further POC and implementation.
> That's a big deal, so let's discuss what could be done here.
>
> On Fri, Jul 23, 2021 at 12:58 PM Atri Sharma wrote:
>
> > I am actually happy to drive the feat
r all the reasons you mentioned and more, using Lucene is the right
> > choice
> >
> > Calcite doesn't have support for Solr but it has an ES adapter which is
> > what we modified to support Solr.
> >
> > Regards,
> > Courtney Robinson
> > Founder
o>
> https://hypi.io
>
>
> On Fri, Jul 23, 2021 at 7:14 PM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Atri,
> >
> > Sure, go ahead. Let's put the ideas on paper and have a discussion.
> >
> > -Val
> >
> >
ndex into Calcite? What is the cost model?
> Splitting rules? Traits?
> * What about consistency with DDL operations, e.g. column rename?
> Ignite indices will operate column ID, so rename operation will not affect
> the index.
>
>
> With all of this, you can go with the IEP (or ev
ly? after
> > node/grid restart?
> > * Any limitations on query syntax?
> >
> > SQL
> > * Will we support FullText search in SQL?
> > * How to integrate Lucene index into Calcite? What is the cost model?
> > Splitting rules? Traits?
> > * What about consistency wi
ests for this thing from the user side, and
> definitely,
> FTS would be a valuable feature for Ignite.
>
> It will be great if the one wants to drive it, any help will be appreciated.
>
>
> On Fri, Jul 23, 2021 at 12:12 PM Atri Sharma wrote:
>
> > Hello,
> >
>
and visibility.
>
> Maybe 2. and 3. will even use a different approach when persistence is
> implemented.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 28 июн. 2021 г. в 14:34, Atri Sharma :
>
> > Hello Again!
> >
> > I have been looking into th
Infra group is the ideal forum for this
On Thu, 22 Jul 2021, 18:14 Denis Magda, wrote:
> Dmitry, Ivan,
>
> It would be ideal if we can open up PonyMail archives for search engines.
> It might be just one setting on a web server configuration. Dmitry, any
> idea whom we should start discussing th
Gentle ping. Please help with context here.
On Mon, 5 Jul 2021, 13:03 Atri Sharma, wrote:
> Hi All,
>
> As part of the text queries overhaul effort, I am looking into the
> following ticket:
>
> https://issues.apache.org/jira/browse/IGNITE-12401
>
> As I understand it,
Hi All,
As part of the text queries overhaul effort, I am looking into the
following ticket:
https://issues.apache.org/jira/browse/IGNITE-12401
As I understand it, the problem lies in the fact that a partition can
move, thus causing duplicate data between two Lucene indices (on
different nodes).
rote:
> >
> > > We can add add an extra param in annotation, that blocks param to be
> > > printed, just set it to false by default and block it wheb set to true
> > >
> > > чт, 1 июл. 2021 г., 19:45 Atri Sharma :
> > >
> > > > What if we allowed
What if we allowed a blocklist of parameters that are never printed?
On Thu, 1 Jul 2021, 22:06 Valentin Kulichenko, <
valentin.kuliche...@gmail.com> wrote:
> Not all of them are OK to be printed out. At the very least, we should have
> a mechanism to exclude some of them. I would still go with op
AFAIK, this allows users to pass in custom VM options which may be undesirable.
On Thu, Jul 1, 2021 at 12:07 PM Zhenya Stanilovsky
wrote:
>
>
> +1 for reverting, can anybody (possibly ticket starter?) explain how jvm
> settings will rise some security problems ?
>
>
>
> >I suppose, that we shoul
I have opened a JIRA for the same:
https://issues.apache.org/jira/browse/IGNITE-15043
Unless objections, I plan on sketching an implementation plan.
On Thu, Jul 1, 2021 at 1:07 AM Atri Sharma wrote:
>
> Hi All,
>
> I have been playing around with Collision SPI and speci
Hi All,
I have been playing around with Collision SPI and specifically used
FifoQueueCollisionSPI and noticed that it is not really adhering to
the specified task of restricting the number of concurrent tasks that
can be run.
Specifically, if there is only one slot available and N tasks
concurren
Gentle ping
On Thu, Jun 24, 2021 at 6:36 PM Atri Sharma wrote:
>
> Hi All,
>
> Can we please publish Spring Sessions Ext artifacts to the Maven repo?
>
> Atri
--
Regards,
Atri
Apache Concerted
new type of queries I'm implementing (IndexQuery, it should also provide
> > ordered results over multiple nodes). Currently I'm not planning to go
> > further with TextQuery, so if you're going to support this it'll be a great
> > contribution, I think.
> >
&g
Hi All,
Can we please publish Spring Sessions Ext artifacts to the Maven repo?
Atri
Hello all,
Sam has approved the PR and tests are passing:
https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_SpringSession/6055833
Can we please approve and merge?
On Fri, 18 Jun 2021, 13:28 Atri Sharma, wrote:
> Hi All,
>
> Please find PR for the aforementio
nning to go
> > further with TextQuery, so if you're going to support this it'll be a great
> > contribution, I think.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-14703
> > [2] https://github.com/apache/ignite/pull/9081
> >
> >
&
Hi All,
I have been looking into our text queries support and see that it has
limited community support.
Therefore, I volunteer to be the maintainer of the module and work on
enhancing it further.
First goal would be to move to Lucene 8.x, then work on sorted reduce
- merge across nodes. Fundame
Hi All,
Please find PR for the aforementioned issue:
https://github.com/apache/ignite-extensions/pull/63
@Данилов Семён Please help in reviewing.
Regards,
Atri
--
Regards,
Atri
Apache Concerted
+1
On Sun, 9 May 2021, 21:33 Stanislav Lukyanov,
wrote:
> Hi Eduard,
>
> I strongly believe that if a configuration option is cluster wide then it
> belongs to distributed metastore and not to IgniteConfiguration.
> This allows to get cluster-wide consistency guarantees and API for dynamic
> cha
> -Val
>
> On Wed, Apr 28, 2021 at 1:07 AM Atri Sharma wrote:
>
> > Hi Ilya and Val,
> >
> > Thank you for taking a look and providing insights. I have updated the
> > PR and raised another iteration.
> >
> > Val, I have moved the configuration to TcpD
> configuration property on the TcpDiscoverySpi instead. Otherwise, the
> filtering should be applied to all network components (although I'm not
> necessarily sure what that would imply).
>
> What do you think?
>
> -Val
>
> On Tue, Apr 27, 2021 at 2:00 AM Atri Sharma wrote:
Hello!
>
> I'm still not fully convinced, but Val's approach sounds rational to me.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 22 апр. 2021 г. в 12:45, Atri Sharma :
>
> > Hello!
> >
> > I actually saw the shared container scenario being tried
e at the conclusion to go
> forward with it?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 22 апр. 2021 г. в 07:51, Atri Sharma :
>
> > Hi Val,
> >
> > Consider a scenario where multiple Ignite clusters are running and for
> > operational ease (and also c
Another thing is IP addresses blocked by firewalls -- such IPs will
cause the cluster bootstrap to slow down.
On Thu, Apr 22, 2021 at 10:20 AM Atri Sharma wrote:
>
> Hi Val,
>
> Consider a scenario where multiple Ignite clusters are running and for
> operational ease (and also
se the users.
>
> Would you mind either making regexp filter setting a part of Azure IpFinder
> only or fix other IpFinders as well?
>
>
> On Wed, Apr 21, 2021 at 7:04 PM Atri Sharma wrote:
>
> > Hi,
> >
> > When a container is shared by multiple cluster
gnitePredicate, so you will
> be able to provide any implementations, including regex or anything else.
>
> -Val
>
> On Wed, Apr 21, 2021 at 9:04 AM Atri Sharma wrote:
>
> > Hi,
> >
> > When a container is shared by multiple clusters, then this can be useful
>
ture? Can you please elaborate?
>
> Thanks,
> --
> Ilya Kasnacheev
>
>
> ср, 21 апр. 2021 г. в 08:23, Atri Sharma :
>
> > Hi All,
> >
> > I have opened the following JIRA for the said topic:
> >
> > https://issues.apache.org/jira/browse/IGNITE-146
Hi All,
I have opened the following JIRA for the said topic:
https://issues.apache.org/jira/browse/IGNITE-14606
The concept is to filter IPs based on a pattern or a blocklist in
IPFinders while consuming IPs. This is more pertinent for cloud based
IPFinders since they can have shared containers.
Atri Sharma created IGNITE-14608:
Summary: Blocklist Based IP Filtering in IPFinders
Key: IGNITE-14608
URL: https://issues.apache.org/jira/browse/IGNITE-14608
Project: Ignite
Issue Type: Sub
Atri Sharma created IGNITE-14607:
Summary: Regex Based Filter in IPFinders
Key: IGNITE-14607
URL: https://issues.apache.org/jira/browse/IGNITE-14607
Project: Ignite
Issue Type: Sub-task
Atri Sharma created IGNITE-14606:
Summary: Filter Support in IPFinders
Key: IGNITE-14606
URL: https://issues.apache.org/jira/browse/IGNITE-14606
Project: Ignite
Issue Type: Improvement
; >
> > Thank you for driving this effort, Atri.
> >
> > The Azure IP Finder code has been merged and will surely be a highlight
> in
> > Apache Ignite 2.11.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > ср, 14 апр. 2021
+1 to move issues to the issues list.
For MTCGA, maybe build@?
On Wed, Apr 14, 2021 at 8:35 PM Ilya Kasnacheev wrote:
>
> Hello!
>
> We have a discussion on how to ensure best engagement in dev@ list, and it
> seems that Issue Created emails from IGNITE project consume a lot of screen
> space, i
; jackson, and preferably for all dependencies.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 13 апр. 2021 г. в 10:33, Atri Sharma :
>
> > Hello,
> >
> > Sorry for the late reply.
> >
> > Thank you for taking a look. Indeed, there were some iss
and comments.
Regards,
Atri
On Fri, Apr 9, 2021 at 4:58 PM Ilya Kasnacheev
wrote:
>
> Hello!
>
> I have responded to the ticket after testing on live Azure.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 9 апр. 2021 г. в 08:37, Atri Sharma :
>
> > Hi
Hi Ilya,
Please let me know if I can help with any further iterations on the PR.
Regards,
Atri
On Wed, Apr 7, 2021 at 5:04 PM Atri Sharma wrote:
>
> Hi Ilya,
>
> Thanks for taking a look. I was able to resolve dependencies (Thanks,
> Sam!) and have updated the PR.
>
>
Hello!
> >
> > I'm not sure that I can see any attachment to your e-mail. Can you please
> > re-send?
> >
> > We could have broken some of those, I guess, since we seem to not run
> > integration tests for them.
> >
> > Regards,
> > --
> &
add such a method to thick client too.
>
> пн, 5 апр. 2021 г. в 09:48, Atri Sharma :
>
> > Hi Alex,
> >
> > Sorry for the late reply.
> >
> > Regarding the thick client, would it be a challenge to add a new method
> > which takes takes interface as parameter?
stener is thin client specific.
> 2. Thick client API uses JCache interfaces, which cannot be modified.
> 2. We can't modify thick client public API either, due to backward
> compatibility.
>
> пт, 2 апр. 2021 г. в 11:51, Atri Sharma :
>
> > Personally, I would disagree
ind attached the log file of errors. This is yesterday's (Apr 1)
> build.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 2 апр. 2021 г. в 11:52, Atri Sharma :
>>
>> I was able to, but then, it might be that something is cached locally.
>>
>> W
in running a node with Azure IP finder enabled in
> configuration, starting from that release directory?
>
> I amn't.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 2 апр. 2021 г. в 07:42, Atri Sharma :
>
> > Hello,
> >
> > Thank you for taking
Personally, I would disagree with an interface implementation being
dictated by the documentation rather than the method signature.
How about having a generic interface (placeholder interface), have
both the thick and thin clients expose methods using the interface as
parameters, then let ClientCh
ght now
> the module directory is empty so I'm not even going to test to run it in
> stand-alone mode:
> ~/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin% ls libs/optional/ignite-azure
> azure-storage-blob-12.0.0.jar ignite-azure-2.11.0-SNAPSHOT.jar README.txt
>
> Please
t; > I am going to check this change out when I have time, using my Azure
> > > account.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вт, 23 мар. 2021 г. в 07:20, Atri Sharma :
> > >
> > > > Gen
t...@apache.org
> > > >
> > > > >> >> > > wrote:
> > > > >> >> > >
> > > > >> >> > > On the one hand, I agree with Alexey.
> > > > >> >> > > CompletableFutu
On further look, this looks interesting and I am happy to dive into the
spring framework.
Please help me in getting started
On Mon, 29 Mar 2021, 11:49 Atri Sharma, wrote:
> Thanks Sam and Ivan.
>
> I am happy to look into that but it looks like most of the work is done
> there?
ave any
> > questions.
> >
> > Cheers, Sam.
> >
> > 25.03.2021, 23:33, "Atri Sharma" :
> >> Hi Community,
> >>
> >> First off, I want to thank the community for being so welcoming and
> >> helpful. This is an awesome place
Hi Community,
First off, I want to thank the community for being so welcoming and
helpful. This is an awesome place to be in.
Now that I have worked on some issues, I would like to get my hands deeper
and with larger issues in the core. Also, some more intermediate tickets to
tackle, my queue has
I would suggest using CompletableFuture -- I don't see a need for a custom
interface that is unique to us.
It also allows a lower barrier for new contributors for understanding
existing code
On Thu, 25 Mar 2021, 20:18 Andrey Mashenkov,
wrote:
> Hi Igniters,
>
> I'd like to start a discussion ab
Thank you!
I have updated the PR. Please see and let me know.
On Tue, Mar 23, 2021 at 4:27 PM Ilya Kasnacheev
wrote:
>
> Hello!
>
> I am going to check this change out when I have time, using my Azure
> account.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт,
Gentle reminder on this -- please help in reviewing this.
On Fri, Mar 19, 2021 at 10:23 AM Atri Sharma wrote:
>
> Thanks Denis.
>
> I have raised a PR for the same:
>
> https://github.com/apache/ignite/pull/8897
>
> Regards,
>
> Atri
>
> On Wed, Mar 10
AM Atri Sharma wrote:
>
> Thanks Denis.
>
> I have raised a PR for the same:
>
> https://github.com/apache/ignite/pull/8897
>
> Regards,
>
> Atri
>
> On Wed, Mar 10, 2021 at 1:21 AM Denis Magda wrote:
> >
> > Atri,
> >
> > Let's disc
Atri Sharma created IGNITE-14347:
Summary: Fix Node failure on Receiving Data of Unknown class via
Distributed Metastorage
Key: IGNITE-14347
URL: https://issues.apache.org/jira/browse/IGNITE-14347
Thanks Denis.
I have raised a PR for the same:
https://github.com/apache/ignite/pull/8897
Regards,
Atri
On Wed, Mar 10, 2021 at 1:21 AM Denis Magda wrote:
>
> Atri,
>
> Let's discuss the subj together with the community. Ignite already supports
> AWS [1] and GCE [2] IP Finders out of the box,
Atri Sharma created IGNITE-14346:
Summary: Implement Azure Blob Storage Based IP Finder
Key: IGNITE-14346
URL: https://issues.apache.org/jira/browse/IGNITE-14346
Project: Ignite
Issue Type
Thank you so much!
On Thu, Mar 18, 2021 at 3:01 AM Valentin Kulichenko
wrote:
>
> Hi Atri,
>
> Looks good to me, I've merged the changes. Please resolve the ticket.
>
> -Val
>
> On Wed, Mar 17, 2021 at 5:07 AM Atri Sharma wrote:
>
> > Hi Valentine,
>
Hi Valentine,
Hoping you are well.
Please let me know if the PR looks ok.
Regards,
Atri
On Thu, 11 Mar 2021, 12:09 Atri Sharma, wrote:
> Hi Val,
>
> Thanks for taking a look. I have updated the PR, please see and let me
> know your thoughts and feedback.
>
> Regards,
&
Hi All,
I would like to propose a change: today, in GridDhtLockFuture, we do
not consider if the cache context is being cleaned up before loading
missing entries from the store. However, if the cache context is being
cleaned up, this operation is moot.
I have raised a PR for the same. Please shar
Atri Sharma created IGNITE-14314:
Summary: GridDhtLockFuture#onComplete Should Be Aware of Cache
Cleanup
Key: IGNITE-14314
URL: https://issues.apache.org/jira/browse/IGNITE-14314
Project: Ignite
Gentle ping
On Thu, 11 Mar 2021 at 2:56 PM, Atri Sharma wrote:
> Hi All,
>
> I have raised a PR for the above mentioned issue. Please see and help
> review:
>
> https://github.com/apache/ignite/pull/8868
>
> Regards,
>
> Atri
>
> --
> Regards,
>
>
+1 (non binding)
Built from source, ran tests and tried the Java client
On Thu, 11 Mar 2021, 16:13 Zhenya Stanilovsky,
wrote:
>
>
> Build from sources, run .net tests, looks good. +1
>
>
>
> >+1 (binding)
> >
> >Downloaded binary packages, started nodes, .NET examples, .NET nodes.
> >Downloaded
Hi All,
I have raised a PR for the above mentioned issue. Please see and help review:
https://github.com/apache/ignite/pull/8868
Regards,
Atri
--
Regards,
Atri
Apache Concerted
Hi Val,
Thanks for taking a look. I have updated the PR, please see and let me
know your thoughts and feedback.
Regards,
Atri
On Thu, Mar 11, 2021 at 6:16 AM Valentin Kulichenko
wrote:
>
> Atri,
>
> I've added my comments to the PR.
>
> -Val
>
> On Wed, Mar 10
I have just updated the PR:
https://github.com/apache/ignite/pull/8820
Please review.
On Wed, Mar 10, 2021 at 1:51 PM Atri Sharma wrote:
>
> Hi Val,
>
> Thank you for taking the time on this one.
>
> The main reason as to why I chose that signature was because I felt it
>
o the
> IgniteSemaphore interface.
>
> -Val
>
> On Tue, Mar 9, 2021 at 8:22 AM Atri Sharma wrote:
>
> > Gentle ping
> >
> > On Mon, 8 Mar 2021, 13:51 Atri Sharma, wrote:
> >
> > > Hi All,
> > >
> > > I would like to start a
Gentle ping
On Mon, 8 Mar 2021, 13:51 Atri Sharma, wrote:
> Hi All,
>
> I would like to start a discussion around IGNITE-2399.
>
> Background: The typical use of IgniteSemaphore consists of acquiring
> the semaphore, performing the task and releasing the semaphore. This
>
; This one looks OK, I will merge.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 8 мар. 2021 г. в 10:57, Atri Sharma :
>
> > Hello,
> >
> > I ran the test suite and here is the link:
> >
> >
> >
> https://ci.ignite.apache.org/buildConfiguratio
Hi All,
I would like to start a discussion around IGNITE-2399.
Background: The typical use of IgniteSemaphore consists of acquiring
the semaphore, performing the task and releasing the semaphore. This
JIRA proposes a new method which will accept a callable, acquire the
semaphore, and return a fut
:
>
> Hello!
>
> Please run tests against this change, get a green TC visa for the ticket.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 3 мар. 2021 г. в 17:13, Atri Sharma :
>
> > Hi,
> >
> > Please help review this PR:
> >
> > https:
Hi,
Please help in reviewing:
https://github.com/apache/ignite/pull/8820
Atri
Hi,
Please help review this PR:
https://github.com/apache/ignite/pull/8845
Regards,
Atri
Hi,
I have raised a new PR for IGNITE-14225:
https://github.com/apache/ignite/pull/8833
Please help in reviewing.
Regards,
Atri
--
Regards,
Atri
Apache Concerted
Atri Sharma created IGNITE-14225:
Summary: Add Helper Method to Check For Expected Exceptions in
JUnitAssertAware
Key: IGNITE-14225
URL: https://issues.apache.org/jira/browse/IGNITE-14225
Project
Thank you, very kind of you! Let me fix the PR and ping you back there.
On Tue, 23 Feb 2021 at 2:05 PM, Данилов Семён wrote:
> Hello Atri,
>
> I've read through your changes, have a look at the review.
>
> Kind regards,
> Sam.
>
> 23.02.2021, 08:07, "Atri Sh
Hi All,
Please help in reviewing the following PR:
https://github.com/apache/ignite/pull/8820
Regards,
Atri
--
Regards,
Atri
Apache Concerted
- aleksey plekhanov
> https://ci.ignite.apache.org/viewModification.html?modId=917288
> - atri sharma
> https://ci.ignite.apache.org/viewModification.html?modId=917319
> - mikhail petrov
> https://ci.ignite.apache.org/viewModification.html?modId=917314
>
&g
Hi,
Please grant me JIRA permissions. My user id is atri
--
Regards,
Atri
Apache Concerted
Thank you!
Where do I figure out which tests are currently flaky?
On Wed, Feb 17, 2021 at 8:58 PM Ilya Kasnacheev
wrote:
>
> Hello!
>
> I think these tests are flaky, I have triggered them to re-run.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 17 ф
t; Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 17 февр. 2021 г. в 07:49, Atri Sharma :
>
> > Thank you! I have updated the PR per your comments.
> >
> > On Tue, Feb 16, 2021 at 9:29 PM Ilya Kasnacheev
> > wrote:
> > >
> > > Hello!
> &
Thank you! I have updated the PR per your comments.
On Tue, Feb 16, 2021 at 9:29 PM Ilya Kasnacheev
wrote:
>
> Hello!
>
> I have left some comments to the PR.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 15 февр. 2021 г. в 18:55, Atri Sharma :
>
> > Hi
Hi all,
I have raised a PR for IGNITE-12508:
https://github.com/apache/ignite/pull/8802
Requesting inputs and feedback on the same, please.
Regards,
Atri
--
Regards,
Atri
Apache Concerted
100 matches
Mail list logo
