+1 to postpone the spring-tx-ext extension release.
So, the following extensions will be released now:
spring-data-ext
spring-data-2.0-ext
spring-data-2.2-ext
spring-data-commons
performance-statistics-ext
вт, 20 апр. 2021 г. в 14:49, Mikhail Petrov :
>
> Igniters,
>
> Changing the scope of Spri
I checked the modules and there is misnaming issue which I think is critical to
test integration automation on TC.
Can we change maven module names sping-data-2.x-ext to align with directory
name? Currently there is underscore in maven module name, which is hyphen in
directory name.
> On 21 Ap
Taras Ledkov created IGNITE-14610:
-
Summary: BinaryBuilderReader doesn't supports reference (HANDLE)
to collection
Key: IGNITE-14610
URL: https://issues.apache.org/jira/browse/IGNITE-14610
Project: Ig
Alexey Scherbakov created IGNITE-14611:
--
Summary: Implement error handling for public API based on error
codes
Key: IGNITE-14611
URL: https://issues.apache.org/jira/browse/IGNITE-14611
Project: I
I've create the ticket for implementing this [1]
[1] https://issues.apache.org/jira/browse/IGNITE-14611
пт, 16 апр. 2021 г. в 16:30, Alexei Scherbakov :
>
>
> чт, 15 апр. 2021 г. в 18:21, Andrey Mashenkov >:
>
>> Hi Alexey,
>> I like the idea.
>>
>> 1.
>>
>> > TBL-0001 is a *string representa
+1 to formalize extension modules names:
ignite-{directory-name}
The release script has this issue too. It will work fine with that name.
ср, 21 апр. 2021 г. в 10:37, Petr Ivanov :
>
> I checked the modules and there is misnaming issue which I think is critical
> to test integration automation o
Alexey,
As I understand, you suggest ErrorScope enum for easier analysis and it
will be a part of a error code.
But what about String representation?
I think we should use a common prefix for error codes in error messages.
Such codes will be more searchable and as a bonus, vendor-specific.
String
Stanilovsky Evgeny created IGNITE-14612:
---
Summary: Calcite. SELECT with CASE without boolean expression -
fails.
Key: IGNITE-14612
URL: https://issues.apache.org/jira/browse/IGNITE-14612
Project
Hello!
What are the expected use cases for this feature? 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-14606
>
> The concept is
Ilya Kasnacheev created IGNITE-14613:
Summary: Mark CacheConfiguration.rebalanceDelay as deprecated.
Key: IGNITE-14613
URL: https://issues.apache.org/jira/browse/IGNITE-14613
Project: Ignite
Mikhail Petrov created IGNITE-14614:
---
Summary: Add the ability to create security user with custom
options
Key: IGNITE-14614
URL: https://issues.apache.org/jira/browse/IGNITE-14614
Project: Ignite
Mikhail Petrov created IGNITE-14615:
---
Summary: Add support of grant/revoke commands for Ignite security
plugin
Key: IGNITE-14615
URL: https://issues.apache.org/jira/browse/IGNITE-14615
Project: Igni
Mikhail Petrov created IGNITE-14616:
---
Summary: eplace the string variables that store the security
password with array of char.
Key: IGNITE-14616
URL: https://issues.apache.org/jira/browse/IGNITE-14616
Stanilovsky Evgeny created IGNITE-14617:
---
Summary: Calcite. Add opportunity to use NUMERIC in WHEN syntax.
Key: IGNITE-14617
URL: https://issues.apache.org/jira/browse/IGNITE-14617
Project: Ignit
Anton Vinogradov created IGNITE-14618:
-
Summary: Increase stop timeout to 60 seconds
Key: IGNITE-14618
URL: https://issues.apache.org/jira/browse/IGNITE-14618
Project: Ignite
Issue Type:
Andrey,
I've already proposed the similar string representation in the very first
message of the topic.
ср, 21 апр. 2021 г. в 12:31, Andrey Mashenkov :
> Alexey,
>
> As I understand, you suggest ErrorScope enum for easier analysis and it
> will be a part of a error code.
> But what about String
Denis Chudov created IGNITE-14619:
-
Summary: Refactoring of GridDeploymentCommunication
Key: IGNITE-14619
URL: https://issues.apache.org/jira/browse/IGNITE-14619
Project: Ignite
Issue Type: I
Hello!
Were you able to get any traction here?
Apache Ignite 3.0 seems to be in too early stage for packaging, IMHO.
We see very few interest in improving Apache Ignite 2.x packages, anyway.
Regards,
--
Ilya Kasnacheev
ср, 24 февр. 2021 г. в 19:01, Petr Ivanov :
> Hi, Igniters.
>
>
> Sincere
Aleksei,
> The method should always report root cause, in your example it will be
> B-, no matter which module API is called
I may be wrong, but I doubt this will be usable for an end-user. Let's
imagine that the same root exception was raised in different contexts
resulting in two outcomes.
Please wait. I'm watching your review.
вт, 6 апр. 2021 г. в 20:14, Denis Garus :
> Hello, Igniters!
>
> I've raised the PR [1] for the issue [2].
> Could somebody review it?
>
> Suggested implementation
>
> If Ignite Security (IS) is enabled, then executors, accessed through the
> PoolProcessor,
I support the idea. All issues notifications are also sent to
iss...@ignite.apache.org so one can subscribe to this list in order to
track the created tickets. The notifications trash the devlist archive UI
and make it extremely difficult to navigate.
вт, 20 апр. 2021 г. в 18:35, Ilya Kasnacheev :
Hello!
INFRA ticket created: https://issues.apache.org/jira/browse/INFRA-21762
I have asked to keep sending the created issue notifications for
"Contributors 1" role, which is empty at present. So if you wish to keep
getting those e-mails, please add yourself to this role or tell me to do so
for
Hi,
When a container is shared by multiple clusters, then this can be useful
for filtering IPs.
Also, things like VPC based barriers can be circumvented using this
technique.
On Wed, 21 Apr 2021, 15:49 Ilya Kasnacheev,
wrote:
> Hello!
>
> What are the expected use cases for this feature? Can y
Hello, Igniters!
Release pyignite-0.4.0-rc1 has been accepted.
The votes received:
3 "+1" binding votes
2 "+1" votes
There are no "+0" or "-1"
Here the votes received:
- Denis Magda (binding)
- Igor Sapego (binding)
- Anton Vinogradov (binding)
- Ivan Daschinsky
- Alexander Surkov
Link to the
Hi Atri,
Can you describe the scenario in a little more detail? What exactly do you
mean by a container shared by multiple clusters? What are the consequences
of this? How does the proposed solution solve the problem?
Also, I would suggest revisiting the design - I'm not sure such filtering
shoul
Hi Atri,
You've added a new property to a base TcpDiscoveryIpFinder interface.
Actually, the only Azure IpFinder uses this setting, but the others.
This behavior may confuse the users.
Would you mind either making regexp filter setting a part of Azure IpFinder
only or fix other IpFinders as well?
Alexei,
I think it's ok to do error conversion if it makes sense, but better to
preserve the root cause whenever possible.
Another way to solve the described scenario is to introduce something like
checked IgniteRetryAgainException, which forces the user to retry or ignore
it.
It's difficult to fo
Pavel Tupitsyn created IGNITE-14620:
---
Summary: GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is
flaky
Key: IGNITE-14620
URL: https://issues.apache.org/jira/browse/IGNITE-14620
Project: Ignite
Amelchev Nikita created IGNITE-14621:
Summary: Ignite Extensions: change spring-data-*-ext modules names
to align with a directory name
Key: IGNITE-14621
URL: https://issues.apache.org/jira/browse/IGNITE-14621
I have created the issue to fix modules names:
https://issues.apache.org/jira/browse/IGNITE-14621
ср, 21 апр. 2021 г. в 11:46, Nikita Amelchev :
>
> +1 to formalize extension modules names:
> ignite-{directory-name}
>
> The release script has this issue too. It will work fine with that name.
>
>
Hi Val,
Consider a scenario where multiple Ignite clusters are running and for
operational ease (and also compliance, in some cases, e.g. to make
auditing easier), people can configure cloud based IP finders to share
the same container (blob container in Azure, S3 container in AWS etc).
In such a
Hi Andrey,
Thanks for the message. Yes, that is the case since I wanted to show
the functionality to the group first.
Val has made a point about an alternate approach which seems cleaner
to me, so let me explore that. If we go that route, then we will not
need to change at IPFinder level which wi
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 compliance, in some
33 matches
Mail list logo
