[jira] [Created] (IGNITE-13918) Ignite Docs: Port Capacity Planning docs from readme.io

2020-12-28 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13918:
-

 Summary: Ignite Docs: Port Capacity Planning docs from readme.io
 Key: IGNITE-13918
 URL: https://issues.apache.org/jira/browse/IGNITE-13918
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.9
Reporter: YuJue Li
 Fix For: 2.10


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

[https://apacheignite.readme.io/docs/capacity-planning]

 



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


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

2020-11-30 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13773:
-

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


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

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

 



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


[jira] [Created] (IGNITE-13688) Ignite Docs: Port Checkpointing Mapping from readme.io

2020-11-09 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13688:
-

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


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

[https://apacheignite.readme.io/docs/continuous-mapping]

[https://apacheignite.readme.io/docs/checkpointing]

 



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


[jira] [Created] (IGNITE-13679) Entryprocessor cannot be hot deployed properly via UriDeploymentSpi

2020-11-05 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13679:
-

 Summary: Entryprocessor cannot be hot deployed properly via 
UriDeploymentSpi
 Key: IGNITE-13679
 URL: https://issues.apache.org/jira/browse/IGNITE-13679
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.9
Reporter: YuJue Li
 Fix For: 2.9.1
 Attachments: ignite-deploy.zip

Entryprocessor cannot be hot deployed properly via UriDeploymentSpi,the 
operation steps are as follows:

1.put jar in the specified folder of uriList;

2.Use example-deploy.xml,start two ignite nodes;

3.Use the DeployClient to deploy the service named "deployService";

4.Execute the test through ThickClientTest, and the result is correct;

5.Modify the code of DeployServiceImpl and DeployEntryProcessor, for example, 
change "Hello" to "Hi", then repackage it and put it into the specified folder 
of uriList;

6.Redeploy services by RedeployClient;

7.Execute the test again through ThickClientTest, and the result is 
incorrect,we will find that if the Entryprocessor accessed by the service is on 
another node, the Entryprocessor uses the old version of the class definition.



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


[jira] [Created] (IGNITE-13651) Ignite Docs: Port Apache Zeppelin docs from readme.io

2020-11-02 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13651:
-

 Summary: Ignite Docs: Port Apache Zeppelin docs from readme.io
 Key: IGNITE-13651
 URL: https://issues.apache.org/jira/browse/IGNITE-13651
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.9
Reporter: YuJue Li
 Fix For: 2.10


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

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

 



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


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

2020-10-22 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13612:
-

 Summary: 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
 Fix For: 2.10


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.3.4#803005)


[jira] [Created] (IGNITE-13611) Ignite Docs: Port Compute Grid/Checkpointing docs from readme.io

2020-10-22 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13611:
-

 Summary: Ignite Docs: Port Compute Grid/Checkpointing docs from 
readme.io
 Key: IGNITE-13611
 URL: https://issues.apache.org/jira/browse/IGNITE-13611
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.9
Reporter: YuJue Li
 Fix For: 2.10


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

https://apacheignite.readme.io/docs/checkpointing



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


[jira] [Created] (IGNITE-13538) Ignite Docs: table missing horizontal scroll bar

2020-10-06 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13538:
-

 Summary: Ignite Docs: table missing horizontal scroll bar
 Key: IGNITE-13538
 URL: https://issues.apache.org/jira/browse/IGNITE-13538
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.9
Reporter: YuJue Li
 Fix For: 2.10
 Attachments: image-2020-10-07-09-01-09-803.png

[https://ignite.apache.org/docs/latest/clustering/network-configuration]

!image-2020-10-07-09-01-09-803.png!

If the table is wide, the content on the right will not be visible

 

 



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


[jira] [Created] (IGNITE-13537) Ignite Docs:codeblock (tabs) component appearance improvement

2020-10-06 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13537:
-

 Summary: Ignite  Docs:codeblock (tabs) component appearance 
improvement
 Key: IGNITE-13537
 URL: https://issues.apache.org/jira/browse/IGNITE-13537
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.9
Reporter: YuJue Li
 Fix For: 2.10


about code block,see:

[https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment]

!6ccIXycaAwAAAIDfgKCMF7Qqk PNRF7DRGMbX 
Hl7XnBAQAAAOCfRVDGW9qmUlmWKsvq35xoDAC 
iaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAIDhf3Y0NOKTdnGDAElFTkSuQmCC!
>From this screenshot, the content of code block is mixed with the doc body. We 
>don't know where the boundary of code block is.
 
And the original readme.io The codeblock looks like this:
!8BrzjYPW22CXEASUVORK5CYII=!
It's not just the highlighted code, it has a gray background as a whole.
 
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.



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


[jira] [Created] (IGNITE-13346) “Joining persistence node to in-memory cluster couldn't be allowed” Verification is too strict

2020-08-10 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13346:
-

 Summary: “Joining persistence node to in-memory cluster couldn't 
be allowed” Verification is too strict
 Key: IGNITE-13346
 URL: https://issues.apache.org/jira/browse/IGNITE-13346
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Affects Versions: 2.8.1
Reporter: YuJue Li
 Fix For: 2.10


1.Start a node that turns on persistence and then activate

2.Start visor and connect to cluster

3.Stop the node and restart the node

4.the node start failer and the exception are as folloews:

Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining persistence 
node to in-memory cluster couldn't be allowed due to baseline auto-adjust is 
enabled and timeout equal to 0

I think there may be problems with the verification logic here. There are two 
possible solutions:

1.Relax the restrictions and exclude the client nodes.

2.Point out the IP address corresponding to the in-memory cluster node, which 
is convenient for troubleshooting.



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


[jira] [Created] (IGNITE-13290) SpringTransactionManager adds support for nested transactions

2020-07-22 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13290:
-

 Summary: SpringTransactionManager adds support for nested 
transactions
 Key: IGNITE-13290
 URL: https://issues.apache.org/jira/browse/IGNITE-13290
 Project: Ignite
  Issue Type: Bug
  Components: spring
Affects Versions: 2.8.1
Reporter: YuJue Li
 Fix For: 2.10


If the transaction propagation of the outer method is REQUIRED, the transaction 
propagation of the inner method is REQUIRES_NEW, the following error will be 
prompted:
org.springframework.transaction.TransactionSuspensionNotSupportedException: 
Transaction manager 
[org.apache.ignite.transactions.spring.SpringTransactionManager] does not 
support transaction suspension

But we see, Ignite's org.apache.ignite.transactions.Transaction, there are 
suspend() and resume() methods, and the function is normal, so 
SpringTransactionManager should support similar functions.



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


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

2020-07-06 Thread 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)


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

2020-04-01 Thread 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)


[jira] [Created] (IGNITE-12202) Support system function ROWNUM()

2019-09-19 Thread YuJue Li (Jira)
YuJue Li created IGNITE-12202:
-

 Summary: Support system function ROWNUM()
 Key: IGNITE-12202
 URL: https://issues.apache.org/jira/browse/IGNITE-12202
 Project: Ignite
  Issue Type: New Feature
  Components: sql
Affects Versions: 2.7.5
Reporter: YuJue Li
 Fix For: 3.0


H2 database support system function ROWNUM(), which is very common, Ignite 
should support its distributed version.



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


[jira] [Created] (IGNITE-5838) The IgniteCache.loadCacheAsync method is not executed asynchronously.

2017-07-25 Thread Yujue Li (JIRA)
Yujue Li created IGNITE-5838:


 Summary: The IgniteCache.loadCacheAsync method is not executed 
asynchronously.
 Key: IGNITE-5838
 URL: https://issues.apache.org/jira/browse/IGNITE-5838
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.0
Reporter: Yujue Li
Priority: Blocker
 Fix For: 2.2


The IgniteCache.loadCacheAsync method is not executed asynchronously.
for example,in the 
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/store/spring/CacheSpringStoreExample.java:
line 129:
If modified to:
cache.loadCacheAsync(null, ENTRY_COUNT);
We will find that the cache is not loaded asynchronously.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (IGNITE-5713) The ignite-spring module should not rely on the ignite-indexing module.

2017-07-07 Thread Yujue Li (JIRA)
Yujue Li created IGNITE-5713:


 Summary: The ignite-spring module should not rely on the 
ignite-indexing module.
 Key: IGNITE-5713
 URL: https://issues.apache.org/jira/browse/IGNITE-5713
 Project: Ignite
  Issue Type: Improvement
  Components: spring
Affects Versions: 2.0
Reporter: Yujue Li
 Fix For: 2.1


In version 2.0, the ignite-spring module has increased reliance on the 
ignite-indexing module, which is not appropriate.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (IGNITE-5696) A localListenAsync method is missing in the IgniteMessaging interface.

2017-07-04 Thread Yujue Li (JIRA)
Yujue Li created IGNITE-5696:


 Summary: A localListenAsync method is missing in the 
IgniteMessaging interface.
 Key: IGNITE-5696
 URL: https://issues.apache.org/jira/browse/IGNITE-5696
 Project: Ignite
  Issue Type: Bug
  Components: messaging
Affects Versions: 2.0
Reporter: Yujue Li
Priority: Critical
 Fix For: 2.1


Prior to version 2.0, the localListen method supports asynchronous mode because 
of the presence of the withAsync method.
But in version 2.0, this is a problem because the withAsync method is obsolete 
and does not provide a localListenAsync method.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (IGNITE-4468) RoundRobinLoadBalancingSpi‘s documentation and Javadoc description incorrectly

2016-12-21 Thread Yujue Li (JIRA)
Yujue Li created IGNITE-4468:


 Summary: RoundRobinLoadBalancingSpi‘s documentation and Javadoc 
description incorrectly
 Key: IGNITE-4468
 URL: https://issues.apache.org/jira/browse/IGNITE-4468
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 1.8
Reporter: Yujue Li
Priority: Minor
 Fix For: 1.9


Class RoundRobinLoadBalancingSpi
Description of the perTask attribute in this class is confusing.
Some places describe the default value of true, some places describe the 
default value of false, and from the source code analysis, the default value 
should be false.
I hope the community can unify the adjustment of Javadoc and related documents.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)