Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

Yuriy, > Let me summarize the approaches: I agree with your reasoning, p.2 sounds the best one to me as well. Will look into merge-sort strategy some time later. Best regards, Ivan Pavlukhin пт, 13 мар. 2020 г. в 19:23, Yuriy Shuliga : > > Ivan, > > I have made changes i

Re: Veena - subscribe to the dev list before sending emails

Hi Veena, I suppose that subscribing to iss...@ignite.apache.org is an overkill because there is so much JIRA notifications. If you wish to receive notifications about a particular issue I suggest to start "watching" it in JIRA. Best regards, Ivan Pavlukhin вс, 15 мар. 2020 г. в 15

Re: Workaround for possible NPE in Selector.open()

Folks, I created a ticket [1] and raised PR. TC is in progress. [1] https://issues.apache.org/jira/browse/IGNITE-12787 Best regards, Ivan Pavlukhin вт, 10 мар. 2020 г. в 16:56, Ilya Kasnacheev : > > Hello! > > Feel free to file a ticket, contribute a fix. > > Regards, >

Re: подписаться

A note for curious ones. Dev-list requires moderation for messages from unsubscribed addresses. As the initial message was delivered without moderation I suppose Kirill had been already subscribed at that (roughly) moment. Best regards, Ivan Pavlukhin пн, 16 мар. 2020 г. в 15:45, Кирилл Пушенко

Re: Workaround for possible NPE in Selector.open()

Igniters, Please review PR for the subject https://issues.apache.org/jira/browse/IGNITE-12787 Best regards, Ivan Pavlukhin пн, 16 мар. 2020 г. в 00:38, Ivan Pavlukhin : > > Folks, > > I created a ticket [1] and raised PR. TC is in progress. > > [1] https://issues.apache.org/

Re: Workaround for possible NPE in Selector.open()

Merged to master. Best regards, Ivan Pavlukhin ср, 18 мар. 2020 г. в 00:53, Ivan Pavlukhin : > > Igniters, > > Please review PR for the subject > https://issues.apache.org/jira/browse/IGNITE-12787 > > Best regards, > Ivan Pavlukhin > > пн, 16 мар. 2020 г. в 00:38,

Re: Commit message format

tters with unnecessary rules. Not all of us contribute only in Ignite and both formats (with colon and not) are common [1, 2, 3]. [1] https://github.com/apache/kafka/commits/trunk [2] https://github.com/apache/hive/commits/trunk [3] https://github.com/openjdk/jdk/commits/master Best regards, Ivan

Re: Commit message format

a commit message? In my opinion current state with commit messages prefixes is totally fine and there is no need to change anything. Best regards, Ivan Pavlukhin пт, 20 мар. 2020 г. в 01:40, Andrey Gura : > > Ivan, > > What could be simpler than exactly one format without any option

Re: FetchSize of the JdbcStore

Hi Nikolay, There is a very similar ticket [1]. Perhaps it could be somehow useful. [1] https://issues.apache.org/jira/browse/IGNITE-11894 Best regards, Ivan Pavlukhin чт, 26 мар. 2020 г. в 17:54, Nikolay Izhikov : > > Hello, Igniters. > > Right now there is no way for the

Re: Get rid of @Nullable and @NotNull

instead of doing explicit null check everywhere. Best regards, Ivan Pavlukhin пт, 27 мар. 2020 г. в 13:05, Denis Garus : > > Hi! > I'm not sure that @Nullable can really fix the NPE problem. > Currently, we have @Nullable annotation and NPE simultaneously. > The best way to avo

Re: Contribution

://ignite.apache.org/community/contribute.html Best regards, Ivan Pavlukhin пн, 6 апр. 2020 г. в 12:25, Никита Алемаскин : > > Hello Ignite Community! > > My name is Nikita. I want to contribute to Apache Ignite and want to > start with this issue - IGNITE-11494 > <https://issues.a

Re: Joining Ignite ASF

://ignite.apache.org/community/contribute.html Consult "Pick a ticket" section if you have no ticket to start with. Best regards, Ivan Pavlukhin пн, 6 апр. 2020 г. в 21:07, Данилов Семён : > > Hello! > I would like to start contributing, could you please add me to contributors > li

Re: No commits to Ignite website: migration from SVN to Git is in progress

Denis, Is it expected that main website https://ignite.apache.org/ does not work now? Best regards, Ivan Pavlukhin сб, 4 апр. 2020 г. в 01:15, Denis Magda : > > Igniters, > > Please avoid any commits to the website repository until further notice. > We're in a process of th

Re: No commits to Ignite website: migration from SVN to Git is in progress

Thank you! Best regards, Ivan Pavlukhin вт, 7 апр. 2020 г. в 00:46, Denis Magda : > > The website is back to normal and serves the content from the Git > repository's "master" branch: > https://github.com/apache/ignite-website/blob/master > > - > Denis > &

Re: Remove "This operating system has been tested less rigorously" diagnostic

Thumbs up! Best regards, Ivan Pavlukhin пн, 13 апр. 2020 г. в 15:08, Pavel Tupitsyn : > > Since there are no objections, I'll go ahead with removal. > > Thanks > > On Wed, Apr 8, 2020 at 10:35 PM Pavel Tupitsyn wrote: > > > Igniters, > > > > Let

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Hi folks, A side note from an external spectator. Should not we reflect on the release page [1] who is a release manager? [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : > > Hello, Ig

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

1. Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov : > > Hello, > > > Should not we reflect on the release page [1] who is a release manager? > > We didn’t it for the previous releases. > Why we should start to do it?) > > > I suggest to i

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Great! Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 12:48, Nikolay Izhikov : > > OK, let’s try it > > > I do not know who is a manager for 2.8.1. > > I am. > > > > 17 апр. 2020 г., в 12:42, Ivan Pavlukhin написал(а): > > > >> We didn’t

Re: [DISCUSSION] `static final` code-style constant naming rules

blems. For example, a developer can make false assumptions about immutability and thread safety basing on a capitalized field name. [1] https://google.github.io/styleguide/javaguide.html#s5.2.4-constant-names Best regards, Ivan Pavlukhin пт, 24 апр. 2020 г. в 21:58, Pavel Tupitsyn : > > &g

Re: Hello.

Welcome Ivan, I added your account to the contributors list in JIRA. Now you can assign tickets to yourself. Best regards, Ivan Pavlukhin вс, 26 апр. 2020 г. в 13:18, Ivan Mironovich : > > My name is Ivan Mironovich and I want to contribute.Need access to > Ignite Jira. My us

Re: [DISCUSSION] `static final` code-style constant naming rules

as common as possible in order simplify things for new contributors. I briefly examined code and found some static final ThreadLocals and Atomic variables. Both are not constants. Currently my opinion is that the proposed change can make more harm than profit. Best regards, Ivan Pavlukhin пн, 27

[DISCUSS] Redirect ignite-website GitHub notifications

, Ivan Pavlukhin

Re: [DISCUSS] Redirect ignite-website GitHub notifications

/jira/browse/IGNITE-12965 Best regards, Ivan Pavlukhin ср, 29 апр. 2020 г. в 20:28, Denis Magda : > > Hi Ivan, > > Please open a ticket for INFRA asking to change the notification alias. I > guess that's my fault - confused aliases when was setting up the repo. > > - &g

Re: [DISCUSS] Redirect ignite-website GitHub notifications

Thanks! Best regards, Ivan Pavlukhin пт, 1 мая 2020 г. в 02:02, Denis Magda : > > Ivan, thanks for figuring this out! I've merged the pull-request. > > - > Denis > > > On Wed, Apr 29, 2020 at 11:37 PM Ivan Pavlukhin wrote: > > > Denis, folks, > > >

Re: Check indexes inline size tool

This one is among other features "missing without a good reason" [1]. [1] https://issues.apache.org/jira/browse/IGNITE-11402 Best regards, Ivan Pavlukhin чт, 30 апр. 2020 г. в 17:18, Ilya Kasnacheev : > > Hello! > > I don't think it ever worked. CREATE INDEX has

[DISCUSS] Remove TC badge from README.md

://lists.apache.org/thread.html/r1580e2fb23728e83afbe1bad2b4cf7e9cece0e19a1d305e5755d7dd1%40%3Cdev.ignite.apache.org%3E Best regards, Ivan Pavlukhin

[REVIEW] IGNITE-12980 Use Apache Ignite logo with registered trade mark symbol in README.md

lack of time. Please review. [1] https://issues.apache.org/jira/browse/IGNITE-12980 Best regards, Ivan Pavlukhin

Re: [DISCUSSION] Pull-request checks on GitHub

Maxim, Thanks again for doing great things! Out of curiosity, could you please shed a light why there are 2 travis checks for PR [1]? I am about checks named continuous-integration/travis-ci/pr and continuous-integration/travis-ci/push. Best regards, Ivan Pavlukhin вс, 3 мая 2020 г. в 13:08

Re: [DISCUSSION] Pull-request checks on GitHub

Pavel, > I think this thread is a good opportunity to discuss commit message > guidelines. We had a thread about it recently [1]. [1] https://lists.apache.org/thread.html/rde6e8258537704433286a60e1d0142485c25228a46561544d35b9704%40%3Cdev.ignite.apache.org%3E Best regards, Ivan Pavlukh

Re: [REVIEW] IGNITE-12980 Use Apache Ignite logo with registered trade mark symbol in README.md

Denis, Thank your for the review. Merged to master. Best regards, Ivan Pavlukhin пн, 4 мая 2020 г. в 20:11, Denis Magda : > > Ivan, thanks for the catch. Please go ahead and merge the changes. > > - > Denis > > > On Mon, May 4, 2020 at 12:30 AM Ivan Pavlukhin wrote: >

Re: Using GraalVM instead of standard JVM

Hi, My thoughts: * Does anyone has an idea what prevents us to run Ignite on GraalVM? * Regarding Python. I suppose every JVM can leverage jython [1]. Also I think we should support all significant features on HotSpot as well. [1] https://www.jython.org/ Best regards, Ivan Pavlukhin ср, 6 мая

Re: [DISCUSS] Remove TC badge from README.md

Folks, I created a ticket [1] and prepared PR with magic number =). Please review. [1] https://issues.apache.org/jira/browse/IGNITE-12987 Best regards, Ivan Pavlukhin пн, 4 мая 2020 г. в 10:01, Ivan Pavlukhin : > > Hi Igniters, > > Inspired by a neighbor thread about PR checks [1]

Re: [ANNOUNCE] New PMC member: Maxim Muzafarov

Maxim, My congratulations! Well deserved! P.S. We should mention snapshots for persistent caches in the achievement list. Great job! Best regards, Ivan Pavlukhin чт, 7 мая 2020 г. в 14:47, Dmitriy Pavlov : > > The Project Management Committee (PMC) for Apache Ignite > > has i

Re: Github pull requests are not linked automatically to jira tickets.

Pavel, Thank you for starting this discussion! Controlling all this repo options on our side sounds very attractive. Personally I do not have any arguments about the proposal. Best regards, Ivan Pavlukhin чт, 7 мая 2020 г. в 17:39, Pavel Pereslegin : > > Igniters, > > recent

Re: I want to become contributor

://ignite.apache.org/community/contribute.html Best regards, Ivan Pavlukhin пт, 8 мая 2020 г. в 13:50, Nikita Tolstunov : > > Hello Ignite Community! > I would like to start contributing, could you please add me to contributors > list? My login for https://issues.apache.org/ is Nikita T. > > Thanks!

Re: [DISCUSS] Remove TC badge from README.md

Merged to master. Best regards, Ivan Pavlukhin чт, 7 мая 2020 г. в 19:45, Dmitriy Pavlov : > > IMO, we can remove. This badge does not work since GitHub started to > cache images. Now TC's status .SVG does not work properly. > > чт, 7 мая 2020 г. в 09:25, Ivan Pavlukhin : &g

Re: [DISCUSSION] Pull-request checks on GitHub

to consider switching to "pr" mode? P.S. I found some information about Travis pr/push builds in a documentation [1]. Perhaps it will be useful for someone. [1] https://docs.travis-ci.com/user/pull-requests/#how-pull-requests-are-built Best regards, Ivan Pavlukhin чт, 7 мая 2020 г. в 21

Re: IGNITE-12976: Invalid SQL syntax for NULLS LAST / NULLS FIRST in IgniteQueryGenerator

Hi Mikhail, Thank you in you help with this! I left some comments in JIRA [1]. [1] https://issues.apache.org/jira/browse/IGNITE-12976 Best regards, Ivan Pavlukhin вс, 10 мая 2020 г. в 10:49, Denis Magda : > > Hi Mikhail, > > Thanks for taking care of this. Please check JIRA. Chang

Re: [MTCGA]: new failures in builds [5293839] needs to be handled

Hi Ivan, Could you please take look into a failing test mentioned by bot? Best regards, Ivan Pavlukhin вс, 10 мая 2020 г. в 04:16, : > > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your change

[DISCUSS] TC bot instructions for open source contributors

/confluence/display/IGNITE/How+to+Contribute [3] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Teamcity+Bot#ApacheIgniteTeamcityBot-HowtocheckaPRwiththeTCBot Best regards, Ivan Pavlukhin

[DISCUSS] Apache URL for TC bot

Igniters, As you might know currently TC bot has a domain name in a GridGain domain [1]. What do you think should we assign a name in an Apache domain to the bot? [1] https://mtcga.gridgain.com/ Best regards, Ivan Pavlukhin

Re: Github pull requests are not linked automatically to jira tickets.

Pavel, Thank you! I merged the PR. Let's see that PR linking to JIRA and everything else work fine. Best regards, Ivan Pavlukhin пт, 8 мая 2020 г. в 14:45, Pavel Pereslegin : > > Igniters, > > ticket created [1], please take a look at the proposed changes [2]. > > [1] ht

Re: Github pull requests are not linked automatically to jira tickets.

Pavel, folks, Does anyone have an evidence that PR linking works fine now? I noticed that for a ticket [1] a PR link had not been added automatically. [1] https://issues.apache.org/jira/browse/IGNITE-12994 Best regards, Ivan Pavlukhin пн, 11 мая 2020 г. в 11:55, Ivan Pavlukhin : > >

Re: [DISCUSS] Apache URL for TC bot

Having bot deployed in open/free (and reliable) infrastructure sounds great! One precaution which seems important to me though is avoidance of duplicate (or even controversial) notifications from 2 bots at the same time. Best regards, Ivan Pavlukhin вт, 12 мая 2020 г. в 15:06, Ivan Rakov

Re: [DISCUSS] Data loss handling improvements

Have not chance to read this thread carefully, but a following discussion sounds very similar and might be somehow useful [1]. [1] http://apache-ignite-developers.2346864.n4.nabble.com/Partition-Loss-Policies-issues-td37304.html Best regards, Ivan Pavlukhin чт, 7 мая 2020 г. в 11:36, Alexei

Re: [DISCUSS] Apache URL for TC bot

Yes, it sounds reasonable at the first place to research how much computing power we can get for free. Best regards, Ivan Pavlukhin вт, 12 мая 2020 г. в 16:36, Dmitriy Pavlov : > > Hi Igniters, > > Open clouds for TC Bot sounds really good, but only concern here if there > will be

Re: [DISCUSS] TC bot instructions for open source contributors

What worries me is that the page [1] is quite large. I would love to see a short (and sufficient enough) version for new contributors. [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Best regards, Ivan Pavlukhin вт, 12 мая 2020 г. в 16:41, Dmitriy Pavlov : > >

Re: [ANNOUNCE] New Committer: Taras Ledkov

Congratulations Taras! Hooray! Best regards, Ivan Pavlukhin вт, 12 мая 2020 г. в 19:33, Roman Kondakov : > > Taras, > > congratulations! Keep it up! > > > -- > Kind Regards > Roman Kondakov > > > On 12.05.2020 19:09, Dmitriy Pavlov wrote: > > Hello Ign

Re: [DISCUSS] Apache URL for TC bot

Petr, Ivan, Good stuff! Thank you! Best regards, Ivan Pavlukhin чт, 14 мая 2020 г. в 10:59, Petr Ivanov : > > https://mtcga.ignite.apache.org <https://mtcga.ignite.apache.org/> is set. > > > > On 12 May 2020, at 17:12, Ivan Pavlukhin wrote: > > > > Yes, it

Re: [DISCUSSION] Separate code sanity check and build task

eTests24Java8_BuildApacheIgnite> > > -- > Regards, > Konstantin Orlov > > > -- Best regards, Ivan Pavlukhin

Re: Request for contributors permissions

://ignite.apache.org/community/contribute.html 2020-05-19 18:06 GMT+03:00, Max Timonin : > Hi all, my name is Maksim Timonin, I'm going to contribute to Ignite. > > Could you please grant contributors permissions to *timonin.maksim > *account? > > Regards, > Maksim > -- Best regards, Ivan Pavlukhin

Re: Request for contributors permissions

pers.2346864.n4.nabble.com/IGNITE-6499-Compact-NULL-fields-tp47526.html> > > I would like to contribute to IGNITE-6499. > > Would you mind giving me the right to contribute. > > Thanks in advance > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > -- Best regards, Ivan Pavlukhin

Re: ExecutorServices hide assertions without logging and node stop

we consider catching AssertionErrors as well and treat them as >> > CRITICAL_ERRORS for the Failure Handler? >> > Should we log uncached errors on each of them? >> > >> > >> > The most important list of executor services configured with OOM handler >> > only: >> > execSvc >> > svcExecSvc >> > sysExecSvc >> > p2pExecSvc >> > restExecSvc >> > utilityCacheExecSvc >> > affExecSvc >> > qryExecSvc >> > >> > [1] >> > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPartitionsExchangeFuture.java#L4848 >> > -- Best regards, Ivan Pavlukhin

Re: ExecutorServices hide assertions without logging and node stop

> called but there a lot of cases where it's not. So, I think we must > log errors here or fail the node. > > On Fri, 22 May 2020 at 10:51, Ivan Pavlukhin wrote: >> >> Hi Maxim, >> >> I recently had similar troubles related to ExecutorService and >>

Re: ExecutorServices hide assertions without logging and node stop

. > > If we not enabling catching assertions for ExecutorServices this patch > for all the cases, at least it must be done for all tests running the > TeamCity environment. But I think we should enable fail node if an > error occurs (assume assertions disabled in production). >

Re: [jira] [Created] (IGNITE-13065) Ignite Web Console 2.7.0 not working when scanning cache Error: Cannot read property 'length' of null

onsole been pushed to docker to support > ignite 2.8.0? > > > > thank you > > David > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) > -- Best regards, Ivan Pavlukhin

Re: Ashish Introduction

opportunity to contribute to this > amazing project . Looking forward to hearing from you > > Jira id :- ashishbadri > > Regards > Ashish PB > -- Best regards, Ivan Pavlukhin

Re: Phani Introduction

t; wonderful Ignite community and contribute. My jira user: psadusumilli. > Please let me know if you need any information to add me to the group. > > -- > Thank you > Phani S Adusumilli > -- Best regards, Ivan Pavlukhin

Re: Ignite and Java 9+

do you think? > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > -- Best regards, Ivan Pavlukhin

Re: Ignite and Java 9+

A note. I assumed that we talk about BinaryWriterExImpl.doWriteString. 2020-06-02 12:52 GMT+03:00, Ivan Pavlukhin : > Hi Steve, > > Could you please describe in more details in what cases do you expect > a profit? AFAIK UTF-8 requires 1 byte for Latin-1 characters. > > I did

Re: Incorrect example in Pull Request checklist: comma after ticket name in commit message

de JIRA key and description (example: >> > > "IGNITE-42 >> > > Support CacheLoader and CacheWriter") >> > > - There should be no colon after ticket name. Moreover, this is >> > reinforced >> > > by our commit messages: there 2x as much entries without colon after >> > ticket >> > > name than ones with colon. >> > > >> > > So I propose to change this checklist: >> > > "The following pattern must be used: IGNITE-12407 Add Cluster API >> > > support >> > > to Java thin client" >> > > >> > > WDYT? >> > > >> > > Regards, >> > > -- >> > > Ilya Kasnacheev >> > > -- Best regards, Ivan Pavlukhin

[DISCUSS] Fix confusing "Used by" on GitHub

Use an ASF repository URL in the NPM package config file. 2. Use the GitHub repository URL for maven packages. While with the first option we will see no "Used by", I tend to think that it is a better option. And what do you think? [1] https://github.com/apache/ignite -- Best regards, Ivan Pavlukhin

Re: [DISCUSS] Fix confusing "Used by" on GitHub

at 10:27 PM Ilya Kasnacheev >>> wrote: >>> > >>> > Hello! >>> > >>> > I don't see such a badge. Instead I see "Watch" "Star" "Fork". >>> > >>> > Regards, >>> > -- >>> >

Re: [DISCUSS] Fix confusing "Used by" on GitHub

more than 1,400 dependants on ignite-core module: > https://github.com/apache/ignite/network/dependents?package_id=UGFja2FnZS0xODE0MjIyNzE%3D > > Probably, it's possible to show the stats of ignite-core in the badge but I > don't have access to the repo settings. Ivan, would

Re: Checkpoint refactoring(part of IEP-47)

hat I suggested several tickets instead of one in > the target of simplification of review and find bugs. > > Any objections? > > -- > Best regards, > Anton Kalashnikov > > -- Best regards, Ivan Pavlukhin

Re: [DISCUSSION] New Ignite settings for IGNITE-12438 and IGNITE-13013

ries in three contexts >> (all >> within server nodes). >> >> If this thread is suggesting changing the functional relationship between >> server and client nodes then this may have impacts on our architecture >> and >> implementation that we will need to conside

Re: [DISCUSSION] New Ignite settings for IGNITE-12438 and IGNITE-13013

u are right, everything is as you described. > > There's also a tie breaker when two nodes connect to each other at the > same time. Only one of them will succeed and it depends on internal > discovery order, which you can't control basically. > > пн, 29 июн. 2020 г. в 16:0

Re: Checkstyle fails Build Apache Ignite - can we split it?

n fixing code style issues reporting by the checkstyle plugin? >> >>>> >> >>>> On Mon, 6 Jul 2020 at 19:43, Ilya Kasnacheev < >> ilya.kasnach...@gmail.com >> >>> >> >>>> wrote: >> >>>>> >> >>>>> Hello! >> >>>>> >> >>>>> I have just noticed today that Checkstyle will fail Apache Ignite >> >> build: >> >>>>> >> >>>> >> >> >> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/5443282?buildTab=log&focusLine=3&linesState=683.4289 >> >>>>> >> >>>>> This means that I have completely lost an option to run tests >> >>>>> against >> >>>> pull >> >>>>> requests by new contributors - they usually compile but will not >> >>>>> pass >> >>>>> Checkstyle. That's a blocker. >> >>>>> >> >>>>> Can we please split Checkstyle as a separate build which is >> >>>>> triggered >> >>>> with >> >>>>> Run All? >> >>>>> I think we even have >> >>>>> >> >>>> >> >> >> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle?mode=builds#all-projects >> >>>>> >> >>>>> WDYT? >> >>>>> >> >>>>> Regards, >> >>>>> -- >> >>>>> Ilya Kasnacheev >> >>>> >> >> >> >> >> >> > -- Best regards, Ivan Pavlukhin

Re: Checkstyle fails Build Apache Ignite - can we split it?

r which deserves not pinning but discussion. > > Regards, > -- > Ilya Kasnacheev > > > вт, 7 июл. 2020 г. в 11:50, Ivan Pavlukhin : > >> Folks, >> >> This discussion reoccurs from month to month. Last one I remember is >> [1]. It sounds useful to

Re: Request for contributors permissions

have the rights to create a branch on the github mirror. Thanks > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > -- Best regards, Ivan Pavlukhin

Re: Re[2]: Request for contributors permissions

c=confmacro >> >>Can you point me to what I do wrong? >> >> >> >>-- >>Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > -- Best regards, Ivan Pavlukhin

Re: assign an issue

lowing jira permissions to me > > https://issues.apache.org/jira/browse/IGNITE-13223 > -- Best regards, Ivan Pavlukhin

Re: Re[2]: IGNITE-6499 Compact NULL fields

gt;>branch in the main repository. Am i missing something? >> >>Sorry I probably misread the document but I though that I should fork the >>repo and then pull request as I do not have the rights to create a branch. >> >>Thanks for your help >> >> >>

Re: New committer: Artem Budnikov

most of docs on apacheignite.readme.io. >> >> Being a committer enables easier contribution to the project since it >> makes >> possible to merge your own, or other contributors', changes after the >> review. This should enable better productivity. >> >> On behalf of Apache Ignite PMC, >> > -- Best regards, Ivan Pavlukhin

Re: New Committer: Sergey Chugunov

gt;>> Best Regards, >>> Dmitriy Pavlov >>> on behalf of Apache Ignite PMC >>> P.S. this announce is a little bit overdue, but I guess Sergey's new >>> role >>> was not announced to the community. > > -- Best regards, Ivan Pavlukhin

Re: [RESULT][VOTE] Stop Maintenance of Ignite Web Console

anted with commit rights? > > --- > Alexey Kuznetsov > -- Best regards, Ivan Pavlukhin

Re: Welcome message

. Please, give me access to Jira (my > username is "wirtzleg") > Thank you. > -- Best regards, Ivan Pavlukhin

Re: Getting rid of NONE cache rebalance mode

ctable behavior. >> >> Thanks for your thoughts, >> --AG >> >> [1] >> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist >> [2] >> >> http://apache-ignite-developers.2346864.n4.nabble.com/About-Rebalance-Mode-SYNC-amp-NONE-td47279.html >> > -- Best regards, Ivan Pavlukhin

Re: Getting rid of NONE cache rebalance mode

Alexey, what do you think about the SYNC mode? In my experience, it does >> not add much value as well. I would go as far as removing the >> rebalancingMode parameter altogether (probably in 3.0). >> >> -Val >> >> On Mon, Jul 20, 2020 at 11:09 AM Ivan Pavlukhin &g

Re: [jira] [Updated] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster

> await cache.PutAsync(1, "Test"); >> > Console.WriteLine("Replace"); >> > cache.Replace(1, "Testing"); // Hangs here >> > Console.WriteLine("Wait"); >> > await Task.Delay(Timeout.Infinite); >> > {code} >> > async/await should absolutely not allow any client code to be run from >> stripes. >> >> >> >> -- >> This message was sent by Atlassian Jira >> (v8.3.4#803005) >> > -- Best regards, Ivan Pavlukhin

Re: [jira] [Updated] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster

ticipated any of the jira issues. > I am getting lot emails related to jira. > > How to unsubscribe all. > > On Wed, 22 Jul, 2020, 3:37 pm Ivan Pavlukhin, wrote: > >> Hi Ravikiran C, >> >> JIRA sends emails about issue updates to participants. I guess >> cl

Re: [jira] [Updated] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster

> > > > On Wed, 22 Jul, 2020, 10:40 pm Ivan Pavlukhin, wrote: > >> Hi Ravikiran C, >> >> Could you please provide all "To:" addresses from a particular JIRA >> notification email? >> >> Might it be the case that you are subscribed to

Re: [jira] [Updated] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster

mailto:notifications-unsubscr...@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me. 2020-07-22 21:39 GMT+03:00, Ivan Pavlukhin : > To unsubscribe you need to send any message to > issues-unsubscr...@ignite.apache.org address and follow instructions > sent

Re: PDS suites fail with exit code 137

ose of you, who are into hardcore Linux and C, confirm >> > > > > that >> > the >> > > > > solution can help us? Experiments show that it completely solves >> the >> > > > > problem. >> > > > > - can you please point me to a person who usually does TC >> > maintenance? >> > > > I'm >> > > > > not entirely sure >> > > > > that I can propagate this environment variable to all suites by >> > myself, >> > > > > which is necessary to >> > > > > avoid occasional error 137 (resulted from the same problem) in >> > future. >> > > I >> > > > > just don't know all the >> > > > > details about suites structure. >> > > > > >> > > > > Thank you! >> > > > > >> > > > > [1] >> > > > > >> > > > > >> > > > >> > > >> > >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsIndexing&tab=buildTypeHistoryList&state=failed&branch_IgniteTests24Java8=%3Cdefault%3E >> > > > > [2] >> > > > > >> > > > > >> > > > >> > > >> > >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds4&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E&state=failed >> > > > > [3] https://issues.apache.org/jira/browse/IGNITE-13266 >> > > > > [4] https://issues.apache.org/jira/browse/IGNITE-13263 >> > > > > [5] >> > > > > >> > > > > >> > > > >> > > >> > >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsIndexing&tab=buildTypeHistoryList&branch_IgniteTests24Java8=pull%2F8051%2Fhead >> > > > > >> > > > > -- >> > > > > Sincerely yours, >> > > > > Ivan Bessonov >> > > > > >> > > > >> > > > >> > > > -- >> > > > Sincerely yours, Ivan Daschinskiy >> > > > >> > > >> > > >> > > -- >> > > Sincerely yours, >> > > Ivan Bessonov >> > > >> > >> > >> > -- >> > Sincerely yours, Ivan Daschinskiy >> > >> >> >> -- >> Sincerely yours, >> Ivan Bessonov >> > > > -- > Sincerely yours, Ivan Daschinskiy > -- Best regards, Ivan Pavlukhin

Re: PDS suites fail with exit code 137

; [1] https://issues.apache.org/jira/browse/IGNITE-13266 > > вс, 26 июл. 2020 г. в 17:36, Ivan Pavlukhin : > >> Ivan B., >> >> I noticed that you were able to configure environment variables for >> PDS (Indexing). Do field experiments show that the suggested approach

Re: Getting rid of NONE cache rebalance mode

your idea how rebalancing relates to expiration? > > вт, 21 июл. 2020 г. в 15:59, Ivan Pavlukhin : > >> Alexey, >> >> Thank you for explanation. I feel that I miss a couple bits to >> understand the picture fully. I am thinking about a case which I tend >> to call

Re: [MTCGA]: new failures in builds [5496180, 5496178] needs to be handled

any questions please contact dev@ignite.apache.org > > Best Regards, > Apache Ignite TeamCity Bot > https://github.com/apache/ignite-teamcity-bot > Notification generated at 22:14:21 29-07-2020 > -- Best regards, Ivan Pavlukhin

Re: [MTCGA]: new failures in builds [5552028] needs to be handled

utors were agreed to do > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute >- Should you have any questions please contact dev@ignite.apache.org > > Best Regards, > Apache Ignite TeamCity Bot > https://github.com/apache/ignite-teamcity-bot > Notification generated at 13:59:20 19-08-2020 > -- Best regards, Ivan Pavlukhin

Re: [MTCGA]: new failures in builds [5552028] needs to be handled

Travis gives a green light for a quick fix. 2020-08-19 14:08 GMT+03:00, Ivan Pavlukhin : > Taras, > > Could you please take a look into this? It seems that checkstyle fails > build due to a malicious extra space here > https://github.com/apach

Re: [MTCGA]: new failures in builds [5552028] needs to be handled

A missing link for a previous message https://github.com/apache/ignite/pull/8167 2020-08-19 14:42 GMT+03:00, Ivan Pavlukhin : > Travis gives a green light for a quick fix. > > 2020-08-19 14:08 GMT+03:00, Ivan Pavlukhin : >> Taras, >> >> Could you please take a lo

Re: [MTCGA]: new failures in builds [5552028] needs to be handled

gt; On 19.08.2020 14:42, Ivan Pavlukhin wrote: >> A missing link for a previous message >> https://github.com/apache/ignite/pull/8167 >> >> 2020-08-19 14:42 GMT+03:00, Ivan Pavlukhin : >>> Travis gives a green light for a quick fix. >>> >>> 2020-08-1

Re: Editing rights

ирование, распространение информации, >> содержащейся в >> > > настоящем сообщении, а также осуществление любых действий на основе >> этой >> > > информации, строго запрещено. Если Вы получили это сообщение по >> > > ошибке, >> > > пожалуйста, сообщите об этом отправителю по электронной почте и >> удалите это >> > > сообщение. CONFIDENTIALITY NOTICE: This email and any files attached >> to it >> > > are confidential. If you are not the intended recipient you are >> notified >> > > that using, copying, distributing or taking any action in reliance on >> the >> > > contents of this information is strictly prohibited. If you have >> received >> > > this email in error please notify the sender and delete this email. >> > > >> > >> > -- Best regards, Ivan Pavlukhin

Re: [DISCUSSION] Consistency across java thin/thick APIs

cation for thin-client, but not fully support >> > > JCache. >> > > > For example, we use Cache.Entry for queries and JCache expiration >> > > policies >> > > > in public thin-client API (also, some of JCache interfaces are used >> by >> > > the >> > > > internal implementation). >> > > > >> > > > I've tried to implement POC for continuous queries for java thin >> > client, >> > > > but without JCache support API looks weird. On the one hand, we >> should >> > > use >> > > > CacheEntryEventFilter (JCache interface) since it's required by the >> > > > server-side, on the other hand, we can't use >> CacheEntryUpdatedListener >> > > > since it requires CacheEntryEvent which requires an instance of >> > > > Cache >> > > > (JCache interface), which doesn't exist on the thin-client side. >> > > > >> > > > We have plans to change public API in Ignite 3.0, perhaps it makes >> > sense >> > > to >> > > > make thick and thin API consistent. WDYT? >> > > > What about JCache support by thin-client in Ignite 3.0? >> > > > Please, share your thoughts. >> > > > >> > > > [1]: >> > > > >> > > > >> > > >> > >> http://apache-ignite-developers.2346864.n4.nabble.com/IEP-51-Java-Thin-Client-Async-API-td48900.html >> > > > >> > > >> > >> > > > -- > Best regards, > Alexey > -- Best regards, Ivan Pavlukhin

Re: Editing rights

; >> > On 2020/08/19 18:20:41, Denis Magda wrote: >> > > Yes, I confused JIRA with wiki in the last response. Ivan, thanks for >> > > catching that. >> > > >> > > - >> > > Denis >> > > >> > > >> >

Re: Editing rights

e-moderate your messages. > > - > Denis > > > On Wed, Aug 26, 2020 at 7:35 AM lonsdalel lonsdalel < > eugenezabot...@gmail.com> wrote: > >> Hi, >> >> Could you now give me editing rights for my new account, which is >> eugenezabotkin, e-mail: eu

Re: [DISCUSSION] Maintenance Mode feature

gt;> > Record using Maintenance Mode API exposed via control.{sh|bat} script >> or >> > JMX. >> > 5. On next startup node goes to normal operations as maintenance >> > reason >> > is fixed. >> > >> > >> > I prepared a PR [3] for ticket [1] with draft implementation. It is not >> > ready to be merged to master branch but is already fully functional and >> can >> > be reviewed. >> > >> > Hope you'll share your feedback on the feature and/or any thoughts on >> > implementation. >> > >> > Thank you! >> > >> > [1] https://issues.apache.org/jira/browse/IGNITE-13366 >> > [2] >> > >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47:+Native+persistence+defragmentation >> > [3] https://github.com/apache/ignite/pull/8189 >> >> > -- Best regards, Ivan Pavlukhin

Re: [DISCUSSION] Maintenance Mode feature

ar features please share it >> with >> us. Personally I'm very welcome to any suggestions that make design more >> intuitive and easy-to-use. >> >> Thanks! >> >> [1] >> >> https://github.com/apache/ignite/blob/master/modules/core/src/mai

Re: IEP-54: Schema-first approach for 3.0

> "schema-first approach". To add more clarity, I've started writing the >> IEP >> > for this change: >> > >> > >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach >> > >> > Please take a look and let me know if there are any immediate thoughts, >> > suggestions, or objections. >> > >> > -Val >> > >> > -- Best regards, Ivan Pavlukhin

Re: IEP-54: Schema-first approach for 3.0

> - >> > Denis >> > >> > >> > On Fri, Aug 28, 2020 at 3:50 PM Valentin Kulichenko < >> > valentin.kuliche...@gmail.com> wrote: >> > >> > > Igniters, >> > > >> > > One of the big changes proposed for Ignite 3.0 is the so-called >> > > "schema-first approach". To add more clarity, I've started writing >> > > the >> > IEP >> > > for this change: >> > > >> > > >> > >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach >> > > >> > > Please take a look and let me know if there are any immediate >> > > thoughts, >> > > suggestions, or objections. >> > > >> > > -Val >> > > >> > >> > -- Best regards, Ivan Pavlukhin

Re: [DISCUSSION] Maintenance Mode feature

on of the feature. >> >> >> >> Ignite node is a complex piece of many components interacting with >> >> each >> >> other, they may have different lifecycles and states; states of >> different >> >> components cannot be reduced to the lowest

<    1   2   3   4   5   6   >