Re: Migrating NodeJS client to TypeScript

[Pavel Tupitsyn]

Semyon,

Fully agree, TypeScript is the way to go.

> full rewrite
I would not call it a "full rewrite", because TypeScript is a superset of
JavaScript.

1. Converting to TypeScript mostly means adding type annotations and
tweaking the code, not rewriting it from scratch
2. The conversion can be gradual

On Tue, Dec 1, 2020 at 9:59 AM Ivan Daschinsky  wrote:

> > Is there any value in keeping both versions - the plain JavaScript one
> and the TypeScript specific
> Hi! No, there is no value. TS sources should be transpiled to JS before
> execution.
>
> вт, 1 дек. 2020 г. в 01:31, Denis Magda :
>
> > Hi Semyon,
> >
> > Is there any value in keeping both versions - the plain JavaScript one
> and
> > the TypeScript specific?
> >
> > -
> > Denis
> >
> >
> > On Mon, Nov 30, 2020 at 12:16 PM Данилов Семён 
> wrote:
> >
> > > Hello Igniters!
> > >
> > > I'd like to propose a big change for the nodejs thin client: a full
> > > rewrite from JavaScript to TypeScript.
> > >
> > > Strong typing will not only help us in future while developing new
> > > features, but will also indicate existing type inconsistencies (I know
> > > there is a couple).
> > > Also, we will have out of the box types for API documentation, which is
> > > very handy for users.
> > >
> > > So what do you think?
> > >
> > > Kind regards,
> > > Semyon.
> > >
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

[jira] [Created] (IGNITE-13785) Calcite improvements. Support CREATE TABLE and INSERT through h2 engine, for test purposes.

[Stanilovsky Evgeny (Jira)]

Stanilovsky Evgeny created IGNITE-13785:
---

 Summary: Calcite improvements. Support CREATE TABLE and INSERT 
through h2 engine, for test purposes.
 Key: IGNITE-13785
 URL: https://issues.apache.org/jira/browse/IGNITE-13785
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Affects Versions: 2.9
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny


For the test purposes we need to have a possibility to *create* and *insert* 
using h2 engine. 



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

Re: Migrating NodeJS client to TypeScript

[Ivan Daschinsky]

> Is there any value in keeping both versions - the plain JavaScript one
and the TypeScript specific
Hi! No, there is no value. TS sources should be transpiled to JS before
execution.

вт, 1 дек. 2020 г. в 01:31, Denis Magda :

> Hi Semyon,
>
> Is there any value in keeping both versions - the plain JavaScript one and
> the TypeScript specific?
>
> -
> Denis
>
>
> On Mon, Nov 30, 2020 at 12:16 PM Данилов Семён  wrote:
>
> > Hello Igniters!
> >
> > I'd like to propose a big change for the nodejs thin client: a full
> > rewrite from JavaScript to TypeScript.
> >
> > Strong typing will not only help us in future while developing new
> > features, but will also indicate existing type inconsistencies (I know
> > there is a couple).
> > Also, we will have out of the box types for API documentation, which is
> > very handy for users.
> >
> > So what do you think?
> >
> > Kind regards,
> > Semyon.
> >
>


-- 
Sincerely yours, Ivan Daschinskiy

[jira] [Created] (IGNITE-13784) List of modules should indicate which modules are currently installed

[Valentin Kulichenko (Jira)]

Valentin Kulichenko created IGNITE-13784:


 Summary: List of modules should indicate which modules are 
currently installed
 Key: IGNITE-13784
 URL: https://issues.apache.org/jira/browse/IGNITE-13784
 Project: Ignite
  Issue Type: Sub-task
Reporter: Valentin Kulichenko


The {{module list}} command shows which optional Ignite modules are available 
and can be used. But there is no way to know which ones are already installed. 
It would be useful to have some sort of marker in the table indicating that.



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

[jira] [Created] (IGNITE-13783) Prevent starting nodes with the same consistent ID

[Valentin Kulichenko (Jira)]

Valentin Kulichenko created IGNITE-13783:


 Summary: Prevent starting nodes with the same consistent ID
 Key: IGNITE-13783
 URL: https://issues.apache.org/jira/browse/IGNITE-13783
 Project: Ignite
  Issue Type: Sub-task
Reporter: Valentin Kulichenko


Currently, it is possible to start two or more nodes with the same consistent 
ID. Trying to stop using that ID succeeds for all the nodes, but an error 
appears in the output: {{Stop of node n1 was failed}}.

Here is the full output:
{noformat}
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node start 
n1
Started ignite node.
PID: 40644
Consistent Id: n1
Log file: /Users/vkulichenko/GridGain/cli-demo/ignite-work/n1.log
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node start 
n1
Started ignite node.
PID: 40648
Consistent Id: n1
Log file: /Users/vkulichenko/GridGain/cli-demo/ignite-work/n1.log
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node list
+---+---+-+
| PID   | Consistent Id | Log   
  |
+---+---+-+
| 40644 | n1| 
/Users/vkulichenko/GridGain/cli-demo/ignite-work/n1.log |
+---+---+-+
| 40648 | n1| 
/Users/vkulichenko/GridGain/cli-demo/ignite-work/n1.log |
+---+---+-+
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node stop n1
Stop of node n1 was failed
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node list
No running nodes
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ 
{noformat}

We should have a mechanism that prevents starting multiple nodes with the same 
ID.



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

Re: Website related tickets on JIRA

[Denis Magda]

Hi Mauricio,

Glad to receive a note from you. The community needs to know its heroes ;)

I've used your advice and labeled some important tasks appropriately. As
you might have noticed, the community voted to define Ignite as a
distributed database. Which means there are some tasks for the two of us :)
Hope you have time to contribute the changes:
https://issues.apache.org/jira/browse/IGNITE-13779

-
Denis


On Mon, Nov 30, 2020 at 10:44 AM Mauricio Stekl  wrote:

> Hi Ignite Community,
> For those of you who do not know me, my name is Mauricio and I have been
> doing contributions related to the website for a long time now. Generally I
> have coordinated these updates directly with some community members.
> However, for future contributions I would like to see if it is possible to
> start creating tickets on JIRA using the 'website' component. This will
> help me to better organize the tasks where I can contribute, and, of
> course, it will help us all track what is going on around the website.
>
> Please let me know if you have any questions or suggestions. Otherwise I
> look forward to seeing those tickets on JIRA.
>
>
> Thanks.
>
> Mauricio
>

[jira] [Created] (IGNITE-13782) [CLI Tool] Manual folder removal causes exceptions

[Valentin Kulichenko (Jira)]

Valentin Kulichenko created IGNITE-13782:


 Summary: [CLI Tool] Manual folder removal causes exceptions
 Key: IGNITE-13782
 URL: https://issues.apache.org/jira/browse/IGNITE-13782
 Project: Ignite
  Issue Type: Bug
Reporter: Valentin Kulichenko


# Run {{ignite init}}
 # Delete {{ignite-bin}} and {{ignite-work}} folders
 # Run {{ignite node start n1}}

Steps result in the following exception:
{nofomat}
Exception in thread "main" java.lang.RuntimeException: 
java.nio.file.NoSuchFileException: 
/Users/vkulichenko/GridGain/cli-demo/ignite-bin/2.9.0/cli
at 
org.apache.ignite.internal.v2.builtins.SystemPathResolver.list(SystemPathResolver.java:39)
at 
org.apache.ignite.internal.v2.spec.IgniteCliSpec.loadSubcommands(IgniteCliSpec.java:81)
at 
org.apache.ignite.internal.v2.spec.IgniteCliSpec.lambda$main$0(IgniteCliSpec.java:64)
at java.base/java.util.Optional.ifPresent(Optional.java:176)
at 
org.apache.ignite.internal.v2.spec.IgniteCliSpec.main(IgniteCliSpec.java:64)
Caused by: java.nio.file.NoSuchFileException: 
/Users/vkulichenko/GridGain/cli-demo/ignite-bin/2.9.0/cli
at 
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at 
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at 
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
at 
java.base/sun.nio.fs.UnixFileSystemProvider.newDirectoryStream(UnixFileSystemProvider.java:412)
at java.base/java.nio.file.Files.newDirectoryStream(Files.java:476)
at java.base/java.nio.file.Files.list(Files.java:3765)
at 
org.apache.ignite.internal.v2.builtins.SystemPathResolver.list(SystemPathResolver.java:28)
... 4 more
{nofomat}

{{ignite init}} fails with the same exception as well, so the only way to fix 
this is to manually delete the {{.ignitecfg}} file, which the user is not aware 
of.

We should have the support for re-initialization, and suggest to do that in 
case the described scenario occures.



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

Re: [VOTE] Define Apache Ignite as a Distributed Database

[Denis Magda]

The vote is closed with results shared in a separate email:
http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50391.html

Thanks to everyone who cast the vote!

@Stephen Darlington , your point about the
compute APIs importance is valid. Those capabilities will be featured at
the top of the main page. I'll draft a text for that section
(High-Performance Compute Cluster) and will appreciate if you share your
thoughts in this ticket: https://issues.apache.org/jira/browse/IGNITE-13780

-
Denis


On Tue, Nov 24, 2020 at 1:34 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:

> -1
>
> I think the compute APIs are an important part of Ignite’s value. Calling
> it a database diminishes that in my opinion.
>
> > On 24 Nov 2020, at 08:40, Ivan Pavlukhin  wrote:
> >
> > +1
> >
> > 2020-11-24 11:33 GMT+03:00, Anton Vinogradov :
> >> +1
> >>
> >> On Tue, Nov 24, 2020 at 10:24 AM Pavel Tupitsyn 
> >> wrote:
> >>
> >>> +1
> >>>
> >>> On Tue, Nov 24, 2020 at 3:25 AM Saikat Maitra  >
> >>> wrote:
> >>>
>  +1
> 
>  On Mon, Nov 23, 2020 at 4:55 PM Valentin Kulichenko <
>  valentin.kuliche...@gmail.com> wrote:
> 
> > +1
> >
> > On Mon, Nov 23, 2020 at 2:44 PM Denis Magda 
> > wrote:
> >
> >> Igniters,
> >>
> >> With this vote, I'd like to formally wrap up our discussion on
> >>> defining
> >> Ignite as a "distributed database" instead of an "in-memory
> >>> computing"
> >> platform. See the following discussion for the rationale and
> >> context:
> >>
> >>
> >
> 
> >>>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Renaming-Ignite-s-product-category-td49246.html
> >>
> >> If the vote passes, the website will define Ignite as "a
> >> distributed
> >> database for in-memory speed at petabyte scale" to underscore our
> > in-memory
> >> origins (and the primary reason why the project is selected) but
> >> not
> >> diminishing our persistence capabilities. All prominent use cases
> >>> such
>  as
> >> caching, high-performance computing, etc. will remain visible on
> >> the
> >> website. There is nothing wrong if a distributed database is used
> >> as
> >>> a
> >> cache or high-performance compute cluster; it's up to an
> >> application
> >> developer to decide.
> >>
> >> Overall, please cast your vote for defining Ignite as a
> >> "distributed
> >> database":
> >> +1 - support the change
> >> -1 - disagree with the change, explain why
> >> 0 - neutral
> >>
> >> This is a majority vote that is open for the next 7 days and to be
>  closed
> >> on Monday, Nov 30th:
> >> https://www.timeanddate.com/countdown/to?year=2020=11=30
> >>
> >> -
> >> Denis
> >>
> >
> 
> >>>
> >>
> >
> >
> > --
> >
> > Best regards,
> > Ivan Pavlukhin
>
>
>

[RESULT][VOTE] Define Apache Ignite as a Distributed Database

[Denis Magda]

The community held a majority vote on defining Apache Ignite as a
"distributed database":
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html

The results are as follows:
[+1] - 5 votes
[-1] - 1 vote
[0] - 0 votes

The majority voted to define Ignite as a distributed database, and the
changes will be rolled out in the coming days.
https://issues.apache.org/jira/browse/IGNITE-13779

-
Denis

[jira] [Created] (IGNITE-13781) Ignite Website: rework Ignite features section

[Denis A. Magda (Jira)]

Denis A. Magda created IGNITE-13781:
---

 Summary: Ignite Website: rework Ignite features section
 Key: IGNITE-13781
 URL: https://issues.apache.org/jira/browse/IGNITE-13781
 Project: Ignite
  Issue Type: Sub-task
  Components: website
Reporter: Denis A. Magda
Assignee: Mauricio Stekl


Presently, the features section introduces a distinguishing capability of 
Ignite with a short paragraph. This is enough for the SEO but not for a 
developer who came to the website from a Google search result and hopes to 
learn more details on the main page.

The features section needs to be reworked as follows (see a sketch attached):
* Top-5 features are arranged in stacked blocks to the left of the section. The 
right part of the section covers details about a selected feature.
* Once a feature is selected, the right part of the section is updated with the 
feature details.
* The feature details include a short paragraph about the feature, a code 
snippet showing how to use or activate the feature, the Learn More button that 
navigates to a dedicated feature page.
* The code snippets section needs to support Java, C#, C++, Python, Node.JS, 
SQL, XML, YAML syntaxes. A single code snippet can consist of multiple tabs 
(for instance, one tab is for Java while the other is for Python).

Check the *A full-stack data platform, from the creators of Apache Druid* 
section of Imply's main page to get a sense of how the section can look like:
https://imply.io



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

[jira] [Created] (IGNITE-13780) Ignite Website: update use cases section

[Denis A. Magda (Jira)]

Denis A. Magda created IGNITE-13780:
---

 Summary: Ignite Website: update use cases section
 Key: IGNITE-13780
 URL: https://issues.apache.org/jira/browse/IGNITE-13780
 Project: Ignite
  Issue Type: Sub-task
  Components: website
Reporter: Denis A. Magda
Assignee: Denis A. Magda


Presently, the website introduces 2 use cases of Ignite - "Ignite as a cache" 
and "Ignite as a digital integration hub". After defining Ignite as a 
distributed database, we need to update this website section featuring the 
following 3 primary usage scenarios of Ignite.

*How Most Developers Use Apache Ignite*

_Applications Acceleration & Data Caching_

Gain up to 100x acceleration for existing applications using Ignite as an 
in-memory cache over a single or multiple backend systems. The cache that you 
can query with SQL, transact and compute on. 

*Distributed Database for Mixed Workloads*

Store and process petabytes of operational and historical data using Ignite as 
a distributed database for mixed workloads. The database that scales up and out 
across available memory, disk, and Intel Optane storage. 

_High-Performance Compute Cluster_

Deploy and execute your kilobyte-size code over petabytes of data. Turn your 
Ignite cluster into a limitless supercomputer for low-latency calculations, 
complex analytics, and machine learning. 



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

[jira] [Created] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes

[Denis A. Magda (Jira)]

Denis A. Magda created IGNITE-13779:
---

 Summary: Ignite as Distributed Database: Required Website Changes
 Key: IGNITE-13779
 URL: https://issues.apache.org/jira/browse/IGNITE-13779
 Project: Ignite
  Issue Type: Task
Reporter: Denis A. Magda


The community 
[voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html]
 to define Ignite as a distributed database.

This is an umbrella ticket with all required website changes.



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

Re: Migrating NodeJS client to TypeScript

[Denis Magda]

Hi Semyon,

Is there any value in keeping both versions - the plain JavaScript one and
the TypeScript specific?

-
Denis


On Mon, Nov 30, 2020 at 12:16 PM Данилов Семён  wrote:

> Hello Igniters!
>
> I'd like to propose a big change for the nodejs thin client: a full
> rewrite from JavaScript to TypeScript.
>
> Strong typing will not only help us in future while developing new
> features, but will also indicate existing type inconsistencies (I know
> there is a couple).
> Also, we will have out of the box types for API documentation, which is
> very handy for users.
>
> So what do you think?
>
> Kind regards,
> Semyon.
>

[jira] [Created] (IGNITE-13778) Fix discovery tests for ducktape

[Sergei Ryzhov (Jira)]

Sergei Ryzhov created IGNITE-13778:
--

 Summary: Fix discovery tests for ducktape
 Key: IGNITE-13778
 URL: https://issues.apache.org/jira/browse/IGNITE-13778
 Project: Ignite
  Issue Type: Task
Reporter: Sergei Ryzhov
Assignee: Sergei Ryzhov






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

Migrating NodeJS client to TypeScript

[Данилов Семён]

Hello Igniters!

I'd like to propose a big change for the nodejs thin client: a full rewrite 
from JavaScript to TypeScript.

Strong typing will not only help us in future while developing new features, 
but will also indicate existing type inconsistencies (I know there is a couple).
Also, we will have out of the box types for API documentation, which is very 
handy for users.

So what do you think?

Kind regards,
Semyon.

Website related tickets on JIRA

[Mauricio Stekl]

Hi Ignite Community,
For those of you who do not know me, my name is Mauricio and I have been
doing contributions related to the website for a long time now. Generally I
have coordinated these updates directly with some community members.
However, for future contributions I would like to see if it is possible to
start creating tickets on JIRA using the 'website' component. This will
help me to better organize the tasks where I can contribute, and, of
course, it will help us all track what is going on around the website.

Please let me know if you have any questions or suggestions. Otherwise I
look forward to seeing those tickets on JIRA.


Thanks.

Mauricio

Re: Join to dev community

[Dmitriy Pavlov]

Sorry, I meant text/plain

пн, 30 нояб. 2020 г. в 20:24, Dmitriy Pavlov :

> Hi Aleksey,
>
> Unfortunately Apache Mailing lists can accept text/html or mixed content
> types in emails. Generally speaking, it is because the formatting of text
> in mailing archives is not supported.
>
> Could you please change your email client settings to provide text or
> mixed messages?
>
> Sincerely
> Dmitriy Pavlov
>
> пн, 30 нояб. 2020 г. в 20:16, Aleksey Rostov :
>
>> Hello!
>> So, I found out that I have created an account in
>> https://cwiki.apache.org/
>> . I thought that confluence and jira share accounts but this was not the
>> case.
>> I have created a jira account - arostov and checked it. My main email
>> address is alekse-ros...@ya.ru but I can't send emails from this
>> account, I
>> catch error every time
>>
>> :
>> ezmlm-reject: fatal: Sorry, I don't accept messages of MIME Content-Type
>> 'text/html' (#5.2.3)
>>
>> Therefore I send from secondary email address arostov.a...@gmail.com
>>
>> пт, 27 нояб. 2020 г. в 21:19, Aleksey Rostov :
>>
>> > Hello everyone!
>> > My name is Aleksey Rostov, I want to contribute to Ignite.NET. I am
>> > currently a senior .net developer in Luxoft company in Saint Petersburg.
>> > Please, help me to start contributing.
>> > I have created a jira account - arostov.
>> >
>>
>

Re: Join to dev community

[Dmitriy Pavlov]

Hi Aleksey,

Unfortunately Apache Mailing lists can accept text/html or mixed content
types in emails. Generally speaking, it is because the formatting of text
in mailing archives is not supported.

Could you please change your email client settings to provide text or
mixed messages?

Sincerely
Dmitriy Pavlov

пн, 30 нояб. 2020 г. в 20:16, Aleksey Rostov :

> Hello!
> So, I found out that I have created an account in
> https://cwiki.apache.org/
> . I thought that confluence and jira share accounts but this was not the
> case.
> I have created a jira account - arostov and checked it. My main email
> address is alekse-ros...@ya.ru but I can't send emails from this account,
> I
> catch error every time
>
> :
> ezmlm-reject: fatal: Sorry, I don't accept messages of MIME Content-Type
> 'text/html' (#5.2.3)
>
> Therefore I send from secondary email address arostov.a...@gmail.com
>
> пт, 27 нояб. 2020 г. в 21:19, Aleksey Rostov :
>
> > Hello everyone!
> > My name is Aleksey Rostov, I want to contribute to Ignite.NET. I am
> > currently a senior .net developer in Luxoft company in Saint Petersburg.
> > Please, help me to start contributing.
> > I have created a jira account - arostov.
> >
>

Re: Join to dev community

[Aleksey Rostov]

Hello!
So, I found out that I have created an account in https://cwiki.apache.org/
. I thought that confluence and jira share accounts but this was not the
case.
I have created a jira account - arostov and checked it. My main email
address is alekse-ros...@ya.ru but I can't send emails from this account, I
catch error every time

:
ezmlm-reject: fatal: Sorry, I don't accept messages of MIME Content-Type
'text/html' (#5.2.3)

Therefore I send from secondary email address arostov.a...@gmail.com

пт, 27 нояб. 2020 г. в 21:19, Aleksey Rostov :

> Hello everyone!
> My name is Aleksey Rostov, I want to contribute to Ignite.NET. I am
> currently a senior .net developer in Luxoft company in Saint Petersburg.
> Please, help me to start contributing.
> I have created a jira account - arostov.
>

[GitHub] [ignite-3] AMashenkov commented on a change in pull request #3: IGNITE-13610 WIP Initial version of unified CLI tool

[GitBox]

AMashenkov commented on a change in pull request #3:
URL: https://github.com/apache/ignite-3/pull/3#discussion_r532742174



##
File path: modules/cli-demo/cli-common/pom.xml
##
@@ -0,0 +1,32 @@
+
+
 
   
   ```

##
File path: modules/cli-demo/demo-module-all/demo-module/pom.xml
##
@@ -0,0 +1,33 @@
+

Re[2]: 2.9.1 release scope and dates

[Zhenya Stanilovsky]

hello !
seems it [1] need to be included too, if it`s not too late, of course. May be 
you can bump reviewer somehow?)
 
[1]  https://issues.apache.org/jira/browse/IGNITE-13765
 
>Ivan, it's added, thanks for pointing that out
>
>On Mon, Nov 30, 2020 at 5:44 PM Ivan Daschinsky < ivanda...@gmail.com > wrote:
> 
>> Yaroslav, could you explain why you decided to remove from scope
>>  https://issues.apache.org/jira/browse/IGNITE-13699 ?
>> This ticket also incorporate few fixes for metrics. Currently metrics is a
>> little bit broken (JoinedCount shows invalid results for example)
>>
>>
>> пн, 30 нояб. 2020 г. в 17:26, Yaroslav Molochkov < molochko...@gmail.com >:
>>
>> > Igniters, hello!
>> >
>> > First of all, sorry that the release process is taking so long.
>> >
>> > Secondly, the release build seems stable and no blockers were introduced
>> > within that list
>> > <
>> >
>>  
>> https://issues.apache.org/jira/browse/IGNITE-11312?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1%20and%20status%20%3D%20Resolved
>> > >
>> > (at
>> > least on RunAll compared to 2.9)
>> >
>> > I've also prepared release notes:
>> >
>> > Ignite Core:
>> > * Added support to graceful shutdown for ZookeeperDiscoverySpi
>> > * Added System view for binary metadata
>> > * Added System view for metastorage items
>> > * Added RebalancingPartitionsTotal metrics
>> > * Improved checkpoint concurrent behaviour
>> > * Fixed critical system error when unregister a JMX bean
>> > * Fixed IgniteCache#isClosed() returns false on server node even if
>> > the cache had been closed before
>> > * Fixed inability to eagerly remove expired cache entries
>> > * Fixed partial index rebuild issue in case indexed cache contains
>> > different datatypes
>> > * Fixed local metastorage system view error if unmarshallable values
>> > present
>> > * Fixed deadlock between grid-timeout-worker and a thread opening a
>> > communication connection
>> > * Fixed deadlock in IgniteServiceProcessor
>> > * Fixed issue when rebalance future might hang in no final state
>> > though all partitions are owned
>> > * Fixed issue when scan query fails with an assertion error: Unexpected
>> > row key
>> > * Fixed issue with archiving and enabled wal compaction setting on
>> > server restart
>> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE strategy
>> > * Fixed synchronization problems when different classloaders are used
>> > for deployment of same class
>> > * Fixed exception on SQL caches when client reconnect
>> > * Fixed deadlock on multiple cache delete
>> > * Fixed NPE in IgniteServiceProcessor when destroying a cache
>> > * Fixed issue when DurableBackgroundTask can abandon incomplete task
>> > * Fixed issue related to cache interceptor deserialization on client
>> nodes
>> > * Fixed issue when control.sh doesn't start if JMX port was set
>> > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can
>> > return invalid node as coordinator
>> > * Fixed issue when valid blocking section in GridNioWorker and
>> > GridNioClientWorker leads to false positive blocking thread detection
>> > * Fixed several logging issues
>> > * Fixed issue when exchange worker, waiting for new task from queue,
>> > considered as blocked
>> > * Fixed incorrect topology snapshot logger output about coordinator
>> change
>> > * Fixed slowdown during node initialization
>> > * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal
>> > and SystemViewMBean classes
>> > * Removed unnecessary dependency to curator-client from and improved
>> > ZookeeperDiscoverySpi
>> > * Removed unnecessary failure trace in IgnitionEx
>> >
>> > Java thin-client:
>> > * Fixed issue when thin client connect/disconnect during topology
>> > update may lead to partition divergence in ignite-sys-cache
>> > * Fixed issue when thin client silently closes channel after inactivity
>> > * Fixed unsupported protocol version exception when getting cache
>> > configuration from Java thin client
>> >
>> > JDBC:
>> > * Fixed thin driver reports incorrect property names
>> > * Updated JDBC metadata to match actual capabilities
>> >
>> > Ignite .NET:
>> > * Improved slow Enum serialization
>> > * Fixed issue when deserializing IBinaryObject containing an
>> > IBinaryObject field fails
>> > * Fixed issue TransactionImpl finalizer can crash the process
>> > * Fixed child processes become zombies when persistence is used with
>> > direct-io on Linux
>> >
>> > Ignite C++:
>> > * Fixed issue when odbc-example loses values if run with 1 additional
>> node
>> > * Added Windows support to CMake build system
>> >
>> >
>> > Thoughts?
>> >
>> >
>> >
>> >
>> > On Thu, Nov 26, 2020 at 11:55 PM Yaroslav Molochkov <
>>  molochko...@gmail.com
>> > >
>> > wrote:
>> >
>> > > Maxim,
>> > >
>> > > Yeah, I guess I did all I could with my access rights, all there’s to
>> do
>> > > is to merge my PR in the branch and publish necessary artifacts
>> > >
>> > > And, of course, sorry that I’m a bit 

Re: 2.9.1 release scope and dates

[Yaroslav Molochkov]

Ivan, it's added, thanks for pointing that out

On Mon, Nov 30, 2020 at 5:44 PM Ivan Daschinsky  wrote:

> Yaroslav, could you explain why you decided to remove from scope
> https://issues.apache.org/jira/browse/IGNITE-13699 ?
> This ticket also incorporate few fixes for metrics. Currently metrics is a
> little bit broken (JoinedCount shows invalid results for example)
>
>
> пн, 30 нояб. 2020 г. в 17:26, Yaroslav Molochkov :
>
> > Igniters, hello!
> >
> > First of all, sorry that the release process is taking so long.
> >
> > Secondly, the release build seems stable and no blockers were introduced
> > within that list
> > <
> >
> https://issues.apache.org/jira/browse/IGNITE-11312?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1%20and%20status%20%3D%20Resolved
> > >
> > (at
> > least on RunAll compared to 2.9)
> >
> > I've also prepared release notes:
> >
> > Ignite Core:
> > * Added support to graceful shutdown for ZookeeperDiscoverySpi
> > * Added System view for binary metadata
> > * Added System view for metastorage items
> > * Added RebalancingPartitionsTotal metrics
> > * Improved checkpoint concurrent behaviour
> > * Fixed critical system error when unregister a JMX bean
> > * Fixed IgniteCache#isClosed() returns false on server node even if
> > the cache had been closed before
> > * Fixed inability to eagerly remove expired cache entries
> > * Fixed partial index rebuild issue in case indexed cache contains
> > different datatypes
> > * Fixed local metastorage system view error if unmarshallable values
> > present
> > * Fixed deadlock between grid-timeout-worker and a thread opening a
> > communication connection
> > * Fixed deadlock in IgniteServiceProcessor
> > * Fixed issue when rebalance future might hang in no final state
> > though all partitions are owned
> > * Fixed issue when scan query fails with an assertion error: Unexpected
> > row key
> > * Fixed issue with archiving and enabled wal compaction setting on
> > server restart
> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE strategy
> > * Fixed synchronization problems when different classloaders are used
> > for deployment of same class
> > * Fixed exception on SQL caches when client reconnect
> > * Fixed deadlock on multiple cache delete
> > * Fixed NPE in IgniteServiceProcessor when destroying a cache
> > * Fixed issue when DurableBackgroundTask can abandon incomplete task
> > * Fixed issue related to cache interceptor deserialization on client
> nodes
> > * Fixed issue when control.sh doesn't start if JMX port was set
> > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can
> > return invalid node as coordinator
> > * Fixed issue when valid blocking section in GridNioWorker and
> > GridNioClientWorker leads to false positive blocking thread detection
> > * Fixed several logging issues
> > * Fixed issue when exchange worker, waiting for new task from queue,
> > considered as blocked
> > * Fixed incorrect topology snapshot logger output about coordinator
> change
> > * Fixed slowdown during node initialization
> > * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal
> > and SystemViewMBean classes
> > * Removed unnecessary dependency to curator-client from and improved
> > ZookeeperDiscoverySpi
> > * Removed unnecessary failure trace in IgnitionEx
> >
> > Java thin-client:
> > * Fixed issue when thin client connect/disconnect during topology
> > update may lead to partition divergence in ignite-sys-cache
> > * Fixed issue when thin client silently closes channel after inactivity
> > * Fixed unsupported protocol version exception when getting cache
> > configuration from Java thin client
> >
> > JDBC:
> > * Fixed thin driver reports incorrect property names
> > * Updated JDBC metadata to match actual capabilities
> >
> > Ignite .NET:
> > * Improved slow Enum serialization
> > * Fixed issue when deserializing IBinaryObject containing an
> > IBinaryObject field fails
> > * Fixed issue TransactionImpl finalizer can crash the process
> > * Fixed child processes become zombies when persistence is used with
> > direct-io on Linux
> >
> > Ignite C++:
> > * Fixed issue when odbc-example loses values if run with 1 additional
> node
> > * Added Windows support to CMake build system
> >
> >
> > Thoughts?
> >
> >
> >
> >
> > On Thu, Nov 26, 2020 at 11:55 PM Yaroslav Molochkov <
> molochko...@gmail.com
> > >
> > wrote:
> >
> > > Maxim,
> > >
> > > Yeah, I guess I did all I could with my access rights, all there’s to
> do
> > > is to merge my PR in the branch and publish necessary artifacts
> > >
> > > And, of course, sorry that I’m a bit behind the schedule
> > >
> > >
> > > > On 26 Nov 2020, at 21:14, Maxim Muzafarov  wrote:
> > > >
> > > > Yaroslav,
> > > >
> > > >
> > > > It seems we've reached the proposed voting date - Nov. 26th
> > > > Do you need any help with the release preparation?
> > > >
> > > >> On Fri, 20 Nov 2020 at 14:46, Steshin Vladimir 
> > > wrote:
> > > >>
> > > >> 

[jira] [Created] (IGNITE-13777) idle_verify should report real size of the partitions

[Stanislav Lukyanov (Jira)]

Stanislav Lukyanov created IGNITE-13777:
---

 Summary: idle_verify should report real size of the partitions
 Key: IGNITE-13777
 URL: https://issues.apache.org/jira/browse/IGNITE-13777
 Project: Ignite
  Issue Type: Bug
Reporter: Stanislav Lukyanov


Currently, idle_verify checks the content of partitions (through hash) and the 
partition size that is stored in the partition meta. It will be better if 
idle_verify also counts the entries inside the partition and returns both the 
size from the meta AND the real size.



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

[GitHub] [ignite-3] kgusakov opened a new pull request #3: IGNITE-13610 WIP Initial version of unified CLI tool

[GitBox]

kgusakov opened a new pull request #3:
URL: https://github.com/apache/ignite-3/pull/3


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE][EXTENSION] Release Apache Ignite Streaming extensions 1.0.0 RC1

[Konstantin Orlov]

+1

-- 
Regards,
Konstantin Orlov

Re: 2.9.1 release scope and dates

[Ivan Daschinsky]

Yaroslav, could you explain why you decided to remove from scope
https://issues.apache.org/jira/browse/IGNITE-13699 ?
This ticket also incorporate few fixes for metrics. Currently metrics is a
little bit broken (JoinedCount shows invalid results for example)


пн, 30 нояб. 2020 г. в 17:26, Yaroslav Molochkov :

> Igniters, hello!
>
> First of all, sorry that the release process is taking so long.
>
> Secondly, the release build seems stable and no blockers were introduced
> within that list
> <
> https://issues.apache.org/jira/browse/IGNITE-11312?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1%20and%20status%20%3D%20Resolved
> >
> (at
> least on RunAll compared to 2.9)
>
> I've also prepared release notes:
>
> Ignite Core:
> * Added support to graceful shutdown for ZookeeperDiscoverySpi
> * Added System view for binary metadata
> * Added System view for metastorage items
> * Added RebalancingPartitionsTotal metrics
> * Improved checkpoint concurrent behaviour
> * Fixed critical system error when unregister a JMX bean
> * Fixed IgniteCache#isClosed() returns false on server node even if
> the cache had been closed before
> * Fixed inability to eagerly remove expired cache entries
> * Fixed partial index rebuild issue in case indexed cache contains
> different datatypes
> * Fixed local metastorage system view error if unmarshallable values
> present
> * Fixed deadlock between grid-timeout-worker and a thread opening a
> communication connection
> * Fixed deadlock in IgniteServiceProcessor
> * Fixed issue when rebalance future might hang in no final state
> though all partitions are owned
> * Fixed issue when scan query fails with an assertion error: Unexpected
> row key
> * Fixed issue with archiving and enabled wal compaction setting on
> server restart
> * Fixed NPE during Cassandra Store initialization with PRIMITIVE strategy
> * Fixed synchronization problems when different classloaders are used
> for deployment of same class
> * Fixed exception on SQL caches when client reconnect
> * Fixed deadlock on multiple cache delete
> * Fixed NPE in IgniteServiceProcessor when destroying a cache
> * Fixed issue when DurableBackgroundTask can abandon incomplete task
> * Fixed issue related to cache interceptor deserialization on client nodes
> * Fixed issue when control.sh doesn't start if JMX port was set
> * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can
> return invalid node as coordinator
> * Fixed issue when valid blocking section in GridNioWorker and
> GridNioClientWorker leads to false positive blocking thread detection
> * Fixed several logging issues
> * Fixed issue when exchange worker, waiting for new task from queue,
> considered as blocked
> * Fixed incorrect topology snapshot logger output about coordinator change
> * Fixed slowdown during node initialization
> * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal
> and SystemViewMBean classes
> * Removed unnecessary dependency to curator-client from and improved
> ZookeeperDiscoverySpi
> * Removed unnecessary failure trace in IgnitionEx
>
> Java thin-client:
> * Fixed issue when thin client connect/disconnect during topology
> update may lead to partition divergence in ignite-sys-cache
> * Fixed issue when thin client silently closes channel after inactivity
> * Fixed unsupported protocol version exception when getting cache
> configuration from Java thin client
>
> JDBC:
> * Fixed thin driver reports incorrect property names
> * Updated JDBC metadata to match actual capabilities
>
> Ignite .NET:
> * Improved slow Enum serialization
> * Fixed issue when deserializing IBinaryObject containing an
> IBinaryObject field fails
> * Fixed issue TransactionImpl finalizer can crash the process
> * Fixed child processes become zombies when persistence is used with
> direct-io on Linux
>
> Ignite C++:
> * Fixed issue when odbc-example loses values if run with 1 additional node
> * Added Windows support to CMake build system
>
>
> Thoughts?
>
>
>
>
> On Thu, Nov 26, 2020 at 11:55 PM Yaroslav Molochkov  >
> wrote:
>
> > Maxim,
> >
> > Yeah, I guess I did all I could with my access rights, all there’s to do
> > is to merge my PR in the branch and publish necessary artifacts
> >
> > And, of course, sorry that I’m a bit behind the schedule
> >
> >
> > > On 26 Nov 2020, at 21:14, Maxim Muzafarov  wrote:
> > >
> > > Yaroslav,
> > >
> > >
> > > It seems we've reached the proposed voting date - Nov. 26th
> > > Do you need any help with the release preparation?
> > >
> > >> On Fri, 20 Nov 2020 at 14:46, Steshin Vladimir 
> > wrote:
> > >>
> > >> Yaroslav, Hi.
> > >>
> > >>
> > >> I suggest to merge minor fix of javadoc: [1]. It should have appeared
> in
> > >> 2.9. Commits in master:
> > >>
> > >> d3e5b7c11ed037670700eea75851e619d5d1b6b1
> > >>
> > >> and
> > >>
> > >> 1654e9fac61842424c08d26a08ef67569f74746a
> > >>
> > >>
> > >> [1] https://github.com/apache/ignite/pull/8448
> > >>
> > >>
> > >>
> > >> 19.11.2020 17:15, 

Re: 2.9.1 release scope and dates

[Yaroslav Molochkov]

Igniters, hello!

First of all, sorry that the release process is taking so long.

Secondly, the release build seems stable and no blockers were introduced
within that list

(at
least on RunAll compared to 2.9)

I've also prepared release notes:

Ignite Core:
* Added support to graceful shutdown for ZookeeperDiscoverySpi
* Added System view for binary metadata
* Added System view for metastorage items
* Added RebalancingPartitionsTotal metrics
* Improved checkpoint concurrent behaviour
* Fixed critical system error when unregister a JMX bean
* Fixed IgniteCache#isClosed() returns false on server node even if
the cache had been closed before
* Fixed inability to eagerly remove expired cache entries
* Fixed partial index rebuild issue in case indexed cache contains
different datatypes
* Fixed local metastorage system view error if unmarshallable values present
* Fixed deadlock between grid-timeout-worker and a thread opening a
communication connection
* Fixed deadlock in IgniteServiceProcessor
* Fixed issue when rebalance future might hang in no final state
though all partitions are owned
* Fixed issue when scan query fails with an assertion error: Unexpected row key
* Fixed issue with archiving and enabled wal compaction setting on
server restart
* Fixed NPE during Cassandra Store initialization with PRIMITIVE strategy
* Fixed synchronization problems when different classloaders are used
for deployment of same class
* Fixed exception on SQL caches when client reconnect
* Fixed deadlock on multiple cache delete
* Fixed NPE in IgniteServiceProcessor when destroying a cache
* Fixed issue when DurableBackgroundTask can abandon incomplete task
* Fixed issue related to cache interceptor deserialization on client nodes
* Fixed issue when control.sh doesn't start if JMX port was set
* Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can
return invalid node as coordinator
* Fixed issue when valid blocking section in GridNioWorker and
GridNioClientWorker leads to false positive blocking thread detection
* Fixed several logging issues
* Fixed issue when exchange worker, waiting for new task from queue,
considered as blocked
* Fixed incorrect topology snapshot logger output about coordinator change
* Fixed slowdown during node initialization
* Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal
and SystemViewMBean classes
* Removed unnecessary dependency to curator-client from and improved
ZookeeperDiscoverySpi
* Removed unnecessary failure trace in IgnitionEx

Java thin-client:
* Fixed issue when thin client connect/disconnect during topology
update may lead to partition divergence in ignite-sys-cache
* Fixed issue when thin client silently closes channel after inactivity
* Fixed unsupported protocol version exception when getting cache
configuration from Java thin client

JDBC:
* Fixed thin driver reports incorrect property names
* Updated JDBC metadata to match actual capabilities

Ignite .NET:
* Improved slow Enum serialization
* Fixed issue when deserializing IBinaryObject containing an
IBinaryObject field fails
* Fixed issue TransactionImpl finalizer can crash the process
* Fixed child processes become zombies when persistence is used with
direct-io on Linux

Ignite C++:
* Fixed issue when odbc-example loses values if run with 1 additional node
* Added Windows support to CMake build system


Thoughts?




On Thu, Nov 26, 2020 at 11:55 PM Yaroslav Molochkov 
wrote:

> Maxim,
>
> Yeah, I guess I did all I could with my access rights, all there’s to do
> is to merge my PR in the branch and publish necessary artifacts
>
> And, of course, sorry that I’m a bit behind the schedule
>
>
> > On 26 Nov 2020, at 21:14, Maxim Muzafarov  wrote:
> >
> > Yaroslav,
> >
> >
> > It seems we've reached the proposed voting date - Nov. 26th
> > Do you need any help with the release preparation?
> >
> >> On Fri, 20 Nov 2020 at 14:46, Steshin Vladimir 
> wrote:
> >>
> >> Yaroslav, Hi.
> >>
> >>
> >> I suggest to merge minor fix of javadoc: [1]. It should have appeared in
> >> 2.9. Commits in master:
> >>
> >> d3e5b7c11ed037670700eea75851e619d5d1b6b1
> >>
> >> and
> >>
> >> 1654e9fac61842424c08d26a08ef67569f74746a
> >>
> >>
> >> [1] https://github.com/apache/ignite/pull/8448
> >>
> >>
> >>
> >> 19.11.2020 17:15, Ivan Daschinsky пишет:
> >>> Hi!
> >>> Yaroslav, Max -- I have another ticket that will be nice to have in
> 2.9.1
> >>> https://issues.apache.org/jira/browse/IGNITE-13699
> >>>
> >>> пт, 13 нояб. 2020 г. в 15:08, Yaroslav Molochkov <
> molochko...@gmail.com>:
> >>>
>  Igniters, hello!
> 
>  I think the scope of 2.9.1 is finalized.
> 
> > On 9 Nov 2020, at 12:04, Yaroslav Molochkov 
>  wrote:
> > Ivan, thanks!
> >
> > Added it to the list.
> >
> >> On 8 Nov 2020, at 14:13, Ivan Daschinsky 
> wrote:
> >>
> 

Re: [VOTE][EXTENSION] Release Apache Ignite Streaming extensions 1.0.0 RC1

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

+1

30.11.2020, 16:15, "Andrey Gura" :
> +1
>
> On Tue, Nov 24, 2020 at 3:24 AM Saikat Maitra  wrote:
>>  +1
>>
>>  Denis, Alex
>>
>>  I have raised PR for the docs for Maven artifactIds and versions on the
>>  documentation pages of the integrations.
>>
>>  PR : https://github.com/apache/ignite/pull/8488
>>
>>  Jira : https://issues.apache.org/jira/browse/IGNITE-12951
>>
>>  Please review and share if any further changes are required.
>>
>>  Regards,
>>  Saikat
>>
>>  On Mon, Nov 23, 2020 at 5:50 PM Denis Magda  wrote:
>>
>>  > +1
>>  >
>>  > Alex, could you please update Maven artifactIds and versions on the
>>  > documentation pages of the integrations? Commit to the master and
>>  > cherry-pick to ignite-2.9-docs, and I'll publish the changes to the
>>  > website.
>>  >
>>  > -
>>  > Denis
>>  >
>>  >
>>  > On Mon, Nov 23, 2020 at 10:52 AM Alexey Goncharuk 
>>  > wrote:
>>  >
>>  > > Dear Ignite Community,
>>  > >
>>  > > I have uploaded a release candidate of the following extension modules:
>>  > > ignite-camel-ext
>>  > > ignite-flink-ext
>>  > > ignite-flume-ext
>>  > > ignite-jms11-ext
>>  > > ignite-kafka-ext
>>  > > ignite-mqtt-ext
>>  > > ignite-pub-sub-ext
>>  > > ignite-rocketmq-ext
>>  > > ignite-storm-ext
>>  > > ignite-twitter-ext
>>  > > ignite-zeromq-ext
>>  > >
>>  > > The following staging can be used for testing:
>>  > > https://repository.apache.org/content/repositories/orgapacheignite-1489
>>  > >
>>  > > Tags were created:
>>  > > ignite-camel-ext-1.0.0-rc1
>>  > > ignite-flink-ext-1.0.0-rc1
>>  > > ignite-flume-ext-1.0.0-rc1
>>  > > ignite-jms11-ext-1.0.0-rc1
>>  > > ignite-kafka-ext-1.0.0-rc1
>>  > > ignite-mqtt-ext-1.0.0-rc1
>>  > > ignite-pub-sub-ext-1.0.0-rc1
>>  > > ignite-rocketmq-ext-1.0.0-rc1
>>  > > ignite-storm-ext-1.0.0-rc1
>>  > > ignite-twitter-ext-1.0.0-rc1
>>  > > ignite-zeromq-ext-1.0.0-rc1
>>  > >
>>  > >
>>  > 
>> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=3f45b3e32d617b652e08af614a90aad6b9ff945d
>>  > >
>>  > > RELEASE NOTES:
>>  > >
>>  > >
>>  > 
>> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=8451780d53af3eea926fbd3235cc535d76888fa9;hb=refs/heads/streaming-all-ext-1.0.0
>>  > >
>>  > > Release 1.0.0 contains the initial state of the modules migrated from 
>> the
>>  > > Apache Ignite main repository according to the IEP (includes the list of
>>  > > resolved issues):
>>  > >
>>  > 
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
>>  > >
>>  > > The vote is formal, see voting guidelines
>>  > > https://www.apache.org/foundation/voting.html
>>  > >
>>  > > +1 - to accept all the Apache Ignite streaming extensions 1.0.0-rc1
>>  > listed
>>  > > in the thread
>>  > > 0 - don't care either way
>>  > > -1 - DO NOT accept either of the Apache Ignite streaming extensions
>>  > > 1.0.0-rc1 (explain why)
>>  > >
>>  > > Given the large list of extensions, the vote will hold for 7 days and
>>  > will
>>  > > end on Monday, November 30th 19:00 UTC:
>>  > >
>>  > >
>>  > 
>> https://www.timeanddate.com/countdown/generic?iso=20201130T22=166=cursive=1
>>  > >
>>  >

Re: [DISCUSS] Ignite 3.0 development approach

[Petr Ivanov]

Hi, Val.


Thanks for comments.
Let me explain some ambiguous points.


> [Val] What do we use Ant tasks for? I'm sure we do use them a lot for
> release packaging, but it will apparently be significantly simplified. Are
> there any other cases?

We have ant tasks for C++ / .NET version changing (including calling Javascript 
via ant), assembling, javadoc modification and so on.
There are at least 11 modules with maven-antrun-plugin, plus core and parent 
pom.

I suggest some revision is required and a) removing of obsolete ones and b) 
trying to replace ant call with more native maven plugin (or at least redesign 
approach to be more clear what it does and why).



> [Val] Could you elaborate on this? What should be parallelized in your
> view, and how exactly it will speed up the process?

I was talking about stable parallel build (current it is not stable, producing 
different results from build to build and having race condition issues) and 
parallel tests (we have no unit tests for now, but when we will have, 
forkCount=1 should be the default behaviour).
For both — correct set of plugins and their version should be introduced and 
tests.

That is not in high priority, more "nice to have" feature.



> [Val] I'm not sure we need this. Gradle does seem to be nicer than Maven in
> many aspects, but this will be a big transition for the community. The
> value of such a transition is not clear. We also seem to have much more
> experience in Maven than in Gradle.

Agree. I was thinking of Gradle only as a possible alternative if we will face 
impossible to solve with maven issues.




> On 28 Nov 2020, at 07:31, Valentin Kulichenko  
> wrote:
> 
> Petr,
> 
> You have some great points! My comments are below.
> 
> -Val
> 
> On Fri, Nov 27, 2020 at 4:28 AM Petr Ivanov  wrote:
> 
>> More or less, unless we specifically forbid that, I guess
>> 
>> However there is bigger concern: JDK 15 is STS, so after half of a year it
>> will be out of support and no major production team will use that JDK in
>> their environment.
>> I would stick to JDK 11 as it is LTS at least until JDK17, plus — a lot of
>> efforts should be made to enforce Apache Ignite be built on JDK 11 alone,
>> not to mention 15th version...
>> 
> 
> [Val] I think we will have to stick with Java 11, simply because it's the
> current LTS. If we go with 15, almost no one will be able to use Ignite in
> production :) We can switch to 17 in the future in case there is any value.
> 
> 
>> Also, If we are going to introduce such major changes, I'd like to purpose
>> maven project refactoring as well:
>> 1. Full revision of all ant-calling tasks with javascript functions and
>> alike — the complexity of those are overwhelming, something new should be
>> at least researched.
>> 
> 
> [Val] What do we use Ant tasks for? I'm sure we do use them a lot for
> release packaging, but it will apparently be significantly simplified. Are
> there any other cases?
> 
> 
>> 2. Full revisions of profiles (for both root and modules) as there are
>> some obsolete ones, and some that do ambiguous or, even worse, totally
>> unknown tasks.
>> 
> 
> [Val] Agree - the number of profiles should be at least minimized. In the
> best case, we should not have any profiles at all. They are non-intuitive
> for developers, and also often confuse IDEs.
> 
> 
>> 3. Introduce plugin and dependency management sections to control over and
>> concrete versions of software we are relying in our project. Additionally —
>> add BOM with all Ignite modules and their dependencies, which should help
>> our users to better embed Ignite to their projects.
>> 4. Up all versions of plugins and dependencies where possible to there
>> current production versions (for plugins — it should be a must if we are
>> ever going to build project under latest JDK versions).
>> 
> 
> [Val] Agree with both.
> 
> 
>> 5. Prepare project for parallel building, testing and assembling where
>> possible for faster development process, with possible additional
>> enhancement like incremental rebuild.
>> 
> 
> [Val] Could you elaborate on this? What should be parallelized in your
> view, and how exactly it will speed up the process?
> 
> 
>> 6. Possibly — research alternate builders, like Gradle (thought there are
>> a lot of questions to its race condition issues during multimodule builds).
>> 
> 
> [Val] I'm not sure we need this. Gradle does seem to be nicer than Maven in
> many aspects, but this will be a big transition for the community. The
> value of such a transition is not clear. We also seem to have much more
> experience in Maven than in Gradle.
> 
> 
>> And last, but not least — think of migrating to 'CI/CD as a Code' approach
>> for our main instrument TeamCity.
>> Whole project (both test and release build configurations) can be
>> described using DSL (Kotlin in case of TC) and stored in VCS, forcing
>> infrastructure changes to go through the same development processes
>> including discussions, review, 

Re: [VOTE][EXTENSION] Release Apache Ignite Streaming extensions 1.0.0 RC1

[Andrey Gura]

+1

On Tue, Nov 24, 2020 at 3:24 AM Saikat Maitra  wrote:
>
> +1
>
> Denis, Alex
>
> I have raised PR for the docs for Maven artifactIds and versions on the
> documentation pages of the integrations.
>
> PR :  https://github.com/apache/ignite/pull/8488
>
> Jira : https://issues.apache.org/jira/browse/IGNITE-12951
>
> Please review and share if any further changes are required.
>
> Regards,
> Saikat
>
>
>
> On Mon, Nov 23, 2020 at 5:50 PM Denis Magda  wrote:
>
> > +1
> >
> > Alex, could you please update Maven artifactIds and versions on the
> > documentation pages of the integrations? Commit to the master and
> > cherry-pick to ignite-2.9-docs, and I'll publish the changes to the
> > website.
> >
> > -
> > Denis
> >
> >
> > On Mon, Nov 23, 2020 at 10:52 AM Alexey Goncharuk 
> > wrote:
> >
> > > Dear Ignite Community,
> > >
> > > I have uploaded a release candidate of the following extension modules:
> > > ignite-camel-ext
> > > ignite-flink-ext
> > > ignite-flume-ext
> > > ignite-jms11-ext
> > > ignite-kafka-ext
> > > ignite-mqtt-ext
> > > ignite-pub-sub-ext
> > > ignite-rocketmq-ext
> > > ignite-storm-ext
> > > ignite-twitter-ext
> > > ignite-zeromq-ext
> > >
> > > The following staging can be used for testing:
> > > https://repository.apache.org/content/repositories/orgapacheignite-1489
> > >
> > > Tags were created:
> > > ignite-camel-ext-1.0.0-rc1
> > > ignite-flink-ext-1.0.0-rc1
> > > ignite-flume-ext-1.0.0-rc1
> > > ignite-jms11-ext-1.0.0-rc1
> > > ignite-kafka-ext-1.0.0-rc1
> > > ignite-mqtt-ext-1.0.0-rc1
> > > ignite-pub-sub-ext-1.0.0-rc1
> > > ignite-rocketmq-ext-1.0.0-rc1
> > > ignite-storm-ext-1.0.0-rc1
> > > ignite-twitter-ext-1.0.0-rc1
> > > ignite-zeromq-ext-1.0.0-rc1
> > >
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=3f45b3e32d617b652e08af614a90aad6b9ff945d
> > >
> > > RELEASE NOTES:
> > >
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=8451780d53af3eea926fbd3235cc535d76888fa9;hb=refs/heads/streaming-all-ext-1.0.0
> > >
> > > Release 1.0.0 contains the initial state of the modules migrated from the
> > > Apache Ignite main repository according to the IEP (includes the list of
> > > resolved issues):
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
> > >
> > > The vote is formal, see voting guidelines
> > > https://www.apache.org/foundation/voting.html
> > >
> > > +1 - to accept all the Apache Ignite streaming extensions 1.0.0-rc1
> > listed
> > > in the thread
> > > 0 - don't care either way
> > > -1 - DO NOT accept either of the Apache Ignite streaming extensions
> > > 1.0.0-rc1 (explain why)
> > >
> > > Given the large list of extensions, the vote will hold for 7 days and
> > will
> > > end on Monday, November 30th 19:00 UTC:
> > >
> > >
> > https://www.timeanddate.com/countdown/generic?iso=20201130T22=166=cursive=1
> > >
> >

[jira] [Created] (IGNITE-13776) BPlus tree lock retries limit reached with sqlOnHeapCacheEnabled

[Konstantin Orlov (Jira)]

Konstantin Orlov created IGNITE-13776:
-

 Summary: BPlus tree lock retries limit reached with 
sqlOnHeapCacheEnabled
 Key: IGNITE-13776
 URL: https://issues.apache.org/jira/browse/IGNITE-13776
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.9
Reporter: Konstantin Orlov
Assignee: Konstantin Orlov


Issue might be reproduced with sqlOnHeapCacheEnabled=true.

The following exception is thrown while streaming some data into caches with 
data streamer:
{code:java}
[2020-07-08 20:22:16,766][ERROR][data-streamer-stripe-0-#9][root] Critical 
system error detected. Will be handled accordingly to configured handler 
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], 
failureCtx=FailureContext [type=CRITICAL_ERROR, err=class 
o.a.i.IgniteCheckedException: Maximum number of retries 1000 reached for Put 
operation (the tree may be corrupted). Increase IGNITE_BPLUS_TREE_LOCK_RETRIES 
system property if you regularly see this message (current value is 1000).]]
class org.apache.ignite.IgniteCheckedException: Maximum number of retries 1000 
reached for Put operation (the tree may be corrupted). Increase 
IGNITE_BPLUS_TREE_LOCK_RETRIES system property if you regularly see this 
message (current value is 1000).
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Get.checkLockRetry(BPlusTree.java:3090)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.checkLockRetry(BPlusTree.java:3887)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2771)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2413)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2393)
at 
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:757)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:379)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2187)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:406)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2561)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1670)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1645)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:2473)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2328)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2601)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:2062)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1879)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1686)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:486)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:446)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1172)
at 

[jira] [Created] (IGNITE-13775) U.ReentrantReadWriteLockTracer improper realization.

[Stanilovsky Evgeny (Jira)]

Stanilovsky Evgeny created IGNITE-13775:
---

 Summary: U.ReentrantReadWriteLockTracer improper realization.
 Key: IGNITE-13775
 URL: https://issues.apache.org/jira/browse/IGNITE-13775
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.9
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny


ReentrantReadWriteLockTracer accepts ReentrantReadWriteLock as a delegate and 
stores delegates for readLock and writeLock. But 
ReentrantReadWriteLock#isWriteLockedByCurrentThread uses sync object to 
evaluate the result instead of writeLock, and ReentrantReadWriteLockTracer has 
it's own sync object.
As a result, if ReentrantReadWriteLockTracer is used to create checkpoint lock 
(when IGNITE_PDS_LOG_CP_READ_LOCK_HOLDERS=true), 
GridCacheDatabaseSharedManager#checkpointLockIsHeldByThread doesn't work 
correctly: it returns false when checkpoint lock is acquired.



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

[jira] [Created] (IGNITE-13774) Create TC suites for release Python Node.js and PHP clients

[Igor Sapego (Jira)]

Igor Sapego created IGNITE-13774:


 Summary: Create TC suites for release Python Node.js and PHP 
clients
 Key: IGNITE-13774
 URL: https://issues.apache.org/jira/browse/IGNITE-13774
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Affects Versions: 2.9
 Environment: Create TC suites for release of new clients
Reporter: Igor Sapego
 Fix For: 2.10


We now have separate repos for Python, Node.js and PHP thin clients. Need to 
create a TC suites to release them as a separate packages on Ignite site and in 
pip, npm and composer.



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

Re: IGNITE-13680

[Ilya Kasnacheev]

Hello!

I have added you as a contributor, now you should be able to assign tickets
to yourself.

Please also read
https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines
and learn how to use MTCGA bot.

Regards,
-- 
Ilya Kasnacheev


сб, 28 нояб. 2020 г. в 10:00, Nikolay Shubin :

> Hello,
>
> My name is Nikolay Shubin.
> I want to work on the
>
>1. IGNITE-13680 
>
>
>1. ticket.
>
> I have been logged in to issues.apache.org (username shubin), but I seem
> to
> lack permissions to change the ticket's status (make myself the Assignee,
> etc.).
> Could you please upgrade my permission so that I can work on this ticket in
> accordance with the guidelines
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Workingonaticket
>
> Sincerely yours,
> Nikolay Shubin
>

Re: Join to dev community

[Ilya Kasnacheev]

Hello!

Unfortunately, I can't see a JIRA user arostov in
https://issues.apache.org/jira/

Regards,
-- 
Ilya Kasnacheev


сб, 28 нояб. 2020 г. в 10:00, Aleksey Rostov :

> Hello everyone!
> My name is Aleksey Rostov, I want to contribute to Ignite.NET. I am
> currently a senior .net developer in Luxoft company in Saint Petersburg.
> Please, help me to start contributing.
> I have created a jira account - arostov.
>

Re: Issue with custom security plugin and thin clients

[Denis Garus]

Hi!

Node attributes can't be used to spread a thin client's security context.
For this purpose,  you can use a cache of Ignite, a third-party database,
or other tools appropriate to your case.

сб, 28 нояб. 2020 г. в 06:16, Vishwas Bm :

> Hi Denis,
>
>
> Thanks for the reply.
> Yes I was looking for a way to spread the security context to all cluster
> nodes when a thin client(sqlline) gets authenticated.
> I tried to see if I can use node attributes or user attributes to pass the
> information to other nodes. When a cluster of ignite server is already
> formed, this will not help as attributes will not be available on remote
> nodes.
>
> The node attributes cannot be changed at run time and the attributes will
> be available to remote nodes only when they join the cluster.
>
> So I wanted to know, if there is any other way to do this ?
> I checked your poc PR for reference,
> https://github.com/apache/ignite/pull/7375
>
> In thin client case authenticate node will not be called but authenticate
> method is getting called.
>
>
> Regards,
> Vishwas
>
>
> On Fri, 27 Nov, 2020, 14:29 Denis Garus,  wrote:
>
> > Hello!
> >
> >
> > If I understood your problem correctly, you need to make a thin client's
> > security context allowed on a remote node.
> >
> > When a security plugin does authenticate a thin client, it should spread
> > the thin client's security context on the cluster.
> >
> > How a security context will be transmitted to a remote node is up to the
> > plugin's developers.
> >
> > Also, you have to implement the
> GridSecurityProcessor.securityContext(UUID
> > subjId) method,
> >
> > the way this method is used in Ignite can see in the task description
> [1].
> >
> >
> >
> >
> >1. https://issues.apache.org/jira/browse/IGNITE-12759
> >
> >
> > чт, 26 нояб. 2020 г. в 10:01, Vishwas Bm :
> >
> > > Hi,
> > >
> > > I was facing an issue with a custom security plugin and thin remote
> > client.
> > > I am using Ignite 2.9.0 version and I am hitting below issue
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-41%3A+Security+Context+of+thin+client+on+remote+nodes
> > >
> > >
> > > I had asked the question in the user listing but unfortunately I did
> not
> > > get any reply.
> > > So I am posting this question here:
> > >
> > >
> > >
> >
> http://apache-ignite-users.70518.x6.nabble.com/Query-on-implementing-GridSecurityProcessor-td34672.html
> > >
> > >
> > > *Thanks & Regards,*
> > >
> > > *Vishwas *
> > >
> >
>

[jira] [Created] (IGNITE-13773) Ignite Docs: Port SQL Tooling from readme.io

[YuJue Li (Jira)]

YuJue Li created IGNITE-13773:
-

 Summary: Ignite Docs: Port SQL Tooling from readme.io
 Key: IGNITE-13773
 URL: https://issues.apache.org/jira/browse/IGNITE-13773
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.9
Reporter: YuJue Li
 Fix For: 2.9.1


The content in the link below is missing from the new version of the document:

[https://apacheignite-sql.readme.io/docs/sql-tooling]

 



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