[jira] [Created] (IGNITE-14270) Remove "project" param from Ducktape Specs.

[Maksim Timonin (Jira)]

Maksim Timonin created IGNITE-14270:
---

 Summary: Remove "project" param from Ducktape Specs.
 Key: IGNITE-14270
 URL: https://issues.apache.org/jira/browse/IGNITE-14270
 Project: Ignite
  Issue Type: Task
Reporter: Maksim Timonin


Currently IgniteSpec supports param "project" that actually is useless. Should 
be removed to avoid misunderstandings of how to use custom build of Ignite with 
ducktape tests.

Also it's required to review other places that this param is used and verify it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14269) Design conditional multi update functionality for meta storage client

[Andrey N. Gura (Jira)]

Andrey N. Gura created IGNITE-14269:
---

 Summary: Design conditional multi update functionality for meta 
storage client
 Key: IGNITE-14269
 URL: https://issues.apache.org/jira/browse/IGNITE-14269
 Project: Ignite
  Issue Type: New Feature
Reporter: Andrey N. Gura
Assignee: Andrey N. Gura
 Fix For: 3.0.0-alpha2


Define entities required for implementation of conditional multi updates (aka 
"transactions") for meta storage.

Requirements:

- Design should provide possibility to define conditional updates in 
if-then-else manner with nested branches.
- Update always starts with condition.
- Any nested branch must start with condition. 
- Update can't precede to condition.
- Every branch can yield exactly one custom result (limited by number of simple 
types) and any number of entries. Corresponding expression always must be at 
the end of branch.
- Condition for entry revision allows the following comparisons: equal, !equal, 
less, greater.
- Condition for entry value allows the following operations (byte-wise): equal, 
!equal.
- Update allows the following operations: put, remove, no-op.
- Condition can not use previously defined condition instance again because it 
will lead to graph cycle and infinite update execution.

Assumptions:

- It seems that conditions and updates entities can be conveniently linked 
using chaining.

Simple example (pseudocode):

{code}
CompletableFuture> = invoke(valCond(EQUAL, 
perstEnabled, true)._then(
 valCond(EQUAL, walEnabled, true)._then(
 update(walEnabled, true)).
 _else(
 update(walEnabled, false))
)._else(NoopUpdate))

{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 *New test failure in master-nightly 
IgniteDbMemoryLeakWithExpirationTest.testMemoryLeak 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7435431350780563606=%3Cdefault%3E=testDetails
 No changes in the build

 - Here's a reminder of what contributors 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 07:25:23 03-03-2021 

Re: Hello

[Denis Magda]

Hello Michele,

Welcome to the community! I've added you to the contributors' list in JIRA,
so go ahead and take over a ticket you're interested in:
https://ignite.apache.org/community/contribute.html

Speaking about Java vs Python contributions, we've been improving the Python
thin client

actively and looking for contributors with Python skills. Is Python OK for
you or you prefer to focus on Java?

Also, do you have any previous experience with Ignite?


-
Denis


On Tue, Mar 2, 2021 at 1:55 PM Michele Caputo  wrote:

> Hello everyone,
>
>
> My name is Michele Caputo and I would like to contribute to the Apache
> Ignite project.
> I am a Software Engineer, in my previous experience I worked as a full
> stack developer from IoT to frontend. My preference was definitely for the
> backend (experience in C#), DB (Oracle, SQL Server) and IoT (Java ME) parts.
>
> In my current job I am more into Data Engineering, but I can’t hide I’m
> missing some ol’  good coding, so I would like to make use of my experience
> in combination with my passion for Software Engineering :)
>
> I know some python and I am keen to improve my Java skills.
>
> I hope I covered the points in the “contribute" page for Ignite and if I
> didn’t… Well I’m just new to ASF and I will learn :)
> As requested I already opened an ASF JIRA account and my JIRA ID is
> mikap83, I hope I can start to contribute soon!
>
> Thank you!
> Michele

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

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 *Test with high flaky rate in master 
TxWithKeyContentionSelfTest.testOptimisticRepeatableReadCheckContentionTxMetricNear
 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8663336740813570408=%3Cdefault%3E=testDetails
 No changes in the build

 - Here's a reminder of what contributors 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 02:25:23 03-03-2021 

Hello

[Michele Caputo]

Hello everyone,


My name is Michele Caputo and I would like to contribute to the Apache Ignite 
project.
I am a Software Engineer, in my previous experience I worked as a full stack 
developer from IoT to frontend. My preference was definitely for the backend 
(experience in C#), DB (Oracle, SQL Server) and IoT (Java ME) parts.

In my current job I am more into Data Engineering, but I can’t hide I’m missing 
some ol’  good coding, so I would like to make use of my experience in 
combination with my passion for Software Engineering :) 

I know some python and I am keen to improve my Java skills.

I hope I covered the points in the “contribute" page for Ignite and if I 
didn’t… Well I’m just new to ASF and I will learn :)
As requested I already opened an ASF JIRA account and my JIRA ID is mikap83, I 
hope I can start to contribute soon!

Thank you!
Michele

[jira] [Created] (IGNITE-14268) [Ignite Website] Content updates 2021-03-02

[Kseniya Romanova (Jira)]

Kseniya Romanova created IGNITE-14268:
-

 Summary: [Ignite Website] Content updates 2021-03-02
 Key: IGNITE-14268
 URL: https://issues.apache.org/jira/browse/IGNITE-14268
 Project: Ignite
  Issue Type: Task
  Components: website
Reporter: Kseniya Romanova


Please update the following pages with new information:

*1. The text banner on the top of the website*

Please change the past meetup for the upcoming:

April 13, 2021: Using Ignite and JBoss Drools to Implement a Complex Event 
Processing Solution 
[https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276693067/]

 

*2. Events Schedule* [https://ignite.apache.org/events.html]

Please update the page. New events:

*How to use Apache Ignite and Spring to build a reliable distributed web 
application*

Webinar, Semyon Danilov

March 17, 2021

Spring is a popular framework, and Apache Ignite is a fast layer for data 
storage. Adding Ignite enables you to manage http sessions, cache-application 
data, and so on. During this 1.5 hour session, Semyon uses the Spring framework 
to create a simple web application and demonstrates how Apache Ignite can 
empower the application. 

[https://www.gridgain.com/resources/webinars/how-use-apache-ignite-and-spring-build-reliable-distributed-web-application]
 

 

*Using Ignite and JBoss Drools to Implement a Complex Event Processing Solution*

Virtual Apache Ignite Meetup, Manoel Pereira de Lima Junior & Ney Luiz Montes 
Junior 

April 13, 2021

In this talk, we describe and show how to use Apache Ignite and JBoss Drools to 
design a complex event processing (CEP) solution. The solution processes and 
correlates millions of events per second from a publish/subscribe message 
broker and another kind of events streamer. The CEP solution that we 
demonstrate has a microservices architecture with real-time automation of 
CI/CD. We show how we have used this highly scalable CEP microservices 
ecosystem since 2018 to support a digital-service and marketing platform for 
one of the largest banks in Brazil.

[https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276693067/] 

 

*3. List of Committers and PMC members update*

[https://ignite.apache.org/community/resources.html#people]

Artem Budnikov, Igor Seliverstov, Ivan Rakov are not with GridGain anymore :( 
Please make the company blank for them at the moment



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14267) Cluster snapshot must support encrypted caches

[Maxim Muzafarov (Jira)]

Maxim Muzafarov created IGNITE-14267:


 Summary: Cluster snapshot must support encrypted caches
 Key: IGNITE-14267
 URL: https://issues.apache.org/jira/browse/IGNITE-14267
 Project: Ignite
  Issue Type: Improvement
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
 Fix For: 2.11


Currently, the snapshot procedure doesn't support taking a cluster snapshot for 
caches with enabled encryption. We should support such a feature, so the user 
will be able to create and restore for such snapshots.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Adding metrics of using WAL archive

[Nikolay Izhikov]

+1 For this.

> 2 марта 2021 г., в 18:32, ткаленко кирилл  написал(а):
> 
> Hi, Nikolay!
> 
> I thought about your proposal and offer the following two metrics:
> 
> 1)The number of bytes logged to the WAL;
> 2)The number of compressed bytes in the WAL.
> 
> Monotonically increasing long.
> 
> WDYT?

Re: Allow arrays in node attributes for thin clients

[Alex Kozhenkov]

OK, I got it.
Yes, we can use String instead.

вт, 2 мар. 2021 г. в 18:27, Pavel Tupitsyn :

> I think we agreed to make thin client attributes String-only [1]
> However, this does not seem to be the case right now.
>
> Anyway, I'd like to avoid complicating the protocol even further with magic
> suffixes.
> Can we simply use a String instead of an array?
>
> [1]
>
> http://apache-ignite-developers.2346864.n4.nabble.com/Add-user-attributes-to-thin-clients-td45273.html
>
> On Tue, Mar 2, 2021 at 4:04 PM Alex Kozhenkov  wrote:
>
> > Hi guys!
> >
> > We have a restriction to filter array values from node attributes if it
> is
> > not "org.apache.ignite.features" (GridTopologyCommandHandler.java:313).
> >
> > It will be useful to allow arrays for any attribute with suffix
> ".features"
> > for external modules. Otherwise, these attributes are not allowed from
> > GridClient.
> >
> > What do you think about allowing it?
> >
>

Adding metrics of using WAL archive

[ткаленко кирилл]

Hi, Nikolay!

I thought about your proposal and offer the following two metrics:

1)The number of bytes logged to the WAL;
2)The number of compressed bytes in the WAL.

Monotonically increasing long.

WDYT?

Re: Allow arrays in node attributes for thin clients

[Pavel Tupitsyn]

I think we agreed to make thin client attributes String-only [1]
However, this does not seem to be the case right now.

Anyway, I'd like to avoid complicating the protocol even further with magic
suffixes.
Can we simply use a String instead of an array?

[1]
http://apache-ignite-developers.2346864.n4.nabble.com/Add-user-attributes-to-thin-clients-td45273.html

On Tue, Mar 2, 2021 at 4:04 PM Alex Kozhenkov  wrote:

> Hi guys!
>
> We have a restriction to filter array values from node attributes if it is
> not "org.apache.ignite.features" (GridTopologyCommandHandler.java:313).
>
> It will be useful to allow arrays for any attribute with suffix ".features"
> for external modules. Otherwise, these attributes are not allowed from
> GridClient.
>
> What do you think about allowing it?
>

[jira] [Created] (IGNITE-14266) System views for page statistics must include the bucktes sizes

[Maxim Muzafarov (Jira)]

Maxim Muzafarov created IGNITE-14266:


 Summary: System views for page statistics must include the bucktes 
sizes
 Key: IGNITE-14266
 URL: https://issues.apache.org/jira/browse/IGNITE-14266
 Project: Ignite
  Issue Type: Improvement
Reporter: Maxim Muzafarov
 Fix For: 2.11


Affected system views: CACHE_GROUP_PAGE_LISTS, DATA_REGION_PAGE_LISTS

The bucket index corresponds to the interval of free space on pages it 
contains. We must add this info to the system views.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Allow arrays in node attributes for thin clients

[Alex Kozhenkov]

Hi guys!

We have a restriction to filter array values from node attributes if it is
not "org.apache.ignite.features" (GridTopologyCommandHandler.java:313).

It will be useful to allow arrays for any attribute with suffix ".features"
for external modules. Otherwise, these attributes are not allowed from
GridClient.

What do you think about allowing it?

[jira] [Created] (IGNITE-14265) Python thin: Support passwords for certificates

[Igor Sapego (Jira)]

Igor Sapego created IGNITE-14265:


 Summary: Python thin: Support passwords for certificates 
 Key: IGNITE-14265
 URL: https://issues.apache.org/jira/browse/IGNITE-14265
 Project: Ignite
  Issue Type: Bug
  Components: python, thin client
Affects Versions: python-0.3.4
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: python-0.4.0


Need to add support for certfiles with passwords.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14264) Ignite extensions: Ignite client cache manager may create cache with incorrect name

[Mikhail Petrov (Jira)]

Mikhail Petrov created IGNITE-14264:
---

 Summary: Ignite extensions: Ignite client cache manager may create 
cache with incorrect name  
 Key: IGNITE-14264
 URL: https://issues.apache.org/jira/browse/IGNITE-14264
 Project: Ignite
  Issue Type: Bug
Reporter: Mikhail Petrov
Assignee: Mikhail Petrov
 Attachments: image-2021-03-02-13-43-04-186.png

During concurrent  cache creation and calling getDynamicCacheConfiguration by 
IgniteClientCacheManager it is possible that the cache name will not be set 
correctly. To solve this problem, it is suggested to copy the dynamic cache 
configuration every time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)