Re: [VOTE] Move Ignite 2.x sources to JDK11

[18624049226]

+1

在 2024/7/16 16:38, Pavel Tupitsyn 写道:

+1

On Tue, Jul 16, 2024 at 10:14 AM Zhenya Stanilovsky
  wrote:


Great !
+1


Hi Igniters,

I'd like to start a voting process about moving Ignite 2.x sources to
JDK11. Discussion of the proposal is here [1].

The plan is as follows:
1. Upgrade all TeamCity jobs from jdk1.8 to jdk11.
2. Review and merge the patch [2] that changes `maven.source.version` in
Ignite's pom.xml to 11. This means that Apache Ignite 2.17 will be built
using jdk11.
3. Clean up all code that relies on jdk1.8 (docs, ignite-tools for 1.8,
pom.xml configs, etc).

I consider this vote as a *code modification* vote, see voting guidelines
[3].

+1 - to accept the plan above
0 - don’t care either way
-1 - DO NOT accept the plan (*veto *[3], please explain why)

This vote will be open for at least 4 days till Saturday July 20, 2024,
10:00 Moscow TZ.

[1]https://lists.apache.org/thread/v81wt7xzvrk6o04sb2k4fmydctqgtjlg
[2]https://issues.apache.org/jira/browse/IGNITE-22669
[3]https://www.apache.org/foundation/voting.html

Re: Ignite Extensions

[18624049226]

Due to some fix, the spring-data-ext module also needs to be released.

在 2024/1/23 00:19, Ivan Daschinsky 写道:

Also, I have updated dependencies and fixed native BLAS integration (tested
on ubuntu 22.04 with Intel MKL)

пн, 22 янв. 2024 г. в 19:18, Ivan Daschinsky:


Hi, Steven. Currently I am preparing an initial release of the ML
extension. Just thinking about creating a new thread and here you are :)
The release branch is ready, I just need to prepare artifacts and upload
them to staging. Then I am going to start the vote thread.


https://github.com/apache/ignite-extensions/tree/release/ignite-ml-ext-1.0.0

пн, 22 янв. 2024 г. в 18:15, Stephen Darlington:


Hi all,

With Ignite 2.16 now out, is there any movement towards releasing some of
the Ignite Extensions?

We have a question in the user mailing list about the ML extensions, which
were moved from core to extensions. And I'd like to see the SpringBoot
extensions released so that we can support current versions (3.x does not
work with Ignite out of the box).

Regards,
Stephen



--
Sincerely yours, Ivan Daschinskiy

Re: About control.sh --meta command

[18624049226]

Hi team,

I think there are two solutions to this issue:
1. Removing the "experimental" status of this feature;
2. In the help of control scripts, increase the output of experimental 
features.


Which is better?

在 2023/5/17 19:50, 18624049226 写道:


Hi team,

It is understood that the Control Script has a --meta command, which 
developed in the following ticket:


https://issues.apache.org/jira/browse/IGNITE-13154

The official document does not provide an introduction to this 
feature, and due to the "experimental", there is no output in the 
command line help, so almost no users are aware of this feature.


This feature is very useful in some scenarios.

I would like to ask why this feature is labeled as "experimental"? If 
there are no special considerations, I suggest removing the 
"experimental" status of this feature.

About control.sh --meta command

[18624049226]

Hi team,

It is understood that the Control Script has a --meta command, which 
developed in the following ticket:


https://issues.apache.org/jira/browse/IGNITE-13154

The official document does not provide an introduction to this feature, 
and due to the "experimental", there is no output in the command line 
help, so almost no users are aware of this feature.


This feature is very useful in some scenarios.

I would like to ask why this feature is labeled as "experimental"? If 
there are no special considerations, I suggest removing the 
"experimental" status of this feature.

Re: [VOTE] Release Apache Ignite 2.15.0 RC0

[18624049226]

The following PR should be merged.

But I think this should not affect the voting.

https://issues.apache.org/jira/browse/IGNITE-19378

在 2023/4/27 12:36, Pavel Tupitsyn 写道:

+1 (binding)

Downloaded binaries, tested node startup, NuGet packages, .NET examples.

On Wed, Apr 26, 2023 at 10:52 PM Alex Plehanov
wrote:


Dear Community,

The release candidate is ready.

I have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.15.0-rc0/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.15.0-rc0/

The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1558/

Tag name is 2.15.0-rc0:

https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.15.0-rc0

2.15.0 most important changes:
* Implemented incremental snapshots.
* Java thin client improvements (logging, connections balancing, events
listening, endpoints discovery)
* Calcite based SQL engine improvements (memory quotas, index scans
optimisations).
* Reworked permission management for system tasks.
* Removed deprecated functionality (daemon nodes, visorcmd, legacy JMX
beans).

RELEASE NOTES:

https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.15

Complete list of resolved issues:

https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.15'))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20('CLOSED'%2C%20'RESOLVED')%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
<
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.15%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority

DEVNOTES

https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.15

The vote is formal, see voting guidelines
https://www.apache.org/foundation/
voting.html

+1 - to accept Apache Ignite 2.15.0-rc0
0 - don't care either way
-1 - DO NOT accept Apache Ignite Ignite 2.15.0-rc0 (explain why)

See notes on how to verify release here
https://www.apache.org/info/verification.html
and

https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification

This vote will be open till Tue May 2, 2023, 07:00 UTC.

https://www.timeanddate.com/countdown/vote?iso=20230502T07&p0=0&msg=VOTE+on+the+Apache+Ignite+Release+2.15.0+RC0&font=sanserif

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

[18624049226]

Hi Alex,

The following PR need to be merged:

https://issues.apache.org/jira/browse/IGNITE-19349

在 2023/4/19 02:16, Alex Plehanov 写道:

Hello,

I'm announcing a code freeze for the 2.15 release. Only blockers are
accepted to the release since this moment.

вт, 11 апр. 2023 г. в 13:25, Pavel Tupitsyn:


Alex,

Just in case, Bugyard credentials are available to all PMCs in the private
SVN repo, see [1]


a lot of changes from 'ignite' to 'gridgain'

That's not good, requested changes on that PR.

[1]

https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-DocumentationFeedbackviaBugyard

On Tue, Apr 11, 2023 at 11:58 AM Alex Plehanov
wrote:


Hello,

I've merged and cherry-picked to 2.15 IGNITE-17892 and IGNITE-18260. As

for

IGNITE-18496, I don't have access to the bugyard and can't validate all
changes. For example, there are a lot of changes from 'ignite' to
'gridgain', not sure if it's correct or not. As far as this ticket will

be

in master I will cherry-pick it into 2.15.

вт, 11 апр. 2023 г. в 03:03, 18624049226<18624049...@163.com>:


Hi Alex,

Can you help merge the following PR into 2.15 branch? small doc fix.

https://issues.apache.org/jira/browse/IGNITE-17892

https://issues.apache.org/jira/browse/IGNITE-18496

https://issues.apache.org/jira/browse/IGNITE-18260

在 2023/4/10 21:31, Alex Plehanov 写道:

Hello Igniters,

I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new

issues

if needed.

The 2.15 scope is frozen. Unresolved not-blocking issues will be

moved

to

the next release on the code freeze stage.


пт, 7 апр. 2023 г. в 17:03, Alex Plehanov:


Hello Igniters,

I have created the 2.15 release page [1].

Also, I've removed from the 2.15 scope some unresolved tickets

(unassigned

and without activity for a long time). Now we have 13 unresolved

tickets

(not related to documentation).

I have a plan to cut the release branch next monday (10 Apr). I will
inform you accordingly, when it will be done.


[1] :


https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15

пт, 31 мар. 2023 г. в 13:18, Jian Chen:


+1

Вячеслав Коптилин于2023年3月31日 周五下午6:12写道：


+1

ср, 29 мар. 2023 г. в 21:57, Alex Plehanov<

plehanov.a...@gmail.com

:

Dear Ignite Community!

I suggest starting Apache Ignite 2.15 release activities.

We've accumulated more than two hundred resolved issues [1] with

new

features and bug fixes which are waiting for release.
The major changes related to the proposed release:
- Incremental snapshots.
- Java thin client improvements (logging, connections balancing,
  events listening, endpoints discovery)
- Calcite based SQL engine improvements (memory quotas, index

scans

optimisations).
- Reworked permission management for system tasks.
- Removed some deprecated functionality (daemon nodes, visorcmd,

legacy

JMX

beans)
etc.

I want to propose myself to be the release manager of the

planning

release.

I propose the following timeline:

Scope Freeze: April 08, 2023
Code Freeze: April 15, 2023
Voting Date: April 22, 2023
Release Date: April 29, 2023

[1].



https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)

WDYT?

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

[18624049226]

Hi Alex,

Can you help merge the following PR into 2.15 branch? small doc fix.

https://issues.apache.org/jira/browse/IGNITE-17892

https://issues.apache.org/jira/browse/IGNITE-18496

https://issues.apache.org/jira/browse/IGNITE-18260

在 2023/4/10 21:31, Alex Plehanov 写道:

Hello Igniters,

I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new issues
if needed.

The 2.15 scope is frozen. Unresolved not-blocking issues will be moved to
the next release on the code freeze stage.


пт, 7 апр. 2023 г. в 17:03, Alex Plehanov:


Hello Igniters,

I have created the 2.15 release page [1].

Also, I've removed from the 2.15 scope some unresolved tickets (unassigned
and without activity for a long time). Now we have 13 unresolved tickets
(not related to documentation).

I have a plan to cut the release branch next monday (10 Apr). I will
inform you accordingly, when it will be done.


[1] :
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15

пт, 31 мар. 2023 г. в 13:18, Jian Chen:


+1

Вячеслав Коптилин于2023年3月31日 周五下午6:12写道：


+1

ср, 29 мар. 2023 г. в 21:57, Alex Plehanov:


Dear Ignite Community!

I suggest starting Apache Ignite 2.15 release activities.

We've accumulated more than two hundred resolved issues [1] with new
features and bug fixes which are waiting for release.
The major changes related to the proposed release:
- Incremental snapshots.
- Java thin client improvements (logging, connections balancing,
 events listening, endpoints discovery)
- Calcite based SQL engine improvements (memory quotas, index scans
optimisations).
- Reworked permission management for system tasks.
- Removed some deprecated functionality (daemon nodes, visorcmd,

legacy

JMX

beans)
etc.

I want to propose myself to be the release manager of the planning

release.

I propose the following timeline:

Scope Freeze: April 08, 2023
Code Freeze: April 15, 2023
Voting Date: April 22, 2023
Release Date: April 29, 2023

[1].



https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)

WDYT?

Re: Ignite-spring dependency on ignite-indexing

[18624049226]

Hiteam,

Because Ignite3.0 is a new product and the community has developed a new 
SQL engine, the situation has changed a lot. I think the community 
should promote the merge of this simple patch, this wrong dependency may 
cause new problems.


在 2022/12/23 08:32, 18624049226 写道:

https://issues.apache.org/jira/browse/IGNITE-5713

在 2022/12/23 00:09, mwiesenberg 写道:

Hi,
  Is there any reason the ignite spring pom has ignite indexing as a
dependency? I was switching from h2 to calcite and observed h2 was by
default still being brought in via ignite spring, for seemingly no 
reason.


If there's no reason, I'm happy to submit an MR to remove, please 
enable my

JIRA account, mberg, as a contributor. Thank you!

Mike

Re: Ignite-spring dependency on ignite-indexing

[18624049226]

https://issues.apache.org/jira/browse/IGNITE-5713

在 2022/12/23 00:09, mwiesenberg 写道:

Hi,
  Is there any reason the ignite spring pom has ignite indexing as a
dependency? I was switching from h2 to calcite and observed h2 was by
default still being brought in via ignite spring, for seemingly no reason.

If there's no reason, I'm happy to submit an MR to remove, please enable my
JIRA account, mberg, as a contributor. Thank you!

Mike

Re: [DISCUSSION] Removal of ignitevisorcmd

[18624049226]

Visor has a 'cache -clear' function, this function is very useful, 
especially in some O&M scenarios.


Because Ignite does not support the TRUNCATE command, it is necessary to 
provide a high-performance clear table data command.


在 2022/12/2 19:13, Nikolay Izhikov 写道:

THanks, Slava, Stephen.

Ticket to reimplement cache scan created -
https://issues.apache.org/jira/browse/IGNITE-18320

пт, 2 дек. 2022 г. в 13:30, Stephen Darlington <
stephen.darling...@gridgain.com>:


One option that’s in Visor but not control.sh is the ability to view cache
content (cache -scan). I do hear of people using that.


On 2 Dec 2022, at 09:17, Andrey Mashenkov

wrote:

Hi Igniters,

I agree with Slava, we have to provide alternative ways for users before
dropping a feature that just worked.
A user may use some feature for a long time without any issues, so, this

is

why there is no mention in chats/mails.
I mean here, the feature is not only the whole visor command, but a

command

option that just makes UX better.

I think we can revise visor features, which are not supported by
control.sh, and create an umbrella ticket for supporting in control.sh.
Set this ticket either as 'required' for a 'dropping visor ticket', or

as a

blocker for the next release if visor dropping will come first.

On Fri, Dec 2, 2022 at 11:09 AM Nikolay Izhikov

wrote:

Hello, Slava.


However, do we have a list of useful features that do not exist in our

control utility?

I don't have the list on hand.
Do you have some feature in mind that must be transferred in control.sh?

I don't find any mentions of visorcmd on user list and in user chats so

my

guess is - this utility is not used by the users in any way.
Do you have some other inputs?

If yes, don't hesitate to create a ticket with the IEP-94 label.


чт, 1 дек. 2022 г. в 19:11, Вячеслав Коптилин 
:

Hi Igniters,

I fully support the idea to stop supporting Visor and removing its
implementation.
However, do we have a list of useful features that do not exist in our
control utility?
Perhaps, it makes sense to reimplement such functionality and provide

it

based on control.sh script.

Thanks,
Slava.

чт, 1 дек. 2022 г. в 15:51, Nikolay Izhikov:


PR is ready for review -https://github.com/apache/ignite/pull/10411

чт, 1 дек. 2022 г. в 16:49, Taras Ledkov:


Hi,

+1 for remove Visor related code.
Unfortunately we have to migrate `control-utility` to use

IgniteClient

(thin client) before drop GridClient. I guess we will do it in the

future.

Also, the old thin JDBC based on the GridClient (classes placed at

the

org.apache.ignite.internal.jdbc.*) must be removed.



--
Best regards,
Andrey V. Mashenkov

Re: A new feedback has been added : 96

[18624049226]

This issue is fixed in https://issues.apache.org/jira/browse/IGNITE-17892.

在 2022/11/29 20:53, Bugyard 写道:

A new feedback has been added, go to bugyard.io to see all the details...

https://bugyard.io

A new feedback has been added

"Change to DataRegionConfiguration#cdcEnabled because it is set per DataRegion" 
  by shishkovilja

View feedbackhttps://app.bugyard.io/web/app/rycqZJDyY/f/638600a2cebcce0014732bf6

Re: [jira] [Assigned] (IGNITE-17857) The native client does not need to verify the configuration consistency of the DeploymentSpi

[18624049226]

Hello,

Is anyone willing to help check the ticket and merge the following PR?

https://github.com/apache/ignite/pull/10297

在 2022/10/10 11:02, YuJue Li (Jira) 写道:

  
[https://issues.apache.org/jira/browse/IGNITE-17857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
  ]

YuJue Li reassigned IGNITE-17857:
-

 Assignee: YuJue Li


The native client does not need to verify the configuration consistency of the 
DeploymentSpi


 Key: IGNITE-17857
 URL:https://issues.apache.org/jira/browse/IGNITE-17857
 Project: Ignite
  Issue Type: Improvement
  Components: clients
Affects Versions: 2.14
Reporter: YuJue Li
Assignee: YuJue Li
Priority: Minor
 Fix For: 2.15

 Attachments: IgniteClient.java, e.log, example-deploy.xml


start a server node with example-deploy.xml by ignite.sh
start a native client with IgniteClient.java
then error.
Normally, the client node does not need to verify the configuration consistency 
of the DeploymentSpi.
Whether the client needs to configure DeploymentSpi should be decided by the 
user.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

memory defragmentation

[18624049226]

hello team,

https://ignite.apache.org/docs/latest/memory-architecture#memory-defragmentation

Does this memory defragmentation function really exist?
If this function is not available, this part of the document should be 
deleted.

Re: [jira] [Created] (IGNITE-17658) Unable to make field private final java.lang.Class java.lang.invoke.SerializedLambda.capturingClass accessible: module java.base does not "opens java.lang.invoke" t

[18624049226]

Hello,

Is there anyone willing to help merge the following PR?

https://github.com/apache/ignite/pull/10242

在 2022/9/9 11:24, YuJue Li (Jira) 写道:

YuJue Li created IGNITE-17658:
-

  Summary: Unable to make field private final java.lang.Class 
java.lang.invoke.SerializedLambda.capturingClass accessible: module java.base does not 
"opens java.lang.invoke" to unnamed module
  Key: IGNITE-17658
  URL:https://issues.apache.org/jira/browse/IGNITE-17658
  Project: Ignite
   Issue Type: Bug
   Components: general
 Affects Versions: 2.13
  Environment: jdk17
 Reporter: YuJue Li
 Assignee: YuJue Li
  Fix For: 2.15
  Attachments: IgniteClient.java

start a node with peerClassLoadingEnabled = true;

execute the reproducer;

then error occurs:

[19:14:24,425][SEVERE][pub-#17][BinaryContext] Failed to deserialize object 
[typeName=o.a.i.i.processors.closure.GridClosureProcessor$C4]
java.lang.reflect.InaccessibleObjectException: Unable to make field private 
final java.lang.Class java.lang.invoke.SerializedLambda.capturingClass 
accessible: mo
dule java.base does not "opens java.lang.invoke" to unnamed module @694e1548



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [jira] [Updated] (IGNITE-13612) Ignite Docs: Duplicate document

[18624049226]

Hello,

Is there anyone willing to help merge the following PR?

https://github.com/apache/ignite/pull/1

在 2022/4/27 10:29, YuJue Li (Jira) 写道:

  
[https://issues.apache.org/jira/browse/IGNITE-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
  ]

YuJue Li updated IGNITE-13612:
--
 Fix Version/s: 2.13
(was: 2.14)


Ignite Docs: Duplicate document
---

 Key: IGNITE-13612
 URL:https://issues.apache.org/jira/browse/IGNITE-13612
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.9
Reporter: YuJue Li
Assignee: YuJue Li
Priority: Minor
 Fix For: 2.13

  Time Spent: 10m
  Remaining Estimate: 0h

The following two documents are duplicate. Keep one.
[https://ignite.apache.org/docs/latest/data-structures/atomic-sequence]
[https://ignite.apache.org/docs/latest/data-structures/id-generator]
  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [jira] [Updated] (IGNITE-11404) Document CREATE TABLE "parallelism" option

[18624049226]

Hello,

Is there anyone willing to help merge the following PR?

https://github.com/apache/ignite/pull/10001

在 2022/4/27 11:05, YuJue Li (Jira) 写道:

  
[https://issues.apache.org/jira/browse/IGNITE-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
  ]

YuJue Li updated IGNITE-11404:
--
 Fix Version/s: 2.13
(was: 2.14)


Document CREATE TABLE "parallelism" option
--

 Key: IGNITE-11404
 URL:https://issues.apache.org/jira/browse/IGNITE-11404
 Project: Ignite
  Issue Type: Task
  Components: documentation, sql
Reporter: Vladimir Ozerov
Assignee: YuJue Li
Priority: Major
 Fix For: 2.13

  Time Spent: 10m
  Remaining Estimate: 0h

We added new {{PARALLELISM}} option:
{code}
CREATE TABLE ... WITH "parallelism = 4"
{code}
This option affect query parallelism which is otherwise set from 
{{CacheConfiguration.queryParallelism}}.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [jira] [Assigned] (IGNITE-17432) ignitevisorcmd can't run in jdk17 env

[18624049226]

Hello,

Is there anyone willing to help merge the following PR?

https://github.com/apache/ignite/pull/10173

在 2022/7/28 11:35, YuJue Li (Jira) 写道:

  
[https://issues.apache.org/jira/browse/IGNITE-17432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
  ]

YuJue Li reassigned IGNITE-17432:
-

 Assignee: YuJue Li


ignitevisorcmd can't run in jdk17 env
-

 Key: IGNITE-17432
 URL:https://issues.apache.org/jira/browse/IGNITE-17432
 Project: Ignite
  Issue Type: Bug
  Components: cli
Affects Versions: 2.13
Reporter: YuJue Li
Assignee: YuJue Li
Priority: Minor
 Fix For: 2.14


Unrecognized VM option 'MaxPermSize=128M'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

[18624049226]

ignite-mesos?

在 2022/5/13 22:51, Maxim Muzafarov 写道:

Folks,

I've found that the following modules are rarely used and haven't been
change for a few years, but  they are released each time Ignite being
released. It seems we can safely move all of them to the Extensions
project.

The list:
- ignite-yarn
- ignite-geospatial
- ignite-schedule

WDYT?

Re: [VOTE] Release Apache Ignite 2.13.0 RC1

[18624049226]

I think the following commit should be included in 2.13:

IGNITE-15712: Documentation: Invalid documentation about 
SqlViewMetricExporterSpi


just doc issue.

在 2022/4/20 16:21, Nikita Amelchev 写道:

Zhenya, Hi!

Additional checks are available for users included into the release
group on TeamCity. Make sure you are in this group.

ср, 20 апр. 2022 г. в 09:19, Zhenya Stanilovsky:


Nikita, thanks !  I found that below link is unavailable:




TC [2] Compare w/ Previous Release
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6398741

Re: [jira] [Assigned] (IGNITE-16866) Integer value is out of bounds when the dataregion maxSize is large enough

[18624049226]

Hello team,

Is there anyone willing to help merge the following PR?

https://github.com/apache/ignite/pull/9983

在 2022/4/17 09:14, YuJue Li (Jira) 写道:

  
[https://issues.apache.org/jira/browse/IGNITE-16866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
  ]

YuJue Li reassigned IGNITE-16866:
-

 Assignee: YuJue Li


Integer value is out of bounds when the dataregion maxSize is large enough
--

 Key: IGNITE-16866
 URL:https://issues.apache.org/jira/browse/IGNITE-16866
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.12
Reporter: YuJue Li
Assignee: YuJue Li
Priority: Minor
 Fix For: 2.14

 Attachments: 2022-04-17_09-12.png


In the Random2LruPageEvictionTracker and RandomLruPageEvictionTracker, 
trackingSize is int, Therefore, when the maxSize of the dataregion is large 
enough (for example, more than 1.2T), execute GridUnsafe.allocateMemory to 
allocate memory, the maximum value of int will be exceeded.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [jira] [Assigned] (IGNITE-15712) Documentation: Invalid documentation about SqlViewMetricExporterSpi

[18624049226]

Hello team,

Is there anyone willing to help merge the following PR?

https://github.com/apache/ignite/pull/9970

在 2022/4/13 19:52, YuJue Li (Jira) 写道:

  
[https://issues.apache.org/jira/browse/IGNITE-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
  ]

YuJue Li reassigned IGNITE-15712:
-

 Assignee: YuJue Li


Documentation: Invalid documentation about SqlViewMetricExporterSpi
---

 Key: IGNITE-15712
 URL:https://issues.apache.org/jira/browse/IGNITE-15712
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.10, 2.11
Reporter: Ivan Daschinsky
Assignee: YuJue Li
Priority: Major
 Fix For: 2.13


Since SqlViewMetricExporterSpi is moved to internal package and is enabled by 
default (see IGNITE-12922), documentation should be updated.
However, currently it contains wrong recipies about how to configure 
SqlMetricsExporter



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [jira] [Created] (IGNITE-16617) Delete the sections related to FIRSTVALUE and LASTVALUE functions in the document

[18624049226]

Is there anyone willing to help merge the following PR?

https://github.com/apache/ignite/pull/9845

在 2022/2/22 18:57, YuJue Li (Jira) 写道:

YuJue Li created IGNITE-16617:
-

  Summary: Delete the sections related to FIRSTVALUE and LASTVALUE 
functions in the document
  Key: IGNITE-16617
  URL:https://issues.apache.org/jira/browse/IGNITE-16617
  Project: Ignite
   Issue Type: Improvement
   Components: documentation
 Affects Versions: 2.12
 Reporter: YuJue Li
  Fix For: 2.13


[https://ignite.apache.org/docs/latest/sql-reference/aggregate-functions]

Ignite does not support these two functions, so community should delete the 
related contents from the document.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: New Ignite Website: Released and Check the Dev Instructions

[18624049226]

Hi,

It seems that all documents are unpublished version 2.12 documents?

For example, the following documents are unpublished IndexQuery:

https://ignite.apache.org/docs/2.11.0/key-value-api/using-cache-queries
https://ignite.apache.org/docs/2.10.0/key-value-api/using-cache-queries
https://ignite.apache.org/docs/2.9.0/key-value-api/using-cache-queries

In addition, the menu tree on the left side of the document should be 
shared by all document versions. Is this unreasonable?


在 2021/12/15 02:29, Mauricio Stekl 写道:

Thank you, Erlan. I merged your first commit into the prod website.
Welcome to the Ignite community!

Best,
Mauricio

On Tue, Dec 14, 2021 at 4:40 AM Erlan Aytpaev  wrote:


Hi Igniters,

I've added the "Extensions" section on the "Downloads" page. Please review
my pull requesthttps://github.com/apache/ignite-website/pull/91.
This is my first commit. And I'm going to continue contributing updates on
the website.

Best Regards,
Erlan.

On Tue, Dec 14, 2021 at 9:55 AM Mauricio Stekl
wrote:


Hi,
I noticed the "Extensions" section was not merged correctly into the
Downloads page. I have created a ticket
https://issues.apache.org/jira/browse/IGNITE-16112, and we'll be solving
this as soon as possible. My apologies for the inconvenience

Best,
Mauricio

On Mon, Dec 13, 2021 at 4:46 PM Denis Magda  wrote:


Igniters,

Please welcome the new Ignite website:https://ignite.apache.org
Hope you like it!

The website uses gulpjs to simplify the dev/maintenance cycles, thus, I
would encourage all of you who release Ignite (and update the downloads
page) or edit any other pages to check the updated instruction:
https://cwiki.apache.org/confluence/display/IGNITE/Website+Development


-
Denis

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[18624049226]

check again, 15503 not cherry-pick, right?

在 2021/9/14 15:55, Shishkov Ilya 写道:

Should the following two issue be merged into the ignite-2.11 branch?

Hi, as I see, both tickets are fixed in 2.10 and 2.11.

вт, 14 сент. 2021 г. в 04:13, 18624049226<18624049...@163.com>:


Should the following two issue be merged into the ignite-2.11 branch?

https://issues.apache.org/jira/browse/IGNITE-14404

https://issues.apache.org/jira/browse/IGNITE-15503

在 2021/9/13 17:12, Pavel Tupitsyn 写道:

+1

Downloaded binary packages, started a cluster with a few nodes, tested

new

.NET examples.

On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
   wrote:


Thanks Maxim !
I tries to compare this ver with 2.10 (some performance tests with
persistence and transactional\atomic payload) and seems all ok there.
+1 from me.


Dear Community,


The release candidate for the 2.11 version is ready.


I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/

The following staging can be used for testing:


https://repository.apache.org/content/repositories/orgapacheignite-1526/
https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite

Tag name is 2.11.0-rc2:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2

RELEASE_NOTES:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11

Complete list of resolved issues:


https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11%27

))

DEVNOTES:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.11

Additional checks have been performed (available for users included

into

the release group on TeamCity).

TC [Check RC: Licenses, compile, chksum]


https://ci.ignite.apache.org/viewLog.html?buildId=6176219&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildResultsDiv

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

+1 - to accept Apache Ignite 2.11.0-rc2
0 - don't care either way
-1 - DO NOT accept Apache Ignite Ignite 2.11.0-rc2 (explain why)

See notes on how to verify release here
https://www.apache.org/info/verification.html
and


https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification

This vote will be open for 4 days until Thu Sep 16, 12:00 2021 (Moscow
time).
Please, write me down the thread if you need additional time to check
the release.


https://www.timeanddate.com/countdown/vote?iso=20210916T12&p0=166&msg=%5BVOTE%5D+Release+Apache+Ignite+2.10.0+RC2&font=serif&csz=1

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[18624049226]

Should the following two issue be merged into the ignite-2.11 branch?

https://issues.apache.org/jira/browse/IGNITE-14404

https://issues.apache.org/jira/browse/IGNITE-15503

在 2021/9/13 17:12, Pavel Tupitsyn 写道:

+1

Downloaded binary packages, started a cluster with a few nodes, tested new
.NET examples.

On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
  wrote:



Thanks Maxim !
I tries to compare this ver with 2.10 (some performance tests with
persistence and transactional\atomic payload) and seems all ok there.
+1 from me.



Dear Community,


The release candidate for the 2.11 version is ready.


I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/

The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1526/


https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite

Tag name is 2.11.0-rc2:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2

RELEASE_NOTES:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11

Complete list of resolved issues:


https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11%27
))

DEVNOTES:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.11


Additional checks have been performed (available for users included into
the release group on TeamCity).

TC [Check RC: Licenses, compile, chksum]


https://ci.ignite.apache.org/viewLog.html?buildId=6176219&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildResultsDiv


The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

+1 - to accept Apache Ignite 2.11.0-rc2
0 - don't care either way
-1 - DO NOT accept Apache Ignite Ignite 2.11.0-rc2 (explain why)

See notes on how to verify release here
https://www.apache.org/info/verification.html
and


https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification


This vote will be open for 4 days until Thu Sep 16, 12:00 2021 (Moscow
time).
Please, write me down the thread if you need additional time to check
the release.


https://www.timeanddate.com/countdown/vote?iso=20210916T12&p0=166&msg=%5BVOTE%5D+Release+Apache+Ignite+2.10.0+RC2&font=serif&csz=1

Re: [ANNOUNCE] Apache Ignite spring-data-all-ext extensions 1.0.0 released

[18624049226]

Igniters,

It seems that these artifact have not been uploaded to Maven Repo? Will 
it be uploaded with ignite 2.11?


This release does not include spring-tx-ext, but the documentation of 
this artifact has been merged into the ignite-2.11 branch, What's wrong?


在 2021/7/7 下午1:49, Nikita Amelchev 写道:

The Apache Ignite Community is pleased to announce the release of
Apache Ignite Spring Data extensions 1.0.0.

The following integrations were migrated to the Apache Ignite
Extensions repository:

- Spring Data 2.2 extension.
- Spring Data 2.0 extension.
- Spring Data extension.

Release notes:
https://ignite.apache.org/releases/ext/spring-data-all-1.0.0/release_notes.html

The sources package is available here:
https://downloads.apache.org/ignite/ignite-extensions/ignite-spring-data-all-ext/1.0.0/

Please let us know if you have any problems
https://ignite.apache.org/community/resources.html#ask

Data out of sync between maillist and nabble.com

[18624049226]

Hi team,

It seems that since mid June, the data between maillist and nabble.com 
is no longer synchronized, which affects the user experience.

Is this a configuration error, or is a rule changed?

Re: IGNITE-13364: Improve index inline defaults

[18624049226]

Hello team,

I think this is a very valuable optimization. This patch has been 
developed for a long time, I don't think there is any reason to continue 
to delay the release of this patch to version 2.12.

Is anyone willing to push this forward and merge this patch into the master?

2021/1/27 下午4:52, Maxim Muzafarov 写道:

Stanislav,


I think the most compatibility impact will be on the in-memory caches with SQL 
and without explicitly specified inline sizes.

I don't think that this is `true` compatibility issue. But I think we
should at least mentioned it on our documentation pages and in the
release notes. So, I'm +1 to proceed with the merge.

Should we include the issue into 2.10 release?

On Fri, 8 Jan 2021 at 16:50, Stanislav Lukyanov  wrote:

Hi Igniters,

I'd like to discuss the change implemented by Evgeniy Rudenko in the ticket 
https://issues.apache.org/jira/browse/IGNITE-13364.
I see that the fix is ready for review and merging, and I'm interested in it so 
I'd like to pick it up on the last mile.
I also wanted to bring community's attention to it before the merge as it 
changes the default behavior.

The patch changes how SQL index inline size is calculated.

Specifically:

1. When inline size is calculated for a variable-sized field, a constant 10 
(configurable via IGNITE_VARIABLE_TYPE_DEFAULT_INDEX_SIZE) is added to the 
calculated size instead of setting the entire calculation result to 10.
For example, consider the following cases

Index (int, int, string)
Before the change: inline size = 10
After the change: inline size = 5 + 5 + 10 = 20

Index (long, long, long, long,  string)
Before the change: inline size = 10
After the change: inline size = 9 + 9 + 9 + 9 + 10 = 46

2. If there is a VARCHAR_FIXED, e.g. VARCHAR(5), then instead of the default 
IGNITE_VARIABLE_TYPE_DEFAULT_INDEX_SIZE Ignite will use the value provided in 
the calculation

3. If the calculated size exceeds IGNITE_MAX_INDEX_PAYLOAD_SIZE_DEFAULT=64, it 
will be truncated to 64.

All of this only affects calculated inline sizes of new indexes.
Existing indexes should not be affected.
Indexes with explicitly specified inline size should not be affected.

I think the most compatibility impact will be on the in-memory caches with SQL 
and without explicitly specified inline sizes.
After the upgrade these caches may slightly increase in size (because the 
inline is likely to become bigger) while SQL is also likely to become faster.

Please comment.
If there are no concerns, I'll proceed with finding a committer to review and 
merge the fix at the end of the next week.

Thanks,
Stan

Re: Apache Ignite 2.11

[18624049226]

hello,

can someone can help to merge the following patch into master?

https://issues.apache.org/jira/browse/IGNITE-12852

This patch has been completed for a long time, and I think it is a 
valuable one.


在 2021/6/3 下午11:12, Dmitry Pavlov 写道:

Sure, thanks for your reply

Folks, could you please advice how to setup JIRA account integration for 
non-committers?

For the page
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
I can see all issues, but Alexey's login seems to be not sufficient. Can wiki 
admins set up smth? Or Alexey should do some setup on his own?

On 2021/06/03 14:55:25, Maksim Timonin  wrote:

I mean I'm OK to release it with 2.12. So, I am glad to hear there are
chances for 2.11, but I guess we can postpone it.


On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov  wrote:


ok, Maksim, keep us posted.

We're in the middle of paperwork rigth now, so there is a chance ))

On 2021/06/03 14:30:55, Maksim Timonin  wrote:

Regarding non-SQL index API it really depends on readiness. I guess if

it

is not in the master, we can skip and release it next time.

Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within

the

next release.

On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov  wrote:


Hi Alexey,

Releasing master as-is makes sence for me.

Regarding non-SQL index API it really depends on readiness. I guess if

it

is not in the master, we can skip and release it next time.

We've a bit overdue initial scope freeze date. It's not a big deal, but
still makes sense to start discussion, create and share wiki page and
create branch.

Since committer privileges required to create branch, could you please
notify me in advance.

Sincerely,
Dmitriy Pavlov

On 2021/06/03 14:08:34, ��  <
olive.c...@gmail.com> wrote:

:scope:

Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11

release

Let's start discussion

[1]

https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

On 2021/05/13 14:27:33, Dmitry Pavlov  wrote:

Hi Alexey,

:pmc to sign distribution:
Formally, only PMC member can be a release manager, so part of

activities should be picked up by committer and PMC member. If noone

else

want to help you here, I would.

:timeline:
And, could you estimate all phases of the release.

:scope:
I guess we can just pick up master current state and release it.

But

if someone has some ideas if we should wait for particular feature to

be

completed before branch divergence/release candidate build, please let

know.

Sincerely,
Dmitriy Pavlov

On 2021/05/13 09:45:02, Алексей Гидаспов 

wrote:

Dear Ignite Community!

I suggest starting Apache Ignite 2.11 release activities. Also

suggest

myself to be a release manager for this release. I plan release

at

the end

of june 2021.

___

Best Regards,
Alexey Gidaspov

Re: Proposal to remove explicit "GC disable" startup suggestion

[18624049226]

Does the document also need to be adjusted?

https://ignite.apache.org/docs/latest/perf-and-troubleshooting/memory-tuning

在 2021/5/18 上午1:46, Valentin Kulichenko 写道:

Got it. The proposal makes sense to me, let's remove the suggestion.

-Val

On Sun, May 16, 2021 at 5:50 AM Ilya Korol  wrote:


In some circumstances there could be a state when direct buffers
(instantiated for IO purposes) hold too many memory and to get this
memory back JVM calls System.gc() (as was mentioned earlier by Ivan
Daschinsky):

ByteBuffer.allocateDirect(capacity)
  new DirectButeBuffer(capacity)
  Bits.reserveMemory(size, cap)
...
  System.gc() // if optimistic attempts to reserve required
memory failed

See also:
[1]

http://www.mastertheboss.com/other/java-stuff/troubleshooting-outofmemoryerror-direct-buffer-memory

See

16.05.2021 01:21, Valentin Kulichenko пишет:

Hi Ilya,

Out of curiosity - what are the potential problems with memory buffers

that

you're referring to?

-Val

On Fri, May 14, 2021 at 5:06 AM Ilya Korol  wrote:


Hi, everyone.

There is a proposal to remove suggestion that user should disable
explicit GC calls in https://issues.apache.org/jira/browse/IGNITE-14720

.

Nowadays people usually don't use this facility directly without huge
need (at least we hope so), so this suggestion doesn't bring much
profit, but instead could lead to potential problems with reclaiming
memory used by direct memory buffers.

I'm going to fix this.

Is there any objections (suggestions)?

Re: [jira] [Created] (IGNITE-12921) System view design leads to bad user expirience.

[18624049226]

Hello Nikolay,

Due to the design change of the ticket, the METRICS view has been 
enabled by default in the 2.10. Then the following document description 
will mislead the user in cognition. If you configure according to the 
document description, you will also throw an error. Please confirm?


https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system

在 2020/4/21 上午12:10, Andrey N. Gura (Jira) 写道:

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

  Summary: System view design leads to bad user expirience.
  Key: IGNITE-12921
  URL: https://issues.apache.org/jira/browse/IGNITE-12921
  Project: Ignite
   Issue Type: Bug
 Affects Versions: 2.8
 Reporter: Andrey N. Gura
  Fix For: 2.8.1


Current implementation of system views has broken system behavior which is 
related with querying system views.

Before 2.8 system views were available via SQL queries (if indexing is 
enabled). It did not depend on any configuration.

After implementation of IGNITE-12145 system views available only if 
{{SqlViewExporterSpi}} is passed to 
{{IgniteConfiguration.setSystemViewExporterSpi()}}. Now, if an user configures 
some {{SystemViewExporterSpi}} then provided user configuration will rewrite 
default configuration and {{SqlViewExporterSpi}} won't be initialized. As 
result it is impossible to query system views and any query to the views fails 
with exception. This behavior is not obvious for the user. See tests below.

The second problem is kind of design problem. System view is internal part of 
the system and should be available regardless of any exporter configuration (at 
least via SQL) such as it was implemented before 2.8 release.

My suggestion is the following: we should remove {{SqlViewExporterSpi}} and 
configure all views on indexing module initialization. {{SqlViewExporterSPI}} 
also doesn't make sense because:
- it operates by some internal API ({{SchemaManager}}, {{GridKernalContext}}, 
{{IgniteH2Indexing}}).
- it doesn't allow to end user to add any new system view.

Only thing that could be useful is a filtering. But it could be done with SQL.

Reproducer of broken behavior:

{code:java}
package org.apache.ignite.internal.processors.cache.metric;

import org.apache.ignite.cache.query.SqlFieldsQuery;
import org.apache.ignite.cluster.ClusterState;
import org.apache.ignite.configuration.DataRegionConfiguration;
import org.apache.ignite.configuration.DataStorageConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.spi.systemview.jmx.JmxSystemViewExporterSpi;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.junit.Test;

import java.util.HashSet;
import java.util.List;
import java.util.Set;

import static java.util.Arrays.asList;
import static 
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest.queryProcessor;

public class SystemViewTest extends GridCommonAbstractTest {

 private static boolean useDefaultSpi;

 /** {@inheritDoc} */
 @Override protected IgniteConfiguration getConfiguration(String 
igniteInstanceName) throws Exception {
 IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);

 cfg.setConsistentId(igniteInstanceName);

 cfg.setDataStorageConfiguration(new DataStorageConfiguration()
 .setDataRegionConfigurations(
 new 
DataRegionConfiguration().setName("in-memory").setMaxSize(100L * 1024 * 1024))
 .setDefaultDataRegionConfiguration(
 new DataRegionConfiguration()
 .setPersistenceEnabled(true)));

 if (!useDefaultSpi) {
 // Configure user provided system view exporter SPI.
 cfg.setSystemViewExporterSpi(new JmxSystemViewExporterSpi());
 }

 return cfg;
 }

 /**
  * Will executed succefully.
  */
 @Test
 public void testSystemViewWithDefaultSpi() throws Exception {
 useDefaultSpi = true;

 doTestSystemView();
 }

 /**
  * Will fail with Table "VIEWS" not found.
  */
 @Test
 public void testSystemViewWithCustomSpi() throws Exception {
 useDefaultSpi = false;

 doTestSystemView();
 }

 private void doTestSystemView() throws Exception {
 try (IgniteEx ignite = startGrid()) {
 ignite.cluster().state(ClusterState.ACTIVE);

 Set cacheNames = new HashSet<>(asList("cache-1", 
"cache-2"));

 for (String name : cacheNames)
 ignite.getOrCreateCache(name);

 SqlFieldsQuery qry = new SqlFieldsQuery("SELECT * FROM SYS.VIEWS");

 List> res = queryProcessor(ignite).querySqlFields(qry, 
true).getAll();

 res.forEach(item -> log.info("VIEW FOUND

Re: 2.9.1 release proposal

[18624049226]

Hello,

I suggest that the remaining document issue in version 2.9.0 can be 
solved in version 2.9.1, and it is not a good practice to postpone to 
version 2.10.


在 2020/10/27 上午2:00, Maxim Muzafarov 写道:

Hello,

+1
Should we start the discussion about the release leader and release dates?

On Tue, 20 Oct 2020 at 10:12, Anton Vinogradov  wrote:

+1 to start the 2.9.1 release process once as soon as 2.9 released.

On Mon, Oct 19, 2020 at 8:49 PM Nikolay Izhikov  wrote:


Hello, Yaroslav.

I support the idea.
But, we should carefully work with the release scope.

IGNITE-13477 - fix for a SQL tracing that will be available only in 2.10
IGNITE-13427 - fix for a new system view that exists in master only, we
need to include IGNITE-13409

Other tickets should be checked, also.
Is this a real fix of a released bug or we fix some issue we bring with
the brand new contribution.


I propose to include the following tickets, also:

CMD tools improvements:

IGNITE-13488 - Command to print metric value
IGNITE-13426 - Command to print system view content
IGNITE-13422 - Parameter to explicitly enable experimental commands

IGNITE-13380 - Output IgniteSystemProperties via ignite.sh

New system views:

IGNITE-13409 Metastorage and DistributedMetastorage viewы.
IGNITE-13408 BinaryMetadata view.



19 окт. 2020 г., в 18:20, Yaroslav Molochkov 

написал(а):

Hello, Igniters!

I've compiled a list of tickets that, i think, deserve to be released in

a

minor Ignite release (meaning in 2.9.1) after 2.9. Here they are:

IGNITE-13569
disable archiving + walCompactionEnabled probably broke reading from wal

on

server restart

IGNITE-13418
Deadlock on multiple cache delete

IGNITE-13563
Deserializing IBinaryObject containing an IBinaryObject field fails

IGNITE-13575
Invalid blocking section in GridNioWorker and GridNioClientWorker leads

to

false positive blocking thread detection

IGNITE-13458
RebalancingPartitionsTotal metrics

IGNITE-13536
.NET: Child processes become zombies when persistence is used with
direct-io on Linux

IGNITE-13500
Checkpoint read lock fail if it is taking under write lock during the
stopping node

IGNITE-13431
NPE during Cassandra Store initialization with PRIMITIVE strategy

IGNITE-13417
Cache Interceptors deserialization on client nodes

IGNITE-13495
ZookeeperDiscoverySpiMBeanImpl#getCoordinator can return invalid node as
coordinator

IGNITE-13479
Both ignite.sh and control.sh use the same JVM_OPTS. Control.sh doesn't
start if JMX port was set

IGNITE-11312
JDBC: Thin driver reports incorrect property names

IGNITE-13462
.NET: Thin client Dispose hangs when continuous query is active on .NET
Core 3.x

IGNITE-13484
C++ odbc-example losing some values if run with 1 additional node

IGNITE-13477
Fix NPE in SQL tracing implementation.

IGNITE-13435
Fixing some unrecorded issues command warm-up control.sh

IGNITE-13403
Update JDBC metadata to match actual capabilities

IGNITE-13427
The local metastorage system view fails if unmarshallable values present

IGNITE-13401
Unsupported protocol version exception when getting cache configuration
from Java thin client

IGNITE-13388
apache-ignite deb package depends on a non-existent package and can't be
installed on Debian 10

IGNITE-13397
NPE in logSupplierDone(UUID nodeId)

IGNITE-13296
.NET: TransactionImpl finalizer can crash the process

IGNITE-13382
DurableBackgroundTask can abandon incomplete task

IGNITE-12509
CACHE_REBALANCE_STOPPED event raises for wrong caches in case of

specified

RebalanceDelay

IGNITE-13072
Synchronization problems when different classloaders are used for
deployment of same class

IGNITE-13379
Exception occur on SQL caches when client reconnect

IGNITE-13363
GridDhtCacheEntry::toString locks

IGNITE-13373
WAL segmentns do not released on releaseHistoryForPreloading()

IGNITE-13540
Exchange worker, waiting for new task from queue, considered as blocked.

IGNITE-13491
Fix incorrect topology snapshot logger output about coordinator change.

IGNITE-13439
Printing detailed classpath slowdowns node initialization

WDYT?

Re: New Ignite Docs: Status and Incomplete Items

[18624049226]

I know that if the content of codeblock(tabs) is a code snippet, it has 
a background color. If it's a markdown text, it's not.
In other words, the background color is the background color of the code 
snippet, not the background color of codeblock.


在 2020/10/6 上午7:31, Denis Magda 写道:

Hey, thanks for keep checking the content and behavior of the new docs.
This helps a lot!

https://ignite.apache.org/docs/latest/installation/deb-rpm

This document should be incomplete. At present, there are only
descriptions related to DEB package, which is much less than the
original one.


Hmm, good remark. @Peter Ivanov , for some reason,
Artem didn't port the RPM instructions.

Compare the readme.io original doc:
https://apacheignite.readme.io/docs/rpm-and-deb-setup
with the new version:
https://ignite.apache.org/docs/latest/installation/deb-rpm

Is this an oversight or do we have any RPM related issue?


1.The right most scroll bar should only affect the body part of the

document, but now scrolling the right scroll bar, the left menu and the
right TOC are affected, so the user experience is not good;
3.Most of the time, the menu on the left side cannot be linked with the
document body normally. When a document is displayed, the menu item on
the left side should be expanded and selected. But now the logic seems
confused, especially when the current page is jumping from external links.


Yeap, the left-side menu issue was known and we keep fixing it. As for the
right-side menu issues, that's new. Both issues will be fixed:
https://issues.apache.org/jira/browse/IGNITE-13522

2.CodeBlock(tabs) components should have a background color or border

line (see the original readme.io),Otherwise, it is easy to be confused
with the document body.


Could you point out to any example? We do use a special background and
syntax highlighter for code snippets. For instance, check a configuration
snippet from this K8 installation section:
https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment#creating-service

https://ignite.apache.org/docs/latest/setup-dotnet

this page is 404


Good catch. I removed that page and, instead, added a special callout to
the top of this page. The callout brings attention to .NET, Python, etc.
installation instructions:
https://ignite.apache.org/docs/latest/understanding-configuration

In addition, with regard to Kubernetes, in fact, the services provided

by various cloud service providers are generally similar. From the
perspective of documents, most of the contents are repetitive. In
addition, many users may still deploy Kubernetes in a private environment.
So recombine these long documents into one general document, and then
according to the differences of different service providers, there is
another document to make it look clearer and save a lot of space.


Makes sense to me. Create a ticket for that. Hope those other contributors
will pick it up. Don't have time to work on it personally:
https://issues.apache.org/jira/browse/IGNITE-13528

Btw, should we create any instructions for Alibaba, Huawei or other clouds?
Do you have anything like that on the Chinese version of the doc?



-
Denis


On Sat, Oct 3, 2020 at 11:03 PM 18624049226 <18624049...@163.com> wrote:


Hi Denis,

There are several suggestions for improvement:

1.The right most scroll bar should only affect the body part of the
document, but now scrolling the right scroll bar, the left menu and the
right TOC are affected, so the user experience is not good;

2.CodeBlock(tabs) components should have a background color or border
line (see the original readme.io),Otherwise, it is easy to be confused
with the document body.

3.Most of the time, the menu on the left side cannot be linked with the
document body normally. When a document is displayed, the menu item on
the left side should be expanded and selected. But now the logic seems
confused, especially when the current page is jumping from external links.

在 2020/10/3 上午11:43, Denis Magda 写道:

Hi,

Thanks for finding the time and walking through the documentation pages.

We

didn't intend to copy the docs as is. There are a lot of structural

changes

as well as complete rewrites of pages.
Also, some of the old pages were skipped deliberately, if they were about
legacy or rarely used APIs.

Please see inline for extra thoughts. Btw, try out the search toolbox

that

can point out to a new location of certain docs.

-
Denis


On Fri, Oct 2, 2020 at 8:05 PM 18624049226 <18624049...@163.com> wrote:


Hi Denis,

I have roughly compared the new document with the original document. The
corresponding page in the list below shows that the new version of the
document is missing or incomplete, please confirm it again.
I didn't check every paragraph of the new document, so this is just a

hint.

https://ignite.apache.org/docs/latest/installation/deb-rpm

https://ignite.apache.org/docs/latest/installation/deb-rpm



https

Re: New Ignite Docs: Status and Incomplete Items

[18624049226]

Hi Denis,

There are several suggestions for improvement:

1.The right most scroll bar should only affect the body part of the 
document, but now scrolling the right scroll bar, the left menu and the 
right TOC are affected, so the user experience is not good;


2.CodeBlock(tabs) components should have a background color or border 
line (see the original readme.io),Otherwise, it is easy to be confused 
with the document body.


3.Most of the time, the menu on the left side cannot be linked with the 
document body normally. When a document is displayed, the menu item on 
the left side should be expanded and selected. But now the logic seems 
confused, especially when the current page is jumping from external links.


在 2020/10/3 上午11:43, Denis Magda 写道:

Hi,

Thanks for finding the time and walking through the documentation pages. We
didn't intend to copy the docs as is. There are a lot of structural changes
as well as complete rewrites of pages.
Also, some of the old pages were skipped deliberately, if they were about
legacy or rarely used APIs.

Please see inline for extra thoughts. Btw, try out the search toolbox that
can point out to a new location of certain docs.

-
Denis


On Fri, Oct 2, 2020 at 8:05 PM 18624049226 <18624049...@163.com> wrote:


Hi Denis,

I have roughly compared the new document with the original document. The
corresponding page in the list below shows that the new version of the
document is missing or incomplete, please confirm it again.
I didn't check every paragraph of the new document, so this is just a hint.

https://ignite.apache.org/docs/latest/installation/deb-rpm

https://ignite.apache.org/docs/latest/installation/deb-rpm




https://apacheignite.readme.io/docs/mesos-deployment
https://apacheignite.readme.io/docs/yarn-deployment


Those are legacy installation options. We agreed not to bring them to the
new docs.


https://apacheignite.readme.io/docs/generic-configuration


That generic K8 configuration was referenced from cloud-specific pages.
Now, the whole installation process is adopted for every cloud environment
so that the reader doesn't
need to jump back and forth between the generic and cloud-specific K8 pages.



https://apacheignite.readme.io/docs/memory-defragmentation


https://ignite.apache.org/docs/latest/memory-architecture#memory-defragmentation



https://apacheignite.readme.io/docs/distributed-locks
https://apacheignite.readme.io/docs/messaging


These two were missed, I'll add them to the new docs.



https://apacheignite.readme.io/docs/perfomance-benchmarking


Same, I'll add it.



https://apacheignite-mix.readme.io/docs/amazon-aws


https://ignite.apache.org/docs/latest/clustering/discovery-in-the-cloud



https://apacheignite-mix.readme.io/docs/web-session-clustering


The page is outdated. There are many blog posts and articles on the topic
on the Internet. We deliberately skipped it.



https://apacheignite-mix.readme.io/docs/installation-in-apache-karaf


The module is not maintained and there are no signs that anybody uses it.
No plans to port.



https://apacheignite.readme.io/docs/ignite-life-cycle


https://ignite.apache.org/docs/latest/starting-nodes#node-lifecycle-events



https://apacheignite.readme.io/docs/thread-pools


https://ignite.apache.org/docs/latest/perf-and-troubleshooting/thread-pools-tuning



https://apacheignite.readme.io/docs/async-support


This page seems redundant. It should be enough to open JavaDocs and see
sync and async versions of the APIs.

--
Denis



在 2020/10/3 上午4:44, Denis Magda 写道:

Thanks Pavel! Merged.

Alright, guys, we've finished with the porting of all useful pages to the
new docs engine as well as documented all the primate Ignite 2.9
enhancements.

On Monday (Oct 5ht), I'll do some final tweaks and start integrating the
feature branch into the master.* Refrain from doing any documentation
changes or sending pull-requests until further notice.*

-
Denis


On Fri, Oct 2, 2020 at 7:50 AM Pavel Tupitsyn 

wrote:

Denis, IGNITE-13331 is ready for your review
https://issues.apache.org/jira/browse/IGNITE-13331

On Thu, Oct 1, 2020 at 9:42 AM Pavel Tupitsyn 
wrote:


Denis,

Thanks a lot for porting those changes, great job!
I'm working on IGNITE-13331, sorry for the delay.

On Wed, Sep 30, 2020 at 2:15 AM Denis Magda  wrote:


You might need to empty the browser cache to see the latest changes

such

as
the "C# and .NET Specific" section that was published today. There is

some

CSS issue that doesn't invalidate browsing caches. It will be fixed

soon.

-
Denis


On Tue, Sep 29, 2020 at 4:12 PM Denis Magda 

wrote:

Pavel,

I ported all the .NET-specific pages from readme.io with minor

changes.

The docs are under the "C# and .NET Specific" section down the

navigation

tree:
https://ignite.apache.org/docs/latest

The thin-client related docs are under the "Thin Clients" sections.

It

all

makes things look a bit clumsy for 

Re: New Ignite Docs: Status and Incomplete Items

[18624049226]

https://ignite.apache.org/docs/latest/setup-dotnet

this page is 404

在 2020/10/3 上午11:43, Denis Magda 写道:

Hi,

Thanks for finding the time and walking through the documentation pages. We
didn't intend to copy the docs as is. There are a lot of structural changes
as well as complete rewrites of pages.
Also, some of the old pages were skipped deliberately, if they were about
legacy or rarely used APIs.

Please see inline for extra thoughts. Btw, try out the search toolbox that
can point out to a new location of certain docs.

-
Denis


On Fri, Oct 2, 2020 at 8:05 PM 18624049226 <18624049...@163.com> wrote:


Hi Denis,

I have roughly compared the new document with the original document. The
corresponding page in the list below shows that the new version of the
document is missing or incomplete, please confirm it again.
I didn't check every paragraph of the new document, so this is just a hint.

https://ignite.apache.org/docs/latest/installation/deb-rpm

https://ignite.apache.org/docs/latest/installation/deb-rpm




https://apacheignite.readme.io/docs/mesos-deployment
https://apacheignite.readme.io/docs/yarn-deployment


Those are legacy installation options. We agreed not to bring them to the
new docs.


https://apacheignite.readme.io/docs/generic-configuration


That generic K8 configuration was referenced from cloud-specific pages.
Now, the whole installation process is adopted for every cloud environment
so that the reader doesn't
need to jump back and forth between the generic and cloud-specific K8 pages.



https://apacheignite.readme.io/docs/memory-defragmentation


https://ignite.apache.org/docs/latest/memory-architecture#memory-defragmentation



https://apacheignite.readme.io/docs/distributed-locks
https://apacheignite.readme.io/docs/messaging


These two were missed, I'll add them to the new docs.



https://apacheignite.readme.io/docs/perfomance-benchmarking


Same, I'll add it.



https://apacheignite-mix.readme.io/docs/amazon-aws


https://ignite.apache.org/docs/latest/clustering/discovery-in-the-cloud



https://apacheignite-mix.readme.io/docs/web-session-clustering


The page is outdated. There are many blog posts and articles on the topic
on the Internet. We deliberately skipped it.



https://apacheignite-mix.readme.io/docs/installation-in-apache-karaf


The module is not maintained and there are no signs that anybody uses it.
No plans to port.



https://apacheignite.readme.io/docs/ignite-life-cycle


https://ignite.apache.org/docs/latest/starting-nodes#node-lifecycle-events



https://apacheignite.readme.io/docs/thread-pools


https://ignite.apache.org/docs/latest/perf-and-troubleshooting/thread-pools-tuning



https://apacheignite.readme.io/docs/async-support


This page seems redundant. It should be enough to open JavaDocs and see
sync and async versions of the APIs.

--
Denis



在 2020/10/3 上午4:44, Denis Magda 写道:

Thanks Pavel! Merged.

Alright, guys, we've finished with the porting of all useful pages to the
new docs engine as well as documented all the primate Ignite 2.9
enhancements.

On Monday (Oct 5ht), I'll do some final tweaks and start integrating the
feature branch into the master.* Refrain from doing any documentation
changes or sending pull-requests until further notice.*

-
Denis


On Fri, Oct 2, 2020 at 7:50 AM Pavel Tupitsyn 

wrote:

Denis, IGNITE-13331 is ready for your review
https://issues.apache.org/jira/browse/IGNITE-13331

On Thu, Oct 1, 2020 at 9:42 AM Pavel Tupitsyn 
wrote:


Denis,

Thanks a lot for porting those changes, great job!
I'm working on IGNITE-13331, sorry for the delay.

On Wed, Sep 30, 2020 at 2:15 AM Denis Magda  wrote:


You might need to empty the browser cache to see the latest changes

such

as
the "C# and .NET Specific" section that was published today. There is

some

CSS issue that doesn't invalidate browsing caches. It will be fixed

soon.

-
Denis


On Tue, Sep 29, 2020 at 4:12 PM Denis Magda 

wrote:

Pavel,

I ported all the .NET-specific pages from readme.io with minor

changes.

The docs are under the "C# and .NET Specific" section down the

navigation

tree:
https://ignite.apache.org/docs/latest

The thin-client related docs are under the "Thin Clients" sections.

It

all

makes things look a bit clumsy for now (that some .NET docs are under

the

".NET specific" section while some under "Thin Clients) but I'll let
technical-writing contributors review and restructure everything

later.

As for the IGNITE-13331, put the changes under the "Thin Clients".


-
Denis


On Fri, Sep 25, 2020 at 12:49 PM Denis Magda 

wrote:

Pavel,

Alright, I'll do the porting of those pages and you'll take care of
IGNITE-13331 <https://issues.apache.org/jira/browse/IGNITE-13331>.

Let's

split the job.

Nikolay, I'll review your contribution early next week.

Thanks, folks, for the cooperation.

-
Denis


On Thu

Re: New Ignite Docs: Status and Incomplete Items

[18624049226]

Hi Denis,

Thank you very much for the detailed explanation.

https://ignite.apache.org/docs/latest/installation/deb-rpm

This document should be incomplete. At present, there are only 
descriptions related to DEB package, which is much less than the 
original one.


In addition, with regard to Kubernetes, in fact, the services provided 
by various cloud service providers are generally similar. From the 
perspective of documents, most of the contents are repetitive. In 
addition, many users may still deploy Kubernetes in a private environment.
So recombine these long documents into one general document, and then 
according to the differences of different service providers, there is 
another document to make it look clearer and save a lot of space.


在 2020/10/3 上午11:43, Denis Magda 写道:

Hi,

Thanks for finding the time and walking through the documentation pages. We
didn't intend to copy the docs as is. There are a lot of structural changes
as well as complete rewrites of pages.
Also, some of the old pages were skipped deliberately, if they were about
legacy or rarely used APIs.

Please see inline for extra thoughts. Btw, try out the search toolbox that
can point out to a new location of certain docs.

-
Denis


On Fri, Oct 2, 2020 at 8:05 PM 18624049226 <18624049...@163.com> wrote:


Hi Denis,

I have roughly compared the new document with the original document. The
corresponding page in the list below shows that the new version of the
document is missing or incomplete, please confirm it again.
I didn't check every paragraph of the new document, so this is just a hint.

https://ignite.apache.org/docs/latest/installation/deb-rpm

https://ignite.apache.org/docs/latest/installation/deb-rpm




https://apacheignite.readme.io/docs/mesos-deployment
https://apacheignite.readme.io/docs/yarn-deployment


Those are legacy installation options. We agreed not to bring them to the
new docs.


https://apacheignite.readme.io/docs/generic-configuration


That generic K8 configuration was referenced from cloud-specific pages.
Now, the whole installation process is adopted for every cloud environment
so that the reader doesn't
need to jump back and forth between the generic and cloud-specific K8 pages.



https://apacheignite.readme.io/docs/memory-defragmentation


https://ignite.apache.org/docs/latest/memory-architecture#memory-defragmentation



https://apacheignite.readme.io/docs/distributed-locks
https://apacheignite.readme.io/docs/messaging


These two were missed, I'll add them to the new docs.



https://apacheignite.readme.io/docs/perfomance-benchmarking


Same, I'll add it.



https://apacheignite-mix.readme.io/docs/amazon-aws


https://ignite.apache.org/docs/latest/clustering/discovery-in-the-cloud



https://apacheignite-mix.readme.io/docs/web-session-clustering


The page is outdated. There are many blog posts and articles on the topic
on the Internet. We deliberately skipped it.



https://apacheignite-mix.readme.io/docs/installation-in-apache-karaf


The module is not maintained and there are no signs that anybody uses it.
No plans to port.



https://apacheignite.readme.io/docs/ignite-life-cycle


https://ignite.apache.org/docs/latest/starting-nodes#node-lifecycle-events



https://apacheignite.readme.io/docs/thread-pools


https://ignite.apache.org/docs/latest/perf-and-troubleshooting/thread-pools-tuning



https://apacheignite.readme.io/docs/async-support


This page seems redundant. It should be enough to open JavaDocs and see
sync and async versions of the APIs.

--
Denis



在 2020/10/3 上午4:44, Denis Magda 写道:

Thanks Pavel! Merged.

Alright, guys, we've finished with the porting of all useful pages to the
new docs engine as well as documented all the primate Ignite 2.9
enhancements.

On Monday (Oct 5ht), I'll do some final tweaks and start integrating the
feature branch into the master.* Refrain from doing any documentation
changes or sending pull-requests until further notice.*

-
Denis


On Fri, Oct 2, 2020 at 7:50 AM Pavel Tupitsyn 

wrote:

Denis, IGNITE-13331 is ready for your review
https://issues.apache.org/jira/browse/IGNITE-13331

On Thu, Oct 1, 2020 at 9:42 AM Pavel Tupitsyn 
wrote:


Denis,

Thanks a lot for porting those changes, great job!
I'm working on IGNITE-13331, sorry for the delay.

On Wed, Sep 30, 2020 at 2:15 AM Denis Magda  wrote:


You might need to empty the browser cache to see the latest changes

such

as
the "C# and .NET Specific" section that was published today. There is

some

CSS issue that doesn't invalidate browsing caches. It will be fixed

soon.

-
Denis


On Tue, Sep 29, 2020 at 4:12 PM Denis Magda 

wrote:

Pavel,

I ported all the .NET-specific pages from readme.io with minor

changes.

The docs are under the "C# and .NET Specific" section down the

navigation

tree:
https://ignite.apache.org/docs/latest

The thin-client related docs are under the "Thin Clients" sections.

It

all

Re: New Ignite Docs: Status and Incomplete Items

[18624049226]

Hi Denis,

I have roughly compared the new document with the original document. The 
corresponding page in the list below shows that the new version of the 
document is missing or incomplete, please confirm it again.

I didn't check every paragraph of the new document, so this is just a hint.

https://ignite.apache.org/docs/latest/installation/deb-rpm

https://apacheignite.readme.io/docs/mesos-deployment
https://apacheignite.readme.io/docs/yarn-deployment
https://apacheignite.readme.io/docs/generic-configuration
https://apacheignite.readme.io/docs/memory-defragmentation
https://apacheignite.readme.io/docs/distributed-locks
https://apacheignite.readme.io/docs/messaging
https://apacheignite.readme.io/docs/perfomance-benchmarking
https://apacheignite-mix.readme.io/docs/amazon-aws
https://apacheignite-mix.readme.io/docs/web-session-clustering
https://apacheignite-mix.readme.io/docs/installation-in-apache-karaf
https://apacheignite.readme.io/docs/ignite-life-cycle
https://apacheignite.readme.io/docs/thread-pools
https://apacheignite.readme.io/docs/async-support

在 2020/10/3 上午4:44, Denis Magda 写道:

Thanks Pavel! Merged.

Alright, guys, we've finished with the porting of all useful pages to the
new docs engine as well as documented all the primate Ignite 2.9
enhancements.

On Monday (Oct 5ht), I'll do some final tweaks and start integrating the
feature branch into the master.* Refrain from doing any documentation
changes or sending pull-requests until further notice.*

-
Denis


On Fri, Oct 2, 2020 at 7:50 AM Pavel Tupitsyn  wrote:


Denis, IGNITE-13331 is ready for your review
https://issues.apache.org/jira/browse/IGNITE-13331

On Thu, Oct 1, 2020 at 9:42 AM Pavel Tupitsyn 
wrote:


Denis,

Thanks a lot for porting those changes, great job!
I'm working on IGNITE-13331, sorry for the delay.

On Wed, Sep 30, 2020 at 2:15 AM Denis Magda  wrote:


You might need to empty the browser cache to see the latest changes such
as
the "C# and .NET Specific" section that was published today. There is

some

CSS issue that doesn't invalidate browsing caches. It will be fixed

soon.

-
Denis


On Tue, Sep 29, 2020 at 4:12 PM Denis Magda  wrote:


Pavel,

I ported all the .NET-specific pages from readme.io with minor

changes.

The docs are under the "C# and .NET Specific" section down the

navigation

tree:
https://ignite.apache.org/docs/latest

The thin-client related docs are under the "Thin Clients" sections. It

all

makes things look a bit clumsy for now (that some .NET docs are under

the

".NET specific" section while some under "Thin Clients) but I'll let
technical-writing contributors review and restructure everything

later.

As for the IGNITE-13331, put the changes under the "Thin Clients".


-
Denis


On Fri, Sep 25, 2020 at 12:49 PM Denis Magda 

wrote:

Pavel,

Alright, I'll do the porting of those pages and you'll take care of
IGNITE-13331 .

Let's

split the job.

Nikolay, I'll review your contribution early next week.

Thanks, folks, for the cooperation.

-
Denis


On Thu, Sep 24, 2020 at 11:19 PM Pavel Tupitsyn <

ptupit...@apache.org>

wrote:


Do you want me to port those pages or are you going to do it

yourself?

I'm ok either way, any help with this will be greatly appreciated :)


Are you saying the .NET community no longer uses those?

Existing integrations are for legacy technologies.
We are going to remove them in 3.0 [1] and, hopefully, replace them

with

modern equivalents later.

[1]



https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist

On Fri, Sep 25, 2020 at 2:20 AM Denis Magda 

wrote:

Pavel, thanks for preparing the list of the missing pages. Do you

want

me

to port those pages or are you going to do it yourself?

Btw, what's wrong with the 3rd-party integrations? Are you saying

the

.NET

community no longer uses those?

-
Denis


On Fri, Sep 18, 2020 at 5:45 AM Pavel Tupitsyn <

ptupit...@apache.org>

wrote:


Denis,


@Pavel Tupitsyn  ... Are you going to

document

the

features added in 2.9  <

https://issues.apache.org/jira/browse/IGNITE-13331

Yes, I have this on my plate, but the release was postponed so I

postponed

the task as well.



is there is anything else you planned to move from readme.io?

A list of missing things:
- Standalone nodes [1]
- Java detection, known issues [2]
- XML configuration [3]
- Serialization details [4]
- Platform interop [5]
- Deployment [6]
- Troubleshooting [7]
- Assembly loading [8]
- LINQ [9]
- Calling Java services [10]
- Plugins [11]
- Logging [12]

Also "Third-party integrations", but I consider them legacy, so

we

can

skip that.

[1] https://apacheignite-net.readme.io/docs/standalone-nodes
[2]

https://apacheignite-net.readme.io/docs/cross-platform-support

[3] https://apacheignite-net.readme.io/docs/configuration
[4] https://apacheignite-net.readme.io/docs/serialization
[5]

https://apacheignite-net.readme.io/docs/platform-interoperability

[6] https://apache

Re: Apache Ignite 3.0

[18624049226]

Hi Val,

AFAIK, many developers use Ignite as a powerful development framework 
for distributed applications.
The messaging function is easy to use. With it, many systems do not need 
to introduce a special message system such as Kafka. Although this 
function does not seem to coordinate with ignite's positioning, but it 
does make the overall system architecture simple.


在 2020/9/17 下午1:21, Valentin Kulichenko 写道:

Raymond,

Can you please describe the way you use messaging in a little bit more
detail? Is it for communication between server nodes or more of a
client-server? what are the typical patterns?

-Val

On Wed, Sep 16, 2020 at 4:05 PM Raymond Wilson 
wrote:


Hi Val,

Possibly, but the core difficulty there is knowing when the fan-out to
listeners has been completed. Before you know it you have
re-implemented Kafka! :)

I think we can leverage our use case knowledge to convert the messaging
style of notifications to a compute style broadcast against a compute
projection using an attribute based selection for nodes that want to be
listeners for the events. The messaging rate is relatively low (a few
messages a second) so this should be pretty workable.

Raymond.

On Thu, Sep 17, 2020 at 3:27 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:


Hi Raymond,

Do you think you could use services for your use case?
https://apacheignite.readme.io/docs/service-grid

-Val

On Tue, Sep 15, 2020 at 4:32 PM Raymond Wilson <

raymond_wil...@trimble.com

wrote:


For what it is worth, we use messaging in Ignite to provide grid
notifications for various purposes. These might stimulate compute
operations in the message recipients, but they don't represent compute.

If messaging is removed, how would Ignite provide the ability for a

node

to

listen to events without the event sender being explicitly aware that

the

listener does, or should, exist, to produce a compute projection to

send

messages-as-compute-requests to?

On Wed, Sep 16, 2020 at 9:28 AM Kseniya Romanova <
romanova.ks@gmail.com>
wrote:


Just wanted to submit a link to the video about some offered changes.
@valentin.kuliche...@gmail.com 

please

add

it to the wiki page. I created timestamps in the description, so one

can

browse the presentation fast or link the particular section:
https://youtu.be/zPuLJgUfLaM
Thanks a lot for the presentation!

вт, 18 авг. 2020 г. в 14:13, Ilya Kasnacheev <

ilya.kasnach...@gmail.com

:


Hello!

Maybe we can implement messaging via compute? Share underlying code

but

have a different API for convenience (maybe in extras).

Regards,
--
Ilya Kasnacheev


вт, 18 авг. 2020 г. в 11:59, Pavel Tupitsyn 
:

Val,


Is see the ".NET Modernization for Ignite 3.0" item in the

roadmap,

but

it

doesn't provide much detail. What are the actual changes in

.NET

that

you

propose for 3.0?

I've updated the roadmap with a brief description.
We want to move away from an old, long unsupported .NET version,
and remove integrations with legacy technologies (old ASP.NET

and

EF).

As for the messaging, so far I haven't seen use cases that

would

require

this API. Sometimes users attempt to use it for remote code

invocation,

but

compute is usually a better option for this. Do you have any

examples

where

messaging is a better fit then compute?

I guess you are right, Compute can replace Messaging in most

scenarios.

Messaging can be more convenient, since it is pub-sub -

subscriber

controls

whether it receives messages on the given topic. But this can be

achieved

with a little more work with Compute as well.

Thanks,
Pavel



On Tue, Aug 18, 2020 at 3:16 AM Saikat Maitra <

saikat.mai...@gmail.com

wrote:


Hi Pavel,

Awesome, thank you.

Yes, I remember having .Net modernization as part of Apache

Ignite

3.0

roadmap.

Regards,
Saikat

On Sun, Aug 16, 2020 at 11:04 AM Pavel Tupitsyn <

ptupit...@apache.org>

wrote:


Saikat, yes, most definitely.
This is mentioned in the wishlist under ".NET: Target .NET

Standard

2.0,

discontinue .NET 4.0 support".
I'm already working towards this goal by making more code and

tests

work

properly under .NET Core,
so when the time for breaking changes comes, it will be

simpler.

On Sat, Aug 15, 2020 at 10:06 PM Saikat Maitra <

saikat.mai...@gmail.com>

wrote:


Hi Val,

Thank you for adding the Cleanup section and Removals list.

Pavel, As part of Apache Ignite Roadmap we had mentioned we

will

add

modernization of .NET. Are we still targeting it in Apache

Ignite

3.0

release?



https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap

Regards,
Saikat



On Fri, Aug 14, 2020 at 10:04 AM Carbone, Adam <
adam.carb...@bottomline.com>
wrote:


If you want to make is simpler to have the components

that

you

want,

but

have that be immutable at install time you could take an

approach

similar

to the way spring does it with their initializer (
https://start.spring.io/ )  as an example... Basically

the

concept

being

something that

Re: Ignite 3.0 meetups

[18624049226]

It seems that the new Calcite based SQL Engine is not included in the 
plan, and this proposal is abandoned?


在 2020/9/16 上午5:24, Kseniya Romanova 写道:

Hi, igniters!
Thanks to all who attended today's event, that was a really warm community
gathering even though we met online! And thanks to Val for his
presentation. I hope these materials will help to run the discussion about
Ignite 3.0[1]
Video: https://youtu.be/zPuLJgUfLaM
Slides with all links: https://bit.ly/32vDR42

I remind, that the Russian speaking community is gathering on September 17:
https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/272675398/

[1]
https://lists.apache.org/thread.html/reea1639499689d6a0cb2f11d7699cdbfd7102e540aeffdd4d361858c%40%3Cdev.ignite.apache.org%3E


пн, 14 сент. 2020 г. в 13:55, Kseniya Romanova :


Hi! Just a reminder that we will meet this week.
Hope to see you there.

ср, 26 авг. 2020 г. в 01:26, Saikat Maitra :


Hi Val,

Thank you for scheduling the meetups. Will join and connect on Ignite 3.0
release planning.

Regards,
Saikat

On Tue, Aug 25, 2020 at 4:49 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:


Igniters,

As was discussed before, we've scheduled two meetups devoted to Ignite
3.0:

- Sep 15 (in English):
https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/272675408/
- Sep 17 (in Russian):
https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/272675398/

I will present the proposed changes and the preliminary roadmap for
Ignite 3.0. Everyone is welcome to join and participate in the discussion!

-Val

Re: [jira] [Created] (IGNITE-13219) Slf4jLogger does not implement the LoggerNodeIdAware interface.

[18624049226]

Hi community,

I have created a PR for this issue. This is a small problem with minor 
changes., is anyone willing to merge this PR into the master?


在 2020/7/6 下午4:10, YuJue Li (Jira) 写道:

YuJue Li created IGNITE-13219:
-

  Summary: Slf4jLogger does not implement the LoggerNodeIdAware 
interface.
  Key: IGNITE-13219
  URL: https://issues.apache.org/jira/browse/IGNITE-13219
  Project: Ignite
   Issue Type: Improvement
   Components: general
 Affects Versions: 2.8.1
 Reporter: YuJue Li
 Assignee: YuJue Li
  Fix For: 2.9


In the scenario of ignite + slf4j + log4j2, the generated log file is named 
ignite-${sys:nodeId}.log, The reason for this problem is that Slf4jLogger does 
not implement the
LoggerNodeIdAware interface.



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

Re: Website link update

[18624049226]

Hi community,

The current site of the Chinese version of the document is 
https://liyuj.gitee.io , this site will stop maintenance in the future.


The new site is located at https://www.ignite-service.cn/doc/java, is 
there anyone in the community can help with the change in 
https://ignite.apache.org/docs-and-apis.html?


在 2019/3/4 下午7:33, Dmitriy Pavlov 写道:

Hi Denis,

Could you please chime in? I had not practiced website updates yet.

Sincerely,
Dmitriy Pavlov

сб, 2 мар. 2019 г. в 04:34, 李玉珏 <18624049...@163.com>:


Hi,

As for Ignite's chinese document, it was previously located on a cloud
note-taking page with the address of:

https://www.zybuluo.com/liyuj/note/230739

Because of the limited functionality and user experience, it has been
migrated to the following address:

https://liyuj.gitee.io

The new site has a much better look and experience than it used to be.


Can someone help me modify the link on ignite. apache. org?
Thank you very much.

About Rebalance Mode (SYNC & NONE)

[18624049226]

Hi Community,

For partition mode cache(without persistence enabled),If rebalanceMode 
is configured as NONE, rebalancing will actually occur when a new node 
is added,This does not match the function definition,i think this is a bug.


But,for persistent cache, rebalancing is controlled by the baseline 
topology,For disabling persistent cache, it seems that rebalanceMode 
config to (SYNC & NONE) has no practical significance, so what is the 
value of this parameter design? Is this a legacy of history that is 
about to be abandoned?

Re: [jira] [评论] (IGNITE-12852) Comma in field is not supported by COPY command

[18624049226]

Hi community,

if someone can help to merge this patch into repo(2.8.1&master)?

在 2020/4/17 下午4:52, Roman Kondakov (Jira) 写道:

Message Title
	Roman Kondakov 
 
*在故障 IGNITE-12852 
上评论*


重新发送: Comma in field is not supported by COPY command 



Nikolay Izhikov 
 the 
patch looks good to me.


添加评论  
添加评论 


这条信息是由Atlassian Jira发送的 (v8.3.4#803005-sha1:1f96e09)
Atlassian logo

Re: [jira] [Created] (IGNITE-12852) Comma in field is not supported by COPY command

[18624049226]

Hi Anton,

I have paid attention to the issue of IGNITE-7537, because it is now 
closed and there is no task assignment, so I created a new ticket.


This issue brings a lot of trouble to data migration, many original 
fields are separated by commas. If it is only to solve the problem of 
comma separation in one field, I think it is relatively simple,so I want 
to solve this issue.However, according to the definition of ignite-7537, 
the relevant functions are still very complete, and I think it needs a 
lot of work.


Now that you have done a lot of work in this area, I think it's better 
for you to continue to do so.However, as far as I'm concerned, it's a 
serious bug that the copy command doesn't support commas in one field, 
while other customization options are just function perfection, which 
doesn't affect the use. Anyway, thank you very much for your work.


在 2020/4/10 下午5:13, akurbanov 写道:

Hello,

Apologies for missing the thread, I am already working on this issue under
the scope of the closed ticket, which I have missed to notify about:
https://issues.apache.org/jira/browse/IGNITE-7537.

I have already fixed the parsing of quotes/field delimiters but there is a
bit more to implement the parser according to RFC4180 and some additional
features (CRLF in the fields, for example) and some other usability features
like custom delimiters, quotes.

Would you like to have a discussion on the CSV parsing and scope of this
ticket and take a look on my PR? Will prepare it today shortly.

Best regards,
Anton



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: [jira] [Created] (IGNITE-12852) Comma in field is not supported by COPY command

[18624049226]

Hi community,

I would like to start contributing with this issue, could someone please add me 
to contributors list? My login forhttps://issues.apache.org/  is liyuj.

在 2020/4/1 下午9:38, YuJue Li (Jira) 写道:

YuJue Li created IGNITE-12852:
-

  Summary: Comma in field is not supported by COPY command
  Key: IGNITE-12852
  URL: https://issues.apache.org/jira/browse/IGNITE-12852
  Project: Ignite
   Issue Type: Bug
   Components: sql
 Affects Versions: 2.8
 Reporter: YuJue Li
  Fix For: 2.8.1


CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a));
  
a.csv:

1,"a,b",2
  
COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV;
  
The copy command fails because there is a comma in the second field,but this is a fully legal and compliant CSV format




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

Re: Ignite 2.8 documentation

[18624049226]

Hi Artem,

https://apacheignite.readme.io/docs/partition-map-exchange-27

This page has no corresponding menu link, is it correct?

在 2020/3/17 上午12:47, Denis Magda 写道:

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 AM Artem Budnikov 
wrote:


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 ignite have been discarded, should related documents
also be deleted?

在 2020/3/13 上午6:08, Ivan Pavlukhin 写道:

Hi,


There are the following functions. I haven't found the related
documents. Please confirm again?

Thank you for checking this thoroughly! I looked into SQL and JDBC
items.


1.SQL:Added KILL QUERY command

Here it is https://apacheignite-sql.readme.io/docs/kill-query but it
seems no link from a parent page [1]


4.JDBC:Added cache expiry policies

Sounds strange because I an not sure that this feature was implemented.

All other pointed SQL and JDBS items seems to be missing =(

Best regards,
Ivan Pavlukhin

чт, 12 мар. 2020 г. в 15:04, 18624049226 <18624049...@163.com>:

Hi igniters,

There are the following functions. I haven't found the related
documents. Please confirm again?

1.SQL:Added KILL QUERY command

2.SQL:Added ability to specify query parallelism in CREATE TABLE's WITH
"" clause

3.SQL:Added default query timeout

4.JDBC:Added cache expiry policies

5.JDBC:Added support JDBC thin driver: connection timeout

6.JDBC:Added support query cancel

7.JDBC:Added support query timeout

8.REST:Added "caches" param for "top" command

9.REST:Added baseline topology commands to REST API

10.REST:Added memory policy metrics via REST

These are great improvements, and without documentation, developers may
not know how to use them.


在 2020/3/12 上午1:40, Artem Budnikov 写道:

Denis,

I made version 2.8 the main version on readme.io. Everybody can see
it now.

-Artem

On Wed, Mar 11, 2020 at 7:35 PM Denis Magda 

wrote:

Artem,

Understood, let's see what Alexey says. As of now, I would suggest we
publishing the existing ML pages and improve the content with no
rush.
Could you also make a 2.8 version the default one? 2.7.6 is still
selected
by default when I navigate to the documentation website.


-
Denis


On Wed, Mar 11, 2020 at 9:33 AM Artem Budnikov <
a.budnikov.ign...@gmail.com>
wrote:


Denis,

I'm waiting for answers from Alexey. I can't really tell how lont
it will
take. Of couse, we can publish everything right now and improve some

pages

later.

-Artem

On Wed, Mar 11, 2020 at 7:13 PM Denis Magda 
wrote:


Artem, thanks! How much time should it take to roll out the ML
pages?

Can

we release what's available right now and continue improving the
pages

in

parallel?

Maxim, please let me publish the blog post [1] on the apache
website

before

sending you'll send an announcement email. The article will
refer to

many

documentation pages including ML. You'll include a reference to the

blog

post in the email.

[1]



http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-announcement-plan-td46238.html

-
Denis


On Wed, Mar 11, 2020 at 8:43 AM Maxim Muzafarov 
wrote:

Artem, Folks


Thank you all.
I'll do announce the release tomorrow in the middle of the day

(~16.00

MSK

TZ).

On Wed, 11 Mar 2020 at 16:06, Artem Budnikov
 wrote:

I created the Apache Ignite Documentation 2.8 with all the new

pages

except for ML, which I and Alexey are still working on. The
docs are

not

published yet, but you can see them under version 2.8.0 if you log

into

readme.io. The ML pages could take a while, but other than that
the
initial plan on creating the docs is accomplished, so it's no
longer

an

obstacle to announcing the release.

-Artem

On Wed, Mar 11, 2020 at 11:50 AM Artem Budnikov <

a.budnikov.ign...@gmail.com> wrote:

OK, I'm going to create the 2.8 version on readme.io for all

documentation pages. If anyone is still working on the docs
version

2.7.6,

please let me know. I'll post an update in this thread when I
finish.
Further changes should be made in version 2.8.

-Artem

On Wed, Mar 11, 2020 at 10:16 AM Anton Vinogradov


wrote:

Artem,
I've updated the Read Repair page

On Thu, Mar 5, 2020 at 3:51 PM Artem Budnikov <

a.budnikov.ign...@gmail.com>

wrote:


Anton,

Could you please review the page about Read Rapair?

https://apacheignite.readme.io/docs/read-repair

-Artem

On 05.03.2020 12:20, Artem Budnikov wrote:

OK, I'll recreate it.

Nikolay, p

Re: About readme.io's latest docs

[18624049226]

Hi Artem,

*apacheignite-fs,apacheignite-mix,apacheignite-tools*

these three parts, is it missing?confirm again?

thank you very much!

在 2020/3/19 下午3:41, Artem Budnikov 写道:

Hi,

Please find the archive with the latest docs attached.

-Artem

On Thu, Mar 19, 2020 at 6:32 AM 18624049226 <18624049...@163.com 
<mailto:18624049...@163.com>> wrote:


Hi Artem,

Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the
document.

thanks!

在 2018/12/20 上午8:49, 李玉珏@163 写道:
>
> Received，thanks!
>
>
> 在 2018/12/20 上午12:55, Prachi Garg 写道:
>> Hi
>>
>> Please see attached.
>>
>> -Prachi
>>
>> On Wed, Dec 19, 2018 at 1:47 AM 李玉珏@163 <18624049...@163.com
<mailto:18624049...@163.com>
>> <mailto:18624049...@163.com <mailto:18624049...@163.com>>> wrote:
>>
>>     Hi,Prachi:
>>
>>     Can you help me?
>>
>>     Previous email have not been answered.
>>
>>     Thank you very much!
>>
>>     在 2018/12/10 下午7:33, 李玉珏@163 写道:
>>>
>>>     Prachi,
>>>
>>>
>>>     Can you help to export all the latest version of all documents
>>>     to me?
>>>     I am ready to make a synchronization of the chinese version of
>>>     the document.
>>>
>>>     thanks!
>>>
>>>
>>>     在 2018/6/2 上午4:38, Prachi Garg 写道:
>>>>     Please see attached.
>>>>
>>>>     On Fri, Jun 1, 2018 at 9:22 AM, 李玉珏@163
<18624049...@163.com <mailto:18624049...@163.com>
>>>>     <mailto:18624049...@163.com
<mailto:18624049...@163.com>>> wrote:
>>>>
>>>>         Prachi,
>>>>
>>>>
>>>>         Can you help to export all the latest version of all
>>>>         documents to me?
>>>>         I am ready to make a synchronization of the chinese
version
>>>>         of the document.
>>>>
>>>>         thanks!
>>>>
>>>>
>>>>         在 2017/11/24 下午1:33, Prachi Garg 写道:
>>>>>         Attached.
>>>>>
>>>>>         On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163
>>>>>         <18624049...@163.com <mailto:18624049...@163.com>
<mailto:18624049...@163.com <mailto:18624049...@163.com>>> wrote:
>>>>>
>>>>>             Prachi,
>>>>>
>>>>>
>>>>>             Can you help me to export all the latest version of
>>>>>             all documents to me?
>>>>>             I am ready to make a synchronization of the chinese
>>>>>             version of the document.
>>>>>
>>>>>             thanks!
>>>>>
>>>>>             在 2017/8/17 上午2:05, Prachi Garg 写道:
>>>>>>             Please see attached.
>>>>>>
>>>>>>             -P
>>>>>>
>>>>>>             On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda
>>>>>>             mailto:dma...@gridgain.com> <mailto:dma...@gridgain.com
<mailto:dma...@gridgain.com>>> wrote:
>>>>>>
>>>>>>                 Hi!
>>>>>>
>>>>>>                 Prachi is on vacation and will send you the
>>>>>>                 latest version as soon as she is back to work.
>>>>>>
>>>>>>                 —
>>>>>>                 Denis
>>>>>>
>>>>>>>                 On Aug 7, 2017, at 5:33 AM, 李玉珏@163
>>>>>>>                 <18624049...@163.com
<mailto:18624049...@163.com>
>>>>>>>                 <mailto:18624049...@163.com
<mailto:18624049...@163.com>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>                 Prachi,
>>>>>>>
>>>>>>>
>>>>>>>                 Can you help me to export all the latest
version
>>>>>>>                 of al

Re: About readme.io's latest docs

[18624049226]

   same export
forIgnite.NET
<http://ignite.net/>and
Hadoop/Spark
documentation?

D.

On Tue, May
24, 2016 at
6:09 AM,
李玉珏@163<18624049...@163.com
<mailto:18624049...@163.com>>wrote:

Hi:

Readme.io
<http://readme.io/>has
the
function
of
exporting
the
document,
can I
have the
right to
export
the
document?
I have a
copy of
the
previous
version
of the
document,
if can
export
the
latest
document,
I would
like to
compare,
for the
chinese
document
to do an
update.

myreadme.io
<http://readme.io/>account
is18624049...@163.com
<mailto:18624049...@163.com>.

thanks!




提示图标邮件带有附件预览链接，若您转发或回复此邮件时不希望对方预览附件，建议您手动删除链接。
共有*1*个附件

apacheignite-2016-6-2.zip(5M)
极速下载
    
<http://preview.mail.163.com/xdownload?filename=apacheignite-2016-6-2.zip&mid=xtbBlAF8jVD%2Ba6JjtgAAsW&part=3&sign=4bf92466402f528af97c9bed1029919d&time=1464928702&uid=18624049226%40163.com>在线预览

<http://preview.mail.163.com/preview?mid=xtbBlAF8jVD%2Ba6JjtgAAsW&part=3&sign=4bf92466402f528af97c9bed1029919d&time=1464928702&uid=18624049226%40163.com>






提示图标邮件带有附件预览链接，若您转发或回复此邮件时不希望对方预览附件，建议您手动删除链接。
共有*1*个附件

apacheignite-fs-2016-6-9.zip(206K)
        极速下载

<http://preview.mail.163.com/xdownload?filename=apacheignite-fs-2016-6-9.zip&mid=1tbiYxeEjVaDoH1DVgAAsg&part=3&sign=c0b6e08db2afeca79a74ca4a15e9d1e9&time=1465520693&uid=18624049226%40163.com>在线预览

<http://preview.mail.163.com/preview?mid=1tbiYxeEjVaDoH1DVgAAsg&part=3&sign=c0b6e08db2afeca79a74ca4a15e9d1e9&time=1465520693&uid=18624049226%40163.com>




提示图标邮件带有附件预览链接，若您转发或回复此邮件时不希望对方预览附件，建议您手动删除链接。
共有*2*个附件

    v1.6.0-ignite-fs.zip(37K)
极速下载

<http://preview.mail.163.com/xdownload?filename=v1.6.0-ignite-fs.zip&mid=1tbiThnNjVUCuQFnAwAAsc&part=3&sign=e796fdcb5fcf5ede0ce3a16a6dd4b1bf&time=1471960665&uid=18624049226%40163.com>在线预览

<http://preview.mail.16

Re: [DISCUSSION] Changes in Ignite release process related to documentation

[18624049226]

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 
write them,instead of adding documents after all the work is done.


在 2020/3/13 上午12:49, Denis Magda 写道:

Igniters,

With the final 2.8 release steps checked out today by announcing the
version globally (congrats!), it's a proper time to consider and tweak our
release process, making completion of some phases more predictable and
aligned. I would like to dedicate this thread solely to changes related to
the documentation.

If to do a recap, Ignite 2.8 announcement went out of sync with the
publication of binaries, Maven and other artifacts because our technical
documentation was completed long after the vote had been closed.

We can easily eliminate such glitches for future releases if agree to start
a vote only if Ignite docs are ready and can be published the same day with
other release artifacts. If the docs are completed and available
internally while the vote goes then we can work on a release blog post
(referring to docs details) and announce the release the same day when the
binaries/docs availability.

Thoughts? Let's change the process ensuring that the vote can be started
only if technical documentation is ready to be released?

-
Denis

Re: Ignite 2.8 documentation

[18624049226]

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 ignite have been discarded, should related documents also 
be deleted?


在 2020/3/13 上午6:08, Ivan Pavlukhin 写道:

Hi,


There are the following functions. I haven't found the related documents. 
Please confirm again?

Thank you for checking this thoroughly! I looked into SQL and JDBC items.


1.SQL:Added KILL QUERY command

Here it is https://apacheignite-sql.readme.io/docs/kill-query but it
seems no link from a parent page [1]


4.JDBC:Added cache expiry policies

Sounds strange because I an not sure that this feature was implemented.

All other pointed SQL and JDBS items seems to be missing =(

Best regards,
Ivan Pavlukhin

чт, 12 мар. 2020 г. в 15:04, 18624049226 <18624049...@163.com>:

Hi igniters,

There are the following functions. I haven't found the related
documents. Please confirm again?

1.SQL:Added KILL QUERY command

2.SQL:Added ability to specify query parallelism in CREATE TABLE's WITH
"" clause

3.SQL:Added default query timeout

4.JDBC:Added cache expiry policies

5.JDBC:Added support JDBC thin driver: connection timeout

6.JDBC:Added support query cancel

7.JDBC:Added support query timeout

8.REST:Added "caches" param for "top" command

9.REST:Added baseline topology commands to REST API

10.REST:Added memory policy metrics via REST

These are great improvements, and without documentation, developers may
not know how to use them.


在 2020/3/12 上午1:40, Artem Budnikov 写道:

Denis,

I made version 2.8 the main version on readme.io. Everybody can see it now.

-Artem

On Wed, Mar 11, 2020 at 7:35 PM Denis Magda  wrote:


Artem,

Understood, let's see what Alexey says. As of now, I would suggest we
publishing the existing ML pages and improve the content with no rush.
Could you also make a 2.8 version the default one? 2.7.6 is still selected
by default when I navigate to the documentation website.


-
Denis


On Wed, Mar 11, 2020 at 9:33 AM Artem Budnikov <
a.budnikov.ign...@gmail.com>
wrote:


Denis,

I'm waiting for answers from Alexey. I can't really tell how lont it will
take. Of couse, we can publish everything right now and improve some

pages

later.

-Artem

On Wed, Mar 11, 2020 at 7:13 PM Denis Magda  wrote:


Artem, thanks! How much time should it take to roll out the ML pages?

Can

we release what's available right now and continue improving the pages

in

parallel?

Maxim, please let me publish the blog post [1] on the apache website

before

sending you'll send an announcement email. The article will refer to

many

documentation pages including ML. You'll include a reference to the

blog

post in the email.

[1]



http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-announcement-plan-td46238.html

-
Denis


On Wed, Mar 11, 2020 at 8:43 AM Maxim Muzafarov 

wrote:

Artem, Folks


Thank you all.
I'll do announce the release tomorrow in the middle of the day

(~16.00

MSK

TZ).

On Wed, 11 Mar 2020 at 16:06, Artem Budnikov
 wrote:

I created the Apache Ignite Documentation 2.8 with all the new

pages

except for ML, which I and Alexey are still working on. The docs are

not

published yet, but you can see them under version 2.8.0 if you log

into

readme.io. The ML pages could take a while, but other than that the
initial plan on creating the docs is accomplished, so it's no longer

an

obstacle to announcing the release.

-Artem

On Wed, Mar 11, 2020 at 11:50 AM Artem Budnikov <

a.budnikov.ign...@gmail.com> wrote:

OK, I'm going to create the 2.8 version on readme.io for all

documentation pages. If anyone is still working on the docs version

2.7.6,

please let me know. I'll post an update in this thread when I finish.
Further changes should be made in version 2.8.

-Artem

On Wed, Mar 11, 2020 at 10:16 AM Anton Vinogradov 

wrote:

Artem,
I've updated the Read Repair page

On Thu, Mar 5, 2020 at 3:51 PM Artem Budnikov <

a.budnikov.ign...@gmail.com>

wrote:


Anton,

Could you please review the page about Read Rapair?

https://apacheignite.readme.io/docs/read-repair

-Artem

On 05.03.2020 12:20, Artem Budnikov wrote:

OK, I'll recreate it.

Nikolay, please let me know when you are finished with the

Metrics

and

system views documentation. I'm done with the list of docs we
identified in this thread and want to publish v. 2.8.

-Artem

On 05.03.2020 11:55, Maxim Muzafarov wrote:

Artem,

I've created that. It is not public and can be safely

removed

since

it's a full copy of 2.7.6 (at that moment)

On Thu, 5 Mar 2020 at 11:53, Artem Budnikov
 wrote:

Guys,

I see that there is already version 2.8 for Ignite docs on

readme.io.

Who created it and when? I've changed some pages under

2.7.6

version

without knowing that there is a newer version.

-Artem

Re: Ignite 2.8 documentation

[18624049226]

Hi igniters,

There are the following functions. I haven't found the related 
documents. Please confirm again?


1.SQL:Added KILL QUERY command

2.SQL:Added ability to specify query parallelism in CREATE TABLE's WITH 
"" clause


3.SQL:Added default query timeout

4.JDBC:Added cache expiry policies

5.JDBC:Added support JDBC thin driver: connection timeout

6.JDBC:Added support query cancel

7.JDBC:Added support query timeout

8.REST:Added "caches" param for "top" command

9.REST:Added baseline topology commands to REST API

10.REST:Added memory policy metrics via REST

These are great improvements, and without documentation, developers may 
not know how to use them.



在 2020/3/12 上午1:40, Artem Budnikov 写道:

Denis,

I made version 2.8 the main version on readme.io. Everybody can see it now.

-Artem

On Wed, Mar 11, 2020 at 7:35 PM Denis Magda  wrote:


Artem,

Understood, let's see what Alexey says. As of now, I would suggest we
publishing the existing ML pages and improve the content with no rush.
Could you also make a 2.8 version the default one? 2.7.6 is still selected
by default when I navigate to the documentation website.


-
Denis


On Wed, Mar 11, 2020 at 9:33 AM Artem Budnikov <
a.budnikov.ign...@gmail.com>
wrote:


Denis,

I'm waiting for answers from Alexey. I can't really tell how lont it will
take. Of couse, we can publish everything right now and improve some

pages

later.

-Artem

On Wed, Mar 11, 2020 at 7:13 PM Denis Magda  wrote:


Artem, thanks! How much time should it take to roll out the ML pages?

Can

we release what's available right now and continue improving the pages

in

parallel?

Maxim, please let me publish the blog post [1] on the apache website

before

sending you'll send an announcement email. The article will refer to

many

documentation pages including ML. You'll include a reference to the

blog

post in the email.

[1]



http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-announcement-plan-td46238.html


-
Denis


On Wed, Mar 11, 2020 at 8:43 AM Maxim Muzafarov 

wrote:

Artem, Folks


Thank you all.
I'll do announce the release tomorrow in the middle of the day

(~16.00

MSK

TZ).

On Wed, 11 Mar 2020 at 16:06, Artem Budnikov
 wrote:

I created the Apache Ignite Documentation 2.8 with all the new

pages

except for ML, which I and Alexey are still working on. The docs are

not

published yet, but you can see them under version 2.8.0 if you log

into

readme.io. The ML pages could take a while, but other than that the
initial plan on creating the docs is accomplished, so it's no longer

an

obstacle to announcing the release.

-Artem

On Wed, Mar 11, 2020 at 11:50 AM Artem Budnikov <

a.budnikov.ign...@gmail.com> wrote:

OK, I'm going to create the 2.8 version on readme.io for all

documentation pages. If anyone is still working on the docs version

2.7.6,

please let me know. I'll post an update in this thread when I finish.
Further changes should be made in version 2.8.

-Artem

On Wed, Mar 11, 2020 at 10:16 AM Anton Vinogradov 

wrote:

Artem,
I've updated the Read Repair page

On Thu, Mar 5, 2020 at 3:51 PM Artem Budnikov <

a.budnikov.ign...@gmail.com>

wrote:


Anton,

Could you please review the page about Read Rapair?

https://apacheignite.readme.io/docs/read-repair

-Artem

On 05.03.2020 12:20, Artem Budnikov wrote:

OK, I'll recreate it.

Nikolay, please let me know when you are finished with the

Metrics

and

system views documentation. I'm done with the list of docs we
identified in this thread and want to publish v. 2.8.

-Artem

On 05.03.2020 11:55, Maxim Muzafarov wrote:

Artem,

I've created that. It is not public and can be safely

removed

since

it's a full copy of 2.7.6 (at that moment)

On Thu, 5 Mar 2020 at 11:53, Artem Budnikov
 wrote:

Guys,

I see that there is already version 2.8 for Ignite docs on

readme.io.

Who created it and when? I've changed some pages under

2.7.6

version

without knowing that there is a newer version.

-Artem

On 05.03.2020 11:45, Artem Budnikov wrote:

I'm confused. Igor, could you please double check?

-Artem

On 05.03.2020 04:15, Ivan Pavlukhin wrote:

That's right, only C++ and .NET clients have partition

awareness

Are your sure? Was not the feature implemented for java

thin

client

in [1]?

[1] https://issues.apache.org/jira/browse/IGNITE-11898

Best regards,
Ivan Pavlukhin

ср, 4 мар. 2020 г. в 18:18, Denis Magda <

dma...@apache.org

:

Maxim,

Yes, it's preferable to have metrics pages fully

completed

even

though the
feature is an experimental state. We want to encourage

to

try

it out

and
switch to the new APIs eventually. Without technical

instructions

available
our users will have a hard time checking the new

capabilities.

Nikolay, thanks a lot!

-
Denis


On Wed, Mar 4, 2020 at 8:52 AM Nikolay Izhikov <

nizhi...@apache.org

wrote:


I think yes.

I will prepare documentation shortly.


4 марта 2020 г., в 17:50, Maxim Muzafarov <

mmu...@apache.org>

написал(а):

Folks,


D