Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
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, Кирилл Пушенко
Hi Aleksei,
Thanks for driving the resolution of the ticket. As I see @Taras Ledkov
and @Andrey Mashenkov has
already stepped in as reviewers and I believe they will look at your
changes soon.
-
Denis
On Mon, Mar 16, 2020 at 3:48 AM Aleksei Litsov
wrote:
> Hello Igniters!
>
> I send PR for
Classification: Public
Hi,
I've recently tried to apply Ilya's idea
(https://issues.apache.org/jira/browse/IGNITE-12663) of minimizing thread pools
and tried to set system pool to 3 in my own tests.
It caused deadlock on a client node and I think it can happen not only on such
small pool
Vladimir,
>> We won’t affect existing services
> How exactly will we affect services without special interface? Please see
> the benchmarks in previous email.
I talk about backward compatibility, not about performance. But it
doesn't matter because... see below.
My fault. From discussion I
Artem,
I'll create a ticket for the IGFS docs replacement once we publish the new
website that we'll have all the references needed to create new pages that
will replace the IGFS content.
@Yuriy Gerzhedovich , could you please help
with the SQL questions?
-
Denis
On Mon, Mar 16, 2020 at 12:22
Denis,
I agree with you.
Also I think that we should move to process which will require
documentation updates during work on issue/feature and will part of
code review process. Such approach has some useful benefits:
- Documentation readiness at the same time when fix/implementation is
ready
Nikolay Izhikov created IGNITE-12791:
Summary: [IEP-39] Management API to cancel user provided tasks and
queries - documentation
Key: IGNITE-12791
URL: https://issues.apache.org/jira/browse/IGNITE-12791
Hello, Igniters.
PR [1] for the IEP-39 [2] are ready to be reviewed.
Ticket [3].
Can someone, please, review my changes
I propose to introduce the following features to Ignite management APIs.
1. JMX beans
```
ComputeMXBean#cancel(String sessionId);
QueryMXBean#cacncelSQL(String id)
Hi Denis,
My suggestion is that in the current version release process, when
planning to release a version, first determine the Time, Scope and
ReleaseManager. On this basis, we can add another work of documentation,
which is to determine which documents need to be written and who should
Folks,
I've walked through all the commits to master since 2.8 branch was cut and
filtered some tickets that in my opinion are worth including to 2.8.1
release below (note that they are ready end the effort of including them to
the release should be low as long as there are no implicit
Hello, Alexei!
I agree with you if we may not care about compatibility at all,
then we can solve the problem much more straightforward way.
In your case, the method GridSecurityProcessor#authenticate will have an
implicit contract:
[ if actx.subject() != null then
returns SecurityContext
Thank you!
I have already subscribed.
пн, 16 мар. 2020 г. в 15:00, Ilya Kasnacheev :
> Hello!
>
> The following mailto should subscribe you to this list:
> mailto:dev-subscr...@ignite.apache.org
> ?subject=Subscribebody=Please%20subscribe%20me.
>
> As you can notice, both email and subject are
Hello!
Can you please show an example of that XML (with sensitive information
masked) so that we can understand what is going on?
Thanks,
--
Ilya Kasnacheev
пн, 16 мар. 2020 г. в 00:39, Mahmoud Rashwan :
> Hello,
>
> First of all, please let me thank you for the great tool, we're using it
>
Hello, guys.
I propose myself as a release manager for 2.8.1.
> 16 марта 2020 г., в 14:19, kpushenko написал(а):
>
> Hi, igniters!
>
> I would like to propose a discussion of version 2.9 and scope releases for
> 2020 to another discussion thread.
>
> I understand that there is no objection
Hello!
The following mailto should subscribe you to this list:
mailto:dev-subscr...@ignite.apache.org
?subject=Subscribebody=Please%20subscribe%20me.
As you can notice, both email and subject are different.
Regards,
--
Ilya Kasnacheev
пн, 16 мар. 2020 г. в 14:05, Maksim Stepachev :
> Please
Hi, igniters!
I would like to propose a discussion of version 2.9 and scope releases for
2020 to another discussion thread.
I understand that there is no objection to release 2.8.1.
I support the date from Maxim and dmagda ~ 1 month to May 1.
I offer my help with the release of Ignite 2.8.1. I
Please type it in English.
пн, 16 мар. 2020 г. в 13:28, Кирилл Пушенко :
> --
> С уважением,
> *Кирилл Пушенко*
>
Hello Igniters!
I send PR for ticket: https://issues.apache.org/jira/browse/IGNITE-8152
I fixed all the comments on the ticket. Could you see the solution. If you need
anything else, I am open for suggestions. If everything is ok, please accept
the PR and I will take the next task
--
С уважением,
*Кирилл Пушенко*
Nikolay, specified ticket only describes the mentioned feature. It's not a
ticket of the current proposal.
On 16.03.2020 12:14, Dmitrii Ryabov wrote:
Hello!
Nikolay, yes, but currently, we can't declare user attributes through
control.sh.
пн, 16 мар. 2020 г., 12:06 Nikolay Izhikov :
Hello,
Hello!
Nikolay, yes, but currently, we can't declare user attributes through
control.sh.
пн, 16 мар. 2020 г., 12:06 Nikolay Izhikov :
> Hello, Mikhail.
>
> Can you, please, double-check link to the ticket?
>
> For now it’s a IGNITE-12049 Add user attributes to thin clients which is
> resolved.
Hello, Mikhail.
Can you, please, double-check link to the ticket?
For now it’s a IGNITE-12049 Add user attributes to thin clients which is
resolved.
> 16 марта 2020 г., в 12:04, Mikhail Petrov написал(а):
>
> Hello, Igniters.
>
> I'd like to propose a small improvement in control.sh
Hello, Igniters.
I'd like to propose a small improvement in control.sh configuration,
which is to add the ability to pass parameters needed for cluster
connection via a special properties file located in the same directory
as control.sh script.
The connection parameters in the proposed
Ivan Bessonov created IGNITE-12789:
--
Summary: Tracking page repairing has no WAL record associated with
it
Key: IGNITE-12789
URL: https://issues.apache.org/jira/browse/IGNITE-12789
Project: Ignite
Anton Vinogradov created IGNITE-12788:
-
Summary: Cluster achieved fully rebalanced (PME-free ready) state
metric
Key: IGNITE-12788
URL: https://issues.apache.org/jira/browse/IGNITE-12788
Project:
Can anyone give some details about those missing features so I can
document them?
-Artem
On 15.03.2020 05:31, 18624049226 wrote:
Hi,
I don't know the missing part. Is there any developer willing to add it?
In addition, as far as I know, IGFS and Hadoop accelerator related
components of
27 matches
Mail list logo
