[jira] [Created] (IGNITE-11828) Ignite Queue "operationContextPerCall" is set only during the moment of creation

Uday Kale created IGNITE-11828: -- Summary: Ignite Queue "operationContextPerCall" is set only during the moment of creation Key: IGNITE-11828 URL: https://issues.apache.org/jira/browse/IG

[jira] [Created] (IGNITE-11397) Binary mode for Ignite Queue

Uday Kale created IGNITE-11397: -- Summary: Binary mode for Ignite Queue Key: IGNITE-11397 URL: https://issues.apache.org/jira/browse/IGNITE-11397 Project: Ignite Issue Type: New Feature

Re: Volunteer needed: AWS Elastic Load Balancer IP Findersimplemented

in the Javadoc of TcpDiscoveryElbIpFinder that it is for the > Classic Load Balancers > 2) Make sure that Javadocs of TcpDiscoveryElbIpFinder and > TcpDiscoveryAlbIpFinder have > each other in “@see” tags > 3) Make sure both are described and clearly distinguished at readme.io > >

Re: Volunteer needed: AWS Elastic Load Balancer IP Findersimplemented

have to extend the existing TcpDiscoveryElbIpFinder – maybe we > could merge them, but let’s not be > stuck on this any longer. > Also let’s not change the existing TcpDiscoveryElbIpFinder – no need to > rename it or deprecate it. We can thing of the > two IpFinders as of just independent

Re: Volunteer needed: AWS Elastic Load Balancer IP Findersimplemented

> I've updated checklist, thank you for pointing to this. > > So I suggest keeping existing naming of TcpDiscoveryElbIpFinder as it is > part of API. > > Sincerely, > Dmitriy Pavlov > > вт, 2 окт. 2018 г. в 21:04, uday kale : > > > Thanks for the review Sta

Re: Volunteer needed: AWS Elastic Load Balancer IP Findersimplemented

Thanks for the review Stan. I renamed the existing class TcpDiscoveryElbIpFinder since the name is not clear regarding the actual load balancer being used. The names TcpDiscoveryClassicElbIpFinder and TcpDiscoveryApplicationElbIpFinder provide a clear distinction. I deprecated the existing class be

[jira] [Created] (IGNITE-9532) Binary mode for Ignite Queue

Uday Kale created IGNITE-9532: - Summary: Binary mode for Ignite Queue Key: IGNITE-9532 URL: https://issues.apache.org/jira/browse/IGNITE-9532 Project: Ignite Issue Type: New Feature

Re: Access to change jira status

Thanks Valentin On Fri, Jun 29, 2018 at 4:15 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Uday, > > I added you to contributors list, you should be able to assign the ticket > to yourself now. Welcome to the community! > > -Val > > On Fri, Jun

Access to change jira status

Hi, I am unable to change the jira status of IGNITE-1260 or assign it to myself. Can someone grant me the necessary permissions. My jira user name is: uday. Regards, Uday

[jira] [Created] (IGNITE-8617) Node Discovery Using AWS Application ELB

Uday Kale created IGNITE-8617: - Summary: Node Discovery Using AWS Application ELB Key: IGNITE-8617 URL: https://issues.apache.org/jira/browse/IGNITE-8617 Project: Ignite Issue Type: New Feature

Re: Request for contributors permissions

Thanks Denis On Mon, May 21, 2018 at 10:46 PM Denis Magda wrote: > Thanks for the details. Please go ahead and implement it if you'd like. > > -- > Denis > > On Sat, May 19, 2018 at 3:42 AM, uday kale wrote: > > > The ELB discovery currently supports cla

Re: Request for contributors permissions

ased discovery, is it the same as this > type of ELB discovery already supported by Ignite? > > https://apacheignite-mix.readme.io/docs/amazon-aws#amazon-elb-based-discovery > > > > On Fri, May 18, 2018 at 8:48 AM, uday kale wrote: > > > Hi, > > > > My

Request for contributors permissions

Hi, My name is Uday Kale. Username: *uday*. I want to add support for Node discovery through AWS Application ELB Target Group. Best Regards, Uday