[jira] [Updated] (IGNITE-9092) SQL: Support CREATE TABLE .. AS (SELECT * from ...) syntax
[
https://issues.apache.org/jira/browse/IGNITE-9092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9092:
--
Summary: SQL: Support CREATE TABLE .. AS (SELECT * from ...) syntax (was:
SQL: Support CREATE TABLE .. AS (SELECT...) syntax)
> SQL: Support CREATE TABLE .. AS (SELECT * from ...) syntax
> --
>
> Key: IGNITE-9092
> URL: https://issues.apache.org/jira/browse/IGNITE-9092
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.5, 2.6
>Reporter: Stepan Pilschikov
>Priority: Major
> Labels: ANSI99, sql-engine
>
> Currently syntax is not supported
> {code:java}
> create table test as (select * from created_table);
> Error: CREATE TABLE ... AS ... syntax is not supported (state=0A000,code=0)
> java.sql.SQLException: CREATE TABLE ... AS ... syntax is not supported
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:762)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265){code}
> But in H2 this statement allowed to do
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9092) SQL: Support CREATE TABLE .. AS (SELECT...) syntax
Stepan Pilschikov created IGNITE-9092:
-
Summary: SQL: Support CREATE TABLE .. AS (SELECT...) syntax
Key: IGNITE-9092
URL: https://issues.apache.org/jira/browse/IGNITE-9092
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.6, 2.5
Reporter: Stepan Pilschikov
Currently syntax is not supported
{code:java}
create table test as (select * from created_table);
Error: CREATE TABLE ... AS ... syntax is not supported (state=0A000,code=0)
java.sql.SQLException: CREATE TABLE ... AS ... syntax is not supported
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:762)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265){code}
But in H2 this statement allowed to do
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9240) Web console: plus sign not clickable on low resolution
Stepan Pilschikov created IGNITE-9240: - Summary: Web console: plus sign not clickable on low resolution Key: IGNITE-9240 URL: https://issues.apache.org/jira/browse/IGNITE-9240 Project: Ignite Issue Type: Bug Components: wizards Reporter: Stepan Pilschikov Attachments: image-2018-08-09-12-37-13-907.png path: /configuration/advanced/clusters Binary configuration panel On resolution less then 960px plus sign in Type configurations going under parent element and becoming not clickable Also this behavior correct for others configuration elements except addresses !image-2018-08-09-12-37-13-907.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9278) ML TF integration: Can't find free ports in range
Stepan Pilschikov created IGNITE-9278:
-
Summary: ML TF integration: Can't find free ports in range
Key: IGNITE-9278
URL: https://issues.apache.org/jira/browse/IGNITE-9278
Project: Ignite
Issue Type: Bug
Components: ml
Affects Versions: 2.7
Environment: CentOS 7
Java 8
Python 3.6.3
Ports in range 1-11000 are free
Reporter: Stepan Pilschikov
- Running cluster
- Fill caches
- Start script
Exception in nodes log
{code:java}
>>> >>> >>> >>> >>> ... ... ... ... ... ... ... >>> ... ... ... ... >>> >>> >>>
[15:27:50,295][SEVERE][service-#105][GridServiceProcessor] Service execution
stopped with error [name=TF_SERVICE_2e3875d0-1471-4f58-b51a-28d6e2dc8497,
execId=d40f3ffd-547c-4f26-867e-07c48b867bd5]
java.lang.IllegalStateException: No free ports in range [from=1, cnt=1000]
at
org.apache.ignite.tensorflow.cluster.util.ClusterPortManager.acquirePort(ClusterPortManager.java:107)
at
org.apache.ignite.tensorflow.cluster.util.TensorFlowClusterResolver.resolveAndAcquirePortsForWorkers(TensorFlowClusterResolver.java:103)
at
org.apache.ignite.tensorflow.cluster.util.TensorFlowClusterResolver.resolveAndAcquirePorts(TensorFlowClusterResolver.java:67)
at
org.apache.ignite.tensorflow.cluster.TensorFlowClusterManager.createCluster(TensorFlowClusterManager.java:116)
at
org.apache.ignite.tensorflow.cluster.TensorFlowClusterMaintainer.execute(TensorFlowClusterMaintainer.java:138)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$3.run(GridServiceProcessor.java:1396)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9313) ML TF integration: killed user script or chief processes didn't restart workers
Stepan Pilschikov created IGNITE-9313: - Summary: ML TF integration: killed user script or chief processes didn't restart workers Key: IGNITE-9313 URL: https://issues.apache.org/jira/browse/IGNITE-9313 Project: Ignite Issue Type: Bug Components: ml Affects Versions: 2.7 Reporter: Stepan Pilschikov * Run cluster * Filling caches with data * Running python script * Killing user script or chief Expected: - chief and user script processes shutdown and run again on same node (-) - rerun user script (+) Actual: - chief or user script shutting down and run again - all workers still running and didn't restart -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9313) ML TF integration: killed user script or chief processes didn't restart workers
[ https://issues.apache.org/jira/browse/IGNITE-9313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9313: -- Description: * Run cluster * Filling caches with data * Running python script * Killing user script or chief Expected: - chief and user script processes shutdown and run again on same node (-) - rerun user script (+) Actual: - chief or user script shutting down and run again - all workers still running and didn't restart was: * Run cluster * Filling caches with data * Running python script * Killing user script or chief Expected: - chief and user script processes shutdown and run again on same node (-) - rerun user script (+) Actual: - chief or user script shutting down and run again - all workers still running and didn't restart > ML TF integration: killed user script or chief processes didn't restart > workers > > > Key: IGNITE-9313 > URL: https://issues.apache.org/jira/browse/IGNITE-9313 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Priority: Major > Labels: tf-integration > > * Run cluster > * Filling caches with data > * Running python script > * Killing user script or chief > Expected: > - chief and user script processes shutdown and run again on same node (-) > - rerun user script (+) > Actual: > - chief or user script shutting down and run again > - all workers still running and didn't restart -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9313) ML TF integration: killed user script or chief processes didn't restart workers
[ https://issues.apache.org/jira/browse/IGNITE-9313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9313: -- Description: Case: * Run cluster * Filling caches with data * Running python script * Killing user script or chief Expected: - chief and user script processes shutdown and run again on same node (-) - rerun user script (+) Actual: - chief or user script shutting down and run again - all workers still running and didn't restart was: * Run cluster * Filling caches with data * Running python script * Killing user script or chief Expected: - chief and user script processes shutdown and run again on same node (-) - rerun user script (+) Actual: - chief or user script shutting down and run again - all workers still running and didn't restart > ML TF integration: killed user script or chief processes didn't restart > workers > > > Key: IGNITE-9313 > URL: https://issues.apache.org/jira/browse/IGNITE-9313 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Priority: Major > Labels: tf-integration > > Case: > * Run cluster > * Filling caches with data > * Running python script > * Killing user script or chief > Expected: > - chief and user script processes shutdown and run again on same node (-) > - rerun user script (+) > Actual: > - chief or user script shutting down and run again > - all workers still running and didn't restart -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9313) ML TF integration: killed user script or chief processes didn't restart workers
[ https://issues.apache.org/jira/browse/IGNITE-9313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9313: -- Description: Case: * Run cluster * Filling caches with data * Running python script * Killing user script or chief Expected: - chief and user script processes shutdown and run again on same node (-) - rerun user script (+) - directory with metadata was deleted and created new one in /tmp (-) Actual: - chief or user script shutting down and run again - all workers still running and didn't restart - directory with metadata (/tmp/tf_us_*) not deleted - new directory with metadata is not created after restart was: Case: * Run cluster * Filling caches with data * Running python script * Killing user script or chief Expected: - chief and user script processes shutdown and run again on same node (-) - rerun user script (+) Actual: - chief or user script shutting down and run again - all workers still running and didn't restart > ML TF integration: killed user script or chief processes didn't restart > workers > > > Key: IGNITE-9313 > URL: https://issues.apache.org/jira/browse/IGNITE-9313 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Anton Dmitriev >Priority: Major > Labels: tf-integration > > Case: > * Run cluster > * Filling caches with data > * Running python script > * Killing user script or chief > Expected: > - chief and user script processes shutdown and run again on same node (-) > - rerun user script (+) > - directory with metadata was deleted and created new one in /tmp (-) > Actual: > - chief or user script shutting down and run again > - all workers still running and didn't restart > - directory with metadata (/tmp/tf_us_*) not deleted > - new directory with metadata is not created after restart -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9193) ML TF Integration: Python process still running after node sigkill shutdown
Stepan Pilschikov created IGNITE-9193: - Summary: ML TF Integration: Python process still running after node sigkill shutdown Key: IGNITE-9193 URL: https://issues.apache.org/jira/browse/IGNITE-9193 Project: Ignite Issue Type: Bug Components: ml Affects Versions: 2.7 Reporter: Stepan Pilschikov 1. Running gird 2. Fill caches with training data 3. Run python script 4. Gird run several python processes on each node 5. Kill SIGNKILL one node Processes restore on other nodes Script is doing rerun But python processes which was created by killed node are still running -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9338) ML TF integration: tf cluster can't connect after killing first node with default port 10800
[ https://issues.apache.org/jira/browse/IGNITE-9338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9338: -- Description: Case: - Run cluster with 3 node on 1 host - Filling caches with data - Running python script - Killing lead node with port 10800 with chief + user_script processes Expect: - chief and user_script restarted on other node - script rerun Actual: - chief and user_secript restarted on other node but started to crash and run again because can't connect to default 10800 port was: Case: - Run cluster with 3 node on 1 host - Filling caches with data - Running python script - Killing lead node with port 10800 with chief + user_script processes Expect: - chief and user_script restarted on other node - script rerun Actual: - chief and user_secript restarted on other node but started to crash and run again because can't connect to default 10800 port > ML TF integration: tf cluster can't connect after killing first node with > default port 10800 > > > Key: IGNITE-9338 > URL: https://issues.apache.org/jira/browse/IGNITE-9338 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Stepan Pilschikov >Priority: Major > Labels: tf-integration > > Case: > - Run cluster with 3 node on 1 host > - Filling caches with data > - Running python script > - Killing lead node with port 10800 with chief + user_script processes > Expect: > - chief and user_script restarted on other node > - script rerun > Actual: > - chief and user_secript restarted on other node but started to crash and run > again because can't connect to default 10800 port -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9338) ML TF integration: tf cluster can't connect after killing first node with default port 10800
Stepan Pilschikov created IGNITE-9338: - Summary: ML TF integration: tf cluster can't connect after killing first node with default port 10800 Key: IGNITE-9338 URL: https://issues.apache.org/jira/browse/IGNITE-9338 Project: Ignite Issue Type: Bug Components: ml Reporter: Stepan Pilschikov Case: - Run cluster with 3 node on 1 host - Filling caches with data - Running python script - Killing lead node with port 10800 with chief + user_script processes Expect: - chief and user_script restarted on other node - script rerun Actual: - chief and user_secript restarted on other node but started to crash and run again because can't connect to default 10800 port -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9396) ML Examples: can't run examples, not enough dependencies in pom.xml
[
https://issues.apache.org/jira/browse/IGNITE-9396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9396:
--
Description:
Trying to run ml-examples and can't compile example project because several
dependencies didn't added in pom.xml
Execution:
Using JB IDEA Run->Run class to execute current class
or
`java -classpath [all classpaths which are listed in pom file] class name`
or compile with maven also failed
`mvn clean compile`
Exception:
Can't compile project. not enough dependencies
Missing dependencies:
{code:xml}
com.github.fommil.netlib
core
org.springframework.data
spring-data-commons
org.springframework
spring-beans
org.springframework
spring-context
com.h2database
h2
{code}
com.github.fommil.netlib, springframework.* and h2 need to run -
org.apache.ignite.examples.ml.dataset.AlgorithmSpecificDatasetExample
was:
Trying to run ml-examples and can't compile example project because several
dependencies didn't added in pom.xml
Execution:
Using JB IDEA Run->Run class to execute current class
or
`java -classpath [all classpaths which are listed in pom file] class name`
or compile with maven also failed
`mvn clean compile`
Exception:
Can't compile project. not enough dipendencies
Missing dependencies:
{code:xml}
com.github.fommil.netlib
core
org.springframework.data
spring-data-commons
org.springframework
spring-beans
org.springframework
spring-context
com.h2database
h2
{code}
com.github.fommil.netlib, springframework.* and h2 need to run -
org.apache.ignite.examples.ml.dataset.AlgorithmSpecificDatasetExample
> ML Examples: can't run examples, not enough dependencies in pom.xml
> ---
>
> Key: IGNITE-9396
> URL: https://issues.apache.org/jira/browse/IGNITE-9396
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to run ml-examples and can't compile example project because several
> dependencies didn't added in pom.xml
> Execution:
> Using JB IDEA Run->Run class to execute current class
> or
> `java -classpath [all classpaths which are listed in pom file] class name`
> or compile with maven also failed
> `mvn clean compile`
> Exception:
> Can't compile project. not enough dependencies
> Missing dependencies:
> {code:xml}
>
> com.github.fommil.netlib
> core
>
>
> org.springframework.data
> spring-data-commons
>
>
> org.springframework
> spring-beans
>
>
> org.springframework
> spring-context
>
>
> com.h2database
> h2
>
> {code}
> com.github.fommil.netlib, springframework.* and h2 need to run -
> org.apache.ignite.examples.ml.dataset.AlgorithmSpecificDatasetExample
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9396) ML Examples: can't run examples, not enough dependencies in pom.xml
Stepan Pilschikov created IGNITE-9396:
-
Summary: ML Examples: can't run examples, not enough dependencies
in pom.xml
Key: IGNITE-9396
URL: https://issues.apache.org/jira/browse/IGNITE-9396
Project: Ignite
Issue Type: Bug
Components: ml
Reporter: Stepan Pilschikov
Trying to run ml-examples and can't compile example project because several
dependencies didn't added in pom.xml
Execution:
Using JB IDEA Run->Run class to execute current class
or
`java -classpath [all classpaths which are listed in pom file] class name`
or compile with maven also failed
`mvn clean compile`
Exception:
Can't compile project. not enough dipendencies
Missing dependencies:
{code:xml}
com.github.fommil.netlib
core
org.springframework.data
spring-data-commons
org.springframework
spring-beans
org.springframework
spring-context
com.h2database
h2
{code}
com.github.fommil.netlib, springframework.* and h2 need to run -
org.apache.ignite.examples.ml.dataset.AlgorithmSpecificDatasetExample
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9396) ML Examples: can't run examples, not enough dependencies in pom.xml
[
https://issues.apache.org/jira/browse/IGNITE-9396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9396:
--
Affects Version/s: 2.7
> ML Examples: can't run examples, not enough dependencies in pom.xml
> ---
>
> Key: IGNITE-9396
> URL: https://issues.apache.org/jira/browse/IGNITE-9396
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Oleg Ignatenko
>Priority: Major
>
> Trying to run ml-examples and can't compile example project because several
> dependencies didn't added in pom.xml
> Execution:
> Using JB IDEA Run->Run class to execute current class
> or
> `java -classpath [all classpaths which are listed in pom file] class name`
> or compile with maven also failed
> `mvn clean compile`
> Exception:
> Can't compile project. not enough dependencies
> Missing dependencies:
> {code:xml}
>
> com.github.fommil.netlib
> core
>
>
> org.springframework.data
> spring-data-commons
>
>
> org.springframework
> spring-beans
>
>
> org.springframework
> spring-context
>
>
> com.h2database
> h2
>
> {code}
> com.github.fommil.netlib, springframework.* and h2 need to run -
> org.apache.ignite.examples.ml.dataset.AlgorithmSpecificDatasetExample
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9313) ML TF integration: killed user script or chief processes didn't restart workers
[
https://issues.apache.org/jira/browse/IGNITE-9313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9313:
--
Description:
Case:
* Run cluster
* Filling caches with data
* Running python script
* Killing user script or chief
Expected:
- chief and user script processes shutdown and run again on same node (-)
- rerun user script (-) (+)
- directory with metadata was deleted and created new one in /tmp (-)
Actual:
- chief or user script shutting down and run again
- all workers still running and didn't restart
- directory with metadata (/tmp/tf_us_*) not deleted
- new directory with metadata is not created after restart
- user script did not rerun after 'chief process' killing ('user_script'
process killing restarting script execution)
was:
Case:
* Run cluster
* Filling caches with data
* Running python script
* Killing user script or chief
Expected:
- chief and user script processes shutdown and run again on same node (-)
- rerun user script (+)
- directory with metadata was deleted and created new one in /tmp (-)
Actual:
- chief or user script shutting down and run again
- all workers still running and didn't restart
- directory with metadata (/tmp/tf_us_*) not deleted
- new directory with metadata is not created after restart
> ML TF integration: killed user script or chief processes didn't restart
> workers
>
>
> Key: IGNITE-9313
> URL: https://issues.apache.org/jira/browse/IGNITE-9313
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Anton Dmitriev
>Priority: Major
> Labels: tf-integration
>
> Case:
> * Run cluster
> * Filling caches with data
> * Running python script
> * Killing user script or chief
> Expected:
> - chief and user script processes shutdown and run again on same node (-)
> - rerun user script (-) (+)
> - directory with metadata was deleted and created new one in /tmp (-)
> Actual:
> - chief or user script shutting down and run again
> - all workers still running and didn't restart
> - directory with metadata (/tmp/tf_us_*) not deleted
> - new directory with metadata is not created after restart
> - user script did not rerun after 'chief process' killing ('user_script'
> process killing restarting script execution)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9421) ML Examples: LogisticRegressionSGDTrainerExample example result not correct
Stepan Pilschikov created IGNITE-9421:
-
Summary: ML Examples: LogisticRegressionSGDTrainerExample example
result not correct
Key: IGNITE-9421
URL: https://issues.apache.org/jira/browse/IGNITE-9421
Project: Ignite
Issue Type: Bug
Components: ml
Affects Versions: 2.6
Reporter: Stepan Pilschikov
Running
org.apache.ignite.examples.ml.regression.logistic.binary.LogisticRegressionSGDTrainerExample
example
Output:
{code}
>>> Absolute amount of errors 100
>>> Accuracy 0.0
>>> Confusion matrix is [[50, 50], [0, 0]]
>>> -
>>> Logistic regression model over partitioned dataset usage example completed.
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9427) SQL MVCC: old data read after parallel update with autoCommit=false
Stepan Pilschikov created IGNITE-9427:
-
Summary: SQL MVCC: old data read after parallel update with
autoCommit=false
Key: IGNITE-9427
URL: https://issues.apache.org/jira/browse/IGNITE-9427
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.5
Reporter: Stepan Pilschikov
Second user don't seeing first user update right after select before commit
Table:
{code:sql}create table test(id int, field_int int, field_var varchar(50),
primary key (id, field_int)) with "template=replicated,
ATOMICITY=TRANSACTIONAL{code}
With one row of data:
{code:sql}insert into test(id, field_int, field_var) values (1, 1,
'test_1'){code}
With two connections to sqlline
{code}sqlline.sh --autoCommit=false --color=true --outputFormat=csv
--showNestedErrs=true --showWarnings=true --verbose=true -u
jdbc:ignite:thin://127.0.0.1:10800 {code}
for *user_1* and *user_2*
*user_1*:
{code:sql}
begin transaction;
select * from test where id = 1 for update;
{code}
*user_2*:
{code:sql}
update test set field_var = 'updated' where id = 1; - transaction get locked
{code}
*user_1*:
{code:sql}
commit;
select * from test; - 1, 1, 'test_1'
{code}
*user_2*:
{code:sql}
1 row affected
commit;
select * from test; - 1, 1, 'updated'
{code}
*user_1*:
{code:sql}
select * from test; - 1, 1, 'test_1' < should be 'updated'
{code}
if *user_1* do commit then he will be seeing update
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9427) SQL MVCC: old data read after parallel update with autoCommit=false
[
https://issues.apache.org/jira/browse/IGNITE-9427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597279#comment-16597279
]
Stepan Pilschikov commented on IGNITE-9427:
---
Close ticket
Don't mind of REPEATABLE_READ
If *user_1* make *update* then updated data from *user_2* has come
> SQL MVCC: old data read after parallel update with autoCommit=false
>
>
> Key: IGNITE-9427
> URL: https://issues.apache.org/jira/browse/IGNITE-9427
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Second user don't seeing first user update right after select before commit
> Table:
> {code:sql}create table test(id int, field_int int, field_var varchar(50),
> primary key (id, field_int)) with "template=replicated,
> ATOMICITY=TRANSACTIONAL{code}
> With one row of data:
> {code:sql}insert into test(id, field_int, field_var) values (1, 1,
> 'test_1'){code}
> With two connections to sqlline
> {code}sqlline.sh --autoCommit=false --color=true --outputFormat=csv
> --showNestedErrs=true --showWarnings=true --verbose=true -u
> jdbc:ignite:thin://127.0.0.1:10800 {code}
> for *user_1* and *user_2*
> *user_1*:
> {code:sql}
> begin transaction;
> select * from test where id = 1 for update;
> {code}
> *user_2*:
> {code:sql}
> update test set field_var = 'updated' where id = 1; - transaction get locked
> {code}
> *user_1*:
> {code:sql}
> commit;
> select * from test; - 1, 1, 'test_1'
> {code}
> *user_2*:
> {code:sql}
> 1 row affected
> commit;
> select * from test; - 1, 1, 'updated'
> {code}
> *user_1*:
> {code:sql}
> select * from test; - 1, 1, 'test_1' < should be 'updated'
> {code}
> if *user_1* do commit then he will be seeing update
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9427) SQL MVCC: old data read after parallel update with autoCommit=false
[
https://issues.apache.org/jira/browse/IGNITE-9427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov resolved IGNITE-9427.
---
Resolution: Not A Problem
> SQL MVCC: old data read after parallel update with autoCommit=false
>
>
> Key: IGNITE-9427
> URL: https://issues.apache.org/jira/browse/IGNITE-9427
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Second user don't seeing first user update right after select before commit
> Table:
> {code:sql}create table test(id int, field_int int, field_var varchar(50),
> primary key (id, field_int)) with "template=replicated,
> ATOMICITY=TRANSACTIONAL{code}
> With one row of data:
> {code:sql}insert into test(id, field_int, field_var) values (1, 1,
> 'test_1'){code}
> With two connections to sqlline
> {code}sqlline.sh --autoCommit=false --color=true --outputFormat=csv
> --showNestedErrs=true --showWarnings=true --verbose=true -u
> jdbc:ignite:thin://127.0.0.1:10800 {code}
> for *user_1* and *user_2*
> *user_1*:
> {code:sql}
> begin transaction;
> select * from test where id = 1 for update;
> {code}
> *user_2*:
> {code:sql}
> update test set field_var = 'updated' where id = 1; - transaction get locked
> {code}
> *user_1*:
> {code:sql}
> commit;
> select * from test; - 1, 1, 'test_1'
> {code}
> *user_2*:
> {code:sql}
> 1 row affected
> commit;
> select * from test; - 1, 1, 'updated'
> {code}
> *user_1*:
> {code:sql}
> select * from test; - 1, 1, 'test_1' < should be 'updated'
> {code}
> if *user_1* do commit then he will be seeing update
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-9427) SQL MVCC: old data read after parallel update with autoCommit=false
[
https://issues.apache.org/jira/browse/IGNITE-9427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov closed IGNITE-9427.
-
Ignite Flags: (was: Docs Required)
> SQL MVCC: old data read after parallel update with autoCommit=false
>
>
> Key: IGNITE-9427
> URL: https://issues.apache.org/jira/browse/IGNITE-9427
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Second user don't seeing first user update right after select before commit
> Table:
> {code:sql}create table test(id int, field_int int, field_var varchar(50),
> primary key (id, field_int)) with "template=replicated,
> ATOMICITY=TRANSACTIONAL{code}
> With one row of data:
> {code:sql}insert into test(id, field_int, field_var) values (1, 1,
> 'test_1'){code}
> With two connections to sqlline
> {code}sqlline.sh --autoCommit=false --color=true --outputFormat=csv
> --showNestedErrs=true --showWarnings=true --verbose=true -u
> jdbc:ignite:thin://127.0.0.1:10800 {code}
> for *user_1* and *user_2*
> *user_1*:
> {code:sql}
> begin transaction;
> select * from test where id = 1 for update;
> {code}
> *user_2*:
> {code:sql}
> update test set field_var = 'updated' where id = 1; - transaction get locked
> {code}
> *user_1*:
> {code:sql}
> commit;
> select * from test; - 1, 1, 'test_1'
> {code}
> *user_2*:
> {code:sql}
> 1 row affected
> commit;
> select * from test; - 1, 1, 'updated'
> {code}
> *user_1*:
> {code:sql}
> select * from test; - 1, 1, 'test_1' < should be 'updated'
> {code}
> if *user_1* do commit then he will be seeing update
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648923#comment-16648923 ] Stepan Pilschikov edited comment on IGNITE-9824 at 10/13/18 12:43 PM: -- After python performance improvements made third run: - rerun python benches from latest sources - rerun java benches with -Djava.compiler=NONE option (by request from [~pavel.petroshenko]) - didn't run other tests again because for php/nodejs nothing changed, just take old results for comparison Results: [^thin_bench_simple_put_v3.pdf] - new results marked by more thick lines was (Author: spilschikov): After python performance improvements made third run: - rerun python benches from latest sources - rerun java benches with -Djava.compiler=NONE option (by request from [~pavel.petroshenko]) - didn't run other tests again because for php/nodejs nothing changed, just take old results for comparison Results: [^thin_bench_simple_put_v3.pdf] > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, > thin_clients_bench_results.pdf, thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648923#comment-16648923 ] Stepan Pilschikov commented on IGNITE-9824: --- After python performance improvements made third run: - rerun python benches from latest sources - rerun java benches with -Djava.compiler=NONE option (by request from [~pavel.petroshenko]) - didn't run other tests again because for php/nodejs nothing changed, just take old results for comparison Results: [^thin_bench_simple_put_v3.pdf] > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, > thin_clients_bench_results.pdf, thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: thin_bench_simple_put_v3.pdf > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, > thin_clients_bench_results.pdf, thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9951) thin php: Date data type cut nanos
[
https://issues.apache.org/jira/browse/IGNITE-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658874#comment-16658874
]
Stepan Pilschikov edited comment on IGNITE-9951 at 10/22/18 10:52 AM:
--
[~pavel.petroshenko] checked case with Date, now i'ts works
But with timestamp i still can't understand
PHP put
{code}
$cache =
$client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::TIMESTAMP)->setValueType(ObjectType::INTEGER);
$cache->put((new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-22 13:35:19.117530'))->getTimestamp() * 1000, 117530)),1);
{code}
JS get
{code}
cache = (await
igniteClient.getOrCreateCache("PH_TIMESTAMP")).setKeyType(ObjectType.PRIMITIVE_TYPE.TIMESTAMP);
console.log(JSON.stringify(await cache.get(new Timestamp(new
Date('2018-10-22T13:35:19.117530').getTime(), 117530;
{code}
When using timestamp as key i can't get value stored with php client (same
python). And in a different way, when i put key timestamp from js i can't get
it from php
But when i put timestamp key from js i can get it with python
As you see i using custom Timestamp object and define time and nano seconds
What should i do to get same timestamp in JS or Python?
was (Author: spilschikov):
[~pavel.petroshenko] checked case with Date, now i'ts works
But with timestamp i still can't understand
PHP put
{code}
$cache =
$client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::TIMESTAMP)->setValueType(ObjectType::INTEGER);
$cache->put((new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-22 13:35:19.117530'))->getTimestamp() * 1000, 117530)),1);
{code}
JS get
{code}
cache = (await
igniteClient.getOrCreateCache("PH_TIMESTAMP")).setKeyType(ObjectType.PRIMITIVE_TYPE.TIMESTAMP);
console.log(JSON.stringify(await cache.get(new Timestamp(new
Date('2018-10-22T13:35:19.117530').getTime(), 117530;
{code}
When using timestamp as key i can't get value stored with php client (same
python). And in a different way, when i put key timestamp from js i can't get
it from php
But when i put timestamp key from js i can get it with python
As you see i using custom Timestamp object and define time and nano seconds
What should i do to get same timestamp in JS or Python?
> thin php: Date data type cut nanos
> --
>
> Key: IGNITE-9951
> URL: https://issues.apache.org/jira/browse/IGNITE-9951
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
> Environment: Ignite 2.7 latest sources
> default cache configuration
> Python 3.7
> nodejs 10+
> PHP 7.2+
> Ubuntu 17
>Reporter: Stepan Pilschikov
>Assignee: Pavel Petroshenko
>Priority: Major
> Fix For: 2.7
>
>
> When using PHP data types TIMESTAMP or DATE have problem with getting data
> with others clients, main reason that is nano seconds was cutted from php
> client side
> PHP code
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Date;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> $cache = $client->getOrCreateCache("PH_DATE")
> ->setKeyType(ObjectType::INTEGER)
> ->setValueType(ObjectType::DATE);
> $cache->put(1,Date::fromDateTime(DateTime::createFromFormat('Y-m-d
> H:i:s.u', '2018-10-19 18:31:13.029726')));
> {code}
> JS output
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> Py code
> {code}
> from pyignite import Client
> from pyignite.datatypes import *
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("PH_DATE")
> print(str(cache.get(1, key_hint=IntObject)))
> {code}
> Py output
> {code}
> 2018-10-19 18:31:13
> {code}
> When im using JS or Python for put looks like
> Py
> {code}
> 2018-10-19 18:31:13.029000
> {code}
> JS
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Same story with Timestamp when
> PHP put
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Timestamp;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> try {
> $cache =
> $client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::TIMESTAMP);
> $cache->put(1,(new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
> '2018-10-19 18:31:13.029734'))->getTimestamp() * 1000, 29734)));
> } finally {
> $client->disconnect();
> }
> {code}
> Py output
> {code}
> (datetime.datetime(2018, 10, 19, 18, 31, 13), 29734)
[jira] [Comment Edited] (IGNITE-9951) thin php: Date data type cut nanos
[
https://issues.apache.org/jira/browse/IGNITE-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658874#comment-16658874
]
Stepan Pilschikov edited comment on IGNITE-9951 at 10/22/18 10:52 AM:
--
[~pavel.petroshenko] checked case with Date, now i'ts works
But with timestamp i still can't understand
PHP put
{code}
$cache =
$client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::TIMESTAMP)->setValueType(ObjectType::INTEGER);
$cache->put((new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-22 13:35:19.117530'))->getTimestamp() * 1000, 117530)),1);
{code}
JS get
{code}
cache = (await
igniteClient.getOrCreateCache("PH_TIMESTAMP")).setKeyType(ObjectType.PRIMITIVE_TYPE.TIMESTAMP);
console.log(JSON.stringify(await cache.get(new Timestamp(new
Date('2018-10-22T13:35:19.117530').getTime(), 117530;
{code}
When using timestamp as key i can't get value stored with php client (same
python). And in a different way, when i put key timestamp from js i can't get
it from php
But when i put timestamp key from js i can get it with python
As you see i using custom Timestamp object and define time and nano seconds
What should i do to get same timestamp in JS or Python?
was (Author: spilschikov):
[~pavel.petroshenko] checked case with Date, now i'ts works
But with timestamp i still can't understand
PHP put
{code}
$client = new Client();
$ENDPOINT = '127.0.0.1:10800';
$client->connect(new ClientConfiguration($ENDPOINT));
$cache =
$client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::TIMESTAMP)->setValueType(ObjectType::INTEGER);
$cache->put((new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-22 13:35:19.117530'))->getTimestamp() * 1000, 117530)),1);
{code}
JS get
{code}
await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT));
cache = (await
igniteClient.getOrCreateCache("PH_TIMESTAMP")).setKeyType(ObjectType.PRIMITIVE_TYPE.TIMESTAMP);
console.log(JSON.stringify(await cache.get(new Timestamp(new
Date('2018-10-22T13:35:19.117530').getTime(), 117530;
{code}
When using timestamp as key i can't get value stored with php client (same
python). And in a different way, when i put key timestamp from js i can't get
it from php
But when i put timestamp key from js i can get it with python
As you see i using custom Timestamp object and define time and nano seconds
What should i do to get same timestamp in JS or Python?
> thin php: Date data type cut nanos
> --
>
> Key: IGNITE-9951
> URL: https://issues.apache.org/jira/browse/IGNITE-9951
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
> Environment: Ignite 2.7 latest sources
> default cache configuration
> Python 3.7
> nodejs 10+
> PHP 7.2+
> Ubuntu 17
>Reporter: Stepan Pilschikov
>Assignee: Pavel Petroshenko
>Priority: Major
> Fix For: 2.7
>
>
> When using PHP data types TIMESTAMP or DATE have problem with getting data
> with others clients, main reason that is nano seconds was cutted from php
> client side
> PHP code
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Date;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> $cache = $client->getOrCreateCache("PH_DATE")
> ->setKeyType(ObjectType::INTEGER)
> ->setValueType(ObjectType::DATE);
> $cache->put(1,Date::fromDateTime(DateTime::createFromFormat('Y-m-d
> H:i:s.u', '2018-10-19 18:31:13.029726')));
> {code}
> JS output
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> Py code
> {code}
> from pyignite import Client
> from pyignite.datatypes import *
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("PH_DATE")
> print(str(cache.get(1, key_hint=IntObject)))
> {code}
> Py output
> {code}
> 2018-10-19 18:31:13
> {code}
> When im using JS or Python for put looks like
> Py
> {code}
> 2018-10-19 18:31:13.029000
> {code}
> JS
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Same story with Timestamp when
> PHP put
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Timestamp;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> try {
> $cache =
> $client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::TIMESTAMP);
> $cache->put(1,(new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
>
[jira] [Comment Edited] (IGNITE-9951) thin php: Date data type cut nanos
[
https://issues.apache.org/jira/browse/IGNITE-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658874#comment-16658874
]
Stepan Pilschikov edited comment on IGNITE-9951 at 10/22/18 10:53 AM:
--
[~pavel.petroshenko] tested case with Date, now i'ts works
But with timestamp i still can't understand
PHP put
{code}
$cache =
$client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::TIMESTAMP)->setValueType(ObjectType::INTEGER);
$cache->put((new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-22 13:35:19.117530'))->getTimestamp() * 1000, 117530)),1);
{code}
JS get
{code}
cache = (await
igniteClient.getOrCreateCache("PH_TIMESTAMP")).setKeyType(ObjectType.PRIMITIVE_TYPE.TIMESTAMP);
console.log(JSON.stringify(await cache.get(new Timestamp(new
Date('2018-10-22T13:35:19.117530').getTime(), 117530;
{code}
When using timestamp as key i can't get value stored with php client (same
python). And in a different way, when i put key timestamp from js i can't get
it from php
But when i put timestamp key from js i can get it with python
As you see i using custom Timestamp object and define time and nano seconds
What should i do to get same timestamp in JS or Python?
was (Author: spilschikov):
[~pavel.petroshenko] checked case with Date, now i'ts works
But with timestamp i still can't understand
PHP put
{code}
$cache =
$client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::TIMESTAMP)->setValueType(ObjectType::INTEGER);
$cache->put((new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-22 13:35:19.117530'))->getTimestamp() * 1000, 117530)),1);
{code}
JS get
{code}
cache = (await
igniteClient.getOrCreateCache("PH_TIMESTAMP")).setKeyType(ObjectType.PRIMITIVE_TYPE.TIMESTAMP);
console.log(JSON.stringify(await cache.get(new Timestamp(new
Date('2018-10-22T13:35:19.117530').getTime(), 117530;
{code}
When using timestamp as key i can't get value stored with php client (same
python). And in a different way, when i put key timestamp from js i can't get
it from php
But when i put timestamp key from js i can get it with python
As you see i using custom Timestamp object and define time and nano seconds
What should i do to get same timestamp in JS or Python?
> thin php: Date data type cut nanos
> --
>
> Key: IGNITE-9951
> URL: https://issues.apache.org/jira/browse/IGNITE-9951
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
> Environment: Ignite 2.7 latest sources
> default cache configuration
> Python 3.7
> nodejs 10+
> PHP 7.2+
> Ubuntu 17
>Reporter: Stepan Pilschikov
>Assignee: Pavel Petroshenko
>Priority: Major
> Fix For: 2.7
>
>
> When using PHP data types TIMESTAMP or DATE have problem with getting data
> with others clients, main reason that is nano seconds was cutted from php
> client side
> PHP code
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Date;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> $cache = $client->getOrCreateCache("PH_DATE")
> ->setKeyType(ObjectType::INTEGER)
> ->setValueType(ObjectType::DATE);
> $cache->put(1,Date::fromDateTime(DateTime::createFromFormat('Y-m-d
> H:i:s.u', '2018-10-19 18:31:13.029726')));
> {code}
> JS output
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> Py code
> {code}
> from pyignite import Client
> from pyignite.datatypes import *
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("PH_DATE")
> print(str(cache.get(1, key_hint=IntObject)))
> {code}
> Py output
> {code}
> 2018-10-19 18:31:13
> {code}
> When im using JS or Python for put looks like
> Py
> {code}
> 2018-10-19 18:31:13.029000
> {code}
> JS
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Same story with Timestamp when
> PHP put
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Timestamp;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> try {
> $cache =
> $client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::TIMESTAMP);
> $cache->put(1,(new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
> '2018-10-19 18:31:13.029734'))->getTimestamp() * 1000, 29734)));
> } finally {
> $client->disconnect();
> }
> {code}
> Py output
> {code}
> (datetime.datetime(2018, 10, 19, 18, 31, 13), 29734)
>
[jira] [Commented] (IGNITE-9951) thin php: Date data type cut nanos
[
https://issues.apache.org/jira/browse/IGNITE-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658874#comment-16658874
]
Stepan Pilschikov commented on IGNITE-9951:
---
[~pavel.petroshenko] checked case with Date, now i'ts works
But with timestamp i still can't understand
PHP put
{code}
$client = new Client();
$ENDPOINT = '127.0.0.1:10800';
$client->connect(new ClientConfiguration($ENDPOINT));
$cache =
$client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::TIMESTAMP)->setValueType(ObjectType::INTEGER);
$cache->put((new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-22 13:35:19.117530'))->getTimestamp() * 1000, 117530)),1);
{code}
JS get
{code}
await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT));
cache = (await
igniteClient.getOrCreateCache("PH_TIMESTAMP")).setKeyType(ObjectType.PRIMITIVE_TYPE.TIMESTAMP);
console.log(JSON.stringify(await cache.get(new Timestamp(new
Date('2018-10-22T13:35:19.117530').getTime(), 117530;
{code}
When using timestamp as key i can't get value stored with php client (same
python). And in a different way, when i put key timestamp from js i can't get
it from php
But when i put timestamp key from js i can get it with python
As you see i using custom Timestamp object and define time and nano seconds
What should i do to get same timestamp in JS or Python?
> thin php: Date data type cut nanos
> --
>
> Key: IGNITE-9951
> URL: https://issues.apache.org/jira/browse/IGNITE-9951
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
> Environment: Ignite 2.7 latest sources
> default cache configuration
> Python 3.7
> nodejs 10+
> PHP 7.2+
> Ubuntu 17
>Reporter: Stepan Pilschikov
>Assignee: Pavel Petroshenko
>Priority: Major
> Fix For: 2.7
>
>
> When using PHP data types TIMESTAMP or DATE have problem with getting data
> with others clients, main reason that is nano seconds was cutted from php
> client side
> PHP code
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Date;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> $cache = $client->getOrCreateCache("PH_DATE")
> ->setKeyType(ObjectType::INTEGER)
> ->setValueType(ObjectType::DATE);
> $cache->put(1,Date::fromDateTime(DateTime::createFromFormat('Y-m-d
> H:i:s.u', '2018-10-19 18:31:13.029726')));
> {code}
> JS output
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> Py code
> {code}
> from pyignite import Client
> from pyignite.datatypes import *
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("PH_DATE")
> print(str(cache.get(1, key_hint=IntObject)))
> {code}
> Py output
> {code}
> 2018-10-19 18:31:13
> {code}
> When im using JS or Python for put looks like
> Py
> {code}
> 2018-10-19 18:31:13.029000
> {code}
> JS
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Same story with Timestamp when
> PHP put
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Timestamp;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> try {
> $cache =
> $client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::TIMESTAMP);
> $cache->put(1,(new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
> '2018-10-19 18:31:13.029734'))->getTimestamp() * 1000, 29734)));
> } finally {
> $client->disconnect();
> }
> {code}
> Py output
> {code}
> (datetime.datetime(2018, 10, 19, 18, 31, 13), 29734)
> {code}
> should look like
> {code}
> (datetime.datetime(2018, 10, 19, 18, 31, 13, 29000), 29734)
> {code}
> Or JS
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> should look like
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Also wanna to admit that PHP Method Timestamp::fromDateTime(Data) didn't take
> nano seconds from date time (thats why in timestamp initialization i am doing
> what i do)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9951) thin php: Date data type cut nanos
[
https://issues.apache.org/jira/browse/IGNITE-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658924#comment-16658924
]
Stepan Pilschikov commented on IGNITE-9951:
---
[~alexey.kosenchuk] Yeah, looks not so pretty, but it really works, Thanks!
{code}
$cache->put((new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-22 13:35:19.117530'))->getTimestamp() * 1000 + 117, 117530)),1);
{code}
Nano seconds stay where they are and we just add millis
For me all issues are fixed
> thin php: Date data type cut nanos
> --
>
> Key: IGNITE-9951
> URL: https://issues.apache.org/jira/browse/IGNITE-9951
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
> Environment: Ignite 2.7 latest sources
> default cache configuration
> Python 3.7
> nodejs 10+
> PHP 7.2+
> Ubuntu 17
>Reporter: Stepan Pilschikov
>Assignee: Pavel Petroshenko
>Priority: Major
> Fix For: 2.7
>
>
> When using PHP data types TIMESTAMP or DATE have problem with getting data
> with others clients, main reason that is nano seconds was cutted from php
> client side
> PHP code
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Date;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> $cache = $client->getOrCreateCache("PH_DATE")
> ->setKeyType(ObjectType::INTEGER)
> ->setValueType(ObjectType::DATE);
> $cache->put(1,Date::fromDateTime(DateTime::createFromFormat('Y-m-d
> H:i:s.u', '2018-10-19 18:31:13.029726')));
> {code}
> JS output
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> Py code
> {code}
> from pyignite import Client
> from pyignite.datatypes import *
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("PH_DATE")
> print(str(cache.get(1, key_hint=IntObject)))
> {code}
> Py output
> {code}
> 2018-10-19 18:31:13
> {code}
> When im using JS or Python for put looks like
> Py
> {code}
> 2018-10-19 18:31:13.029000
> {code}
> JS
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Same story with Timestamp when
> PHP put
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Timestamp;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> try {
> $cache =
> $client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::TIMESTAMP);
> $cache->put(1,(new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
> '2018-10-19 18:31:13.029734'))->getTimestamp() * 1000, 29734)));
> } finally {
> $client->disconnect();
> }
> {code}
> Py output
> {code}
> (datetime.datetime(2018, 10, 19, 18, 31, 13), 29734)
> {code}
> should look like
> {code}
> (datetime.datetime(2018, 10, 19, 18, 31, 13, 29000), 29734)
> {code}
> Or JS
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> should look like
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Also wanna to admit that PHP Method Timestamp::fromDateTime(Data) didn't take
> nano seconds from date time (thats why in timestamp initialization i am doing
> what i do)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9951) thin php: Date data type cut nanos
[
https://issues.apache.org/jira/browse/IGNITE-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658926#comment-16658926
]
Stepan Pilschikov commented on IGNITE-9951:
---
And yes, i note that in nanos i use millis, thanks
> thin php: Date data type cut nanos
> --
>
> Key: IGNITE-9951
> URL: https://issues.apache.org/jira/browse/IGNITE-9951
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
> Environment: Ignite 2.7 latest sources
> default cache configuration
> Python 3.7
> nodejs 10+
> PHP 7.2+
> Ubuntu 17
>Reporter: Stepan Pilschikov
>Assignee: Pavel Petroshenko
>Priority: Major
> Fix For: 2.7
>
>
> When using PHP data types TIMESTAMP or DATE have problem with getting data
> with others clients, main reason that is nano seconds was cutted from php
> client side
> PHP code
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Date;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> $cache = $client->getOrCreateCache("PH_DATE")
> ->setKeyType(ObjectType::INTEGER)
> ->setValueType(ObjectType::DATE);
> $cache->put(1,Date::fromDateTime(DateTime::createFromFormat('Y-m-d
> H:i:s.u', '2018-10-19 18:31:13.029726')));
> {code}
> JS output
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> Py code
> {code}
> from pyignite import Client
> from pyignite.datatypes import *
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("PH_DATE")
> print(str(cache.get(1, key_hint=IntObject)))
> {code}
> Py output
> {code}
> 2018-10-19 18:31:13
> {code}
> When im using JS or Python for put looks like
> Py
> {code}
> 2018-10-19 18:31:13.029000
> {code}
> JS
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Same story with Timestamp when
> PHP put
> {code}
> require_once '/vendor/autoload.php';
> use Apache\Ignite\Client;
> use Apache\Ignite\ClientConfiguration;
> use Apache\Ignite\Data\Timestamp;
> use Apache\Ignite\Type\ObjectType;
>
> $client = new Client();
> $ENDPOINT = '127.0.0.1:10800';
> $client->connect(new ClientConfiguration($ENDPOINT));
> try {
> $cache =
> $client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::TIMESTAMP);
> $cache->put(1,(new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
> '2018-10-19 18:31:13.029734'))->getTimestamp() * 1000, 29734)));
> } finally {
> $client->disconnect();
> }
> {code}
> Py output
> {code}
> (datetime.datetime(2018, 10, 19, 18, 31, 13), 29734)
> {code}
> should look like
> {code}
> (datetime.datetime(2018, 10, 19, 18, 31, 13, 29000), 29734)
> {code}
> Or JS
> {code}
> "2018-10-19T15:31:13.000Z"
> {code}
> should look like
> {code}
> "2018-10-19T15:31:13.029Z"
> {code}
> Also wanna to admit that PHP Method Timestamp::fromDateTime(Data) didn't take
> nano seconds from date time (thats why in timestamp initialization i am doing
> what i do)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9950) thin python: Decimal data type didn't match with others clients
[
https://issues.apache.org/jira/browse/IGNITE-9950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9950:
--
Affects Version/s: 2.7
> thin python: Decimal data type didn't match with others clients
> ---
>
> Key: IGNITE-9950
> URL: https://issues.apache.org/jira/browse/IGNITE-9950
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
> Environment: Ignite 2.7 latest sources
> default cache configuration
> Python 3.7
> nodejs 10+
> PHP 7.2+
> Ubuntu 17
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to put Decimal value from JS or PHP client and get with Python, but
> exception throwing
> JS code:
> {code}
> IgniteClient = require('apache-ignite-client');
> IgniteClientConfiguration = IgniteClient.IgniteClientConfiguration;
> const Decimal = IgniteClient.Decimal;
> const ObjectType = IgniteClient.ObjectType;
> ENDPOINT = '127.0.0.1:10800';
> igniteClient = new IgniteClient();
> async function start() {
> await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT));
> try {
> cache = (await igniteClient.getOrCreateCache("JS_DECIMAL"))
> .setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER)
> .setValueType(ObjectType.PRIMITIVE_TYPE.DECIMAL);
> await cache.put(1, new Decimal('7.7'));
> } finally {
> igniteClient.disconnect();
> }
> }
> start();
> {code}
> Python get code
> {code}
> from pyignite import Client
> from pyignite.datatypes import *
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("JS_DECIMAL")
> print(str(cache.get(1, key_hint=IntObject)))
> {code}
> exception in python
> {code}
> Traceback (most recent call last):
> File get_value_JS_DECIMAL.py", line 7, in
> print(str(cache.get(1, key_hint=IntObject)))
> File "[ignite_src]/platforms/python/pyignite/utils.py", line 163, in
> ste_wrapper
> result = fn(*args, **kwargs)
> File "[ignite_src]/platforms/python/pyignite/cache.py", line 200, in get
> result = cache_get(self._client, self._cache_id, key, key_hint=key_hint)
> File "[ignite_src]/platforms/python/pyignite/api/key_value.py", line 107,
> in cache_get
> ('value', AnyDataObject),
> File "[ignite_src]/platforms/python/pyignite/queries/__init__.py", line
> 291, in perform
> result.value = response_struct.to_python(response)
> File "[ignite_src]/platforms/python/pyignite/queries/__init__.py", line 96,
> in to_python
> *args, **kwargs
> File "[ignite_src]/platforms/python/pyignite/datatypes/internal.py", line
> 288, in to_python
> return data_class.to_python(ctype_object)
> File "[ignite_src]/platforms/python/pyignite/datatypes/standard.py", line
> 183, in to_python
> result = decimal.Decimal(data.decode(PROTOCOL_STRING_ENCODING))
> decimal.InvalidOperation: []
> {code}
> When trying with PHP have same exception
> Also when use Decimal from Python others clients return different value:
> Python decimal put code
> {code}
> from pyignite import Client
> from pyignite.datatypes import *
> from decimal import Decimal
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("PY_DECIMAL")
> cache.put(1, Decimal('7.7'), key_hint=IntObject, value_hint=DecimalObject)
> {code}
> JS get
> {code}
> IgniteClient = require('apache-ignite-client');
> IgniteClientConfiguration = IgniteClient.IgniteClientConfiguration;
> const ObjectType = IgniteClient.ObjectType;
> ENDPOINT = '127.0.0.1:10800';
> igniteClient = new IgniteClient();
> async function start() {
> await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT));
> try {
> cache = (await igniteClient.getOrCreateCache("PY_DECIMAL"))
> .setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER);
> console.log(await cache.get(1));
> } finally {
> igniteClient.disconnect();
> }
> }
> start();
> {code}
> JS return '141350' value
> PHP have same behavior as JS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9950) thin python: Decimal data type didn't match with others clients
Stepan Pilschikov created IGNITE-9950:
-
Summary: thin python: Decimal data type didn't match with others
clients
Key: IGNITE-9950
URL: https://issues.apache.org/jira/browse/IGNITE-9950
Project: Ignite
Issue Type: Bug
Components: thin client
Environment: Ignite 2.7 latest sources
default cache configuration
Python 3.7
nodejs 10+
PHP 7.2+
Ubuntu 17
Reporter: Stepan Pilschikov
Trying to put Decimal value from JS or PHP client and get with Python, but
exception throwing
JS code:
{code}
IgniteClient = require('apache-ignite-client');
IgniteClientConfiguration = IgniteClient.IgniteClientConfiguration;
const Decimal = IgniteClient.Decimal;
const ObjectType = IgniteClient.ObjectType;
ENDPOINT = '127.0.0.1:10800';
igniteClient = new IgniteClient();
async function start() {
await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT));
try {
cache = (await igniteClient.getOrCreateCache("JS_DECIMAL"))
.setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER)
.setValueType(ObjectType.PRIMITIVE_TYPE.DECIMAL);
await cache.put(1, new Decimal('7.7'));
} finally {
igniteClient.disconnect();
}
}
start();
{code}
Python get code
{code}
from pyignite import Client
from pyignite.datatypes import *
client = Client()
client.connect('127.0.0.1', 10800)
cache = client.get_or_create_cache("JS_DECIMAL")
print(str(cache.get(1, key_hint=IntObject)))
{code}
exception in python
{code}
Traceback (most recent call last):
File get_value_JS_DECIMAL.py", line 7, in
print(str(cache.get(1, key_hint=IntObject)))
File "[ignite_src]/platforms/python/pyignite/utils.py", line 163, in
ste_wrapper
result = fn(*args, **kwargs)
File "[ignite_src]/platforms/python/pyignite/cache.py", line 200, in get
result = cache_get(self._client, self._cache_id, key, key_hint=key_hint)
File "[ignite_src]/platforms/python/pyignite/api/key_value.py", line 107, in
cache_get
('value', AnyDataObject),
File "[ignite_src]/platforms/python/pyignite/queries/__init__.py", line 291,
in perform
result.value = response_struct.to_python(response)
File "[ignite_src]/platforms/python/pyignite/queries/__init__.py", line 96,
in to_python
*args, **kwargs
File "[ignite_src]/platforms/python/pyignite/datatypes/internal.py", line
288, in to_python
return data_class.to_python(ctype_object)
File "[ignite_src]/platforms/python/pyignite/datatypes/standard.py", line
183, in to_python
result = decimal.Decimal(data.decode(PROTOCOL_STRING_ENCODING))
decimal.InvalidOperation: []
{code}
When trying with PHP have same exception
Also when use Decimal from Python others clients return different value:
Python decimal put code
{code}
from pyignite import Client
from pyignite.datatypes import *
from decimal import Decimal
client = Client()
client.connect('127.0.0.1', 10800)
cache = client.get_or_create_cache("PY_DECIMAL")
cache.put(1, Decimal('7.7'), key_hint=IntObject, value_hint=DecimalObject)
{code}
JS get
{code}
IgniteClient = require('apache-ignite-client');
IgniteClientConfiguration = IgniteClient.IgniteClientConfiguration;
const ObjectType = IgniteClient.ObjectType;
ENDPOINT = '127.0.0.1:10800';
igniteClient = new IgniteClient();
async function start() {
await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT));
try {
cache = (await igniteClient.getOrCreateCache("PY_DECIMAL"))
.setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER);
console.log(await cache.get(1));
} finally {
igniteClient.disconnect();
}
}
start();
{code}
JS return '141350' value
PHP have same behavior as JS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9951) thin php: Date data type cut nanos
Stepan Pilschikov created IGNITE-9951:
-
Summary: thin php: Date data type cut nanos
Key: IGNITE-9951
URL: https://issues.apache.org/jira/browse/IGNITE-9951
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.7
Environment: Ignite 2.7 latest sources
default cache configuration
Python 3.7
nodejs 10+
PHP 7.2+
Ubuntu 17
Reporter: Stepan Pilschikov
When using PHP data types TIMESTAMP or DATE have problem with getting data with
others clients, main reason that is nano seconds was cutted from php client side
PHP code
{code}
connect(new ClientConfiguration($ENDPOINT));
$cache = $client->getOrCreateCache("PH_DATE")
->setKeyType(ObjectType::INTEGER)
->setValueType(ObjectType::DATE);
$cache->put(1,Date::fromDateTime(DateTime::createFromFormat('Y-m-d
H:i:s.u', '2018-10-19 18:31:13.029726')));
{code}
JS output
{code}
"2018-10-19T15:31:13.000Z"
{code}
Py code
{code}
from pyignite import Client
from pyignite.datatypes import *
client = Client()
client.connect('127.0.0.1', 10800)
cache = client.get_or_create_cache("PH_DATE")
print(str(cache.get(1, key_hint=IntObject)))
{code}
Py output
{code}
2018-10-19 18:31:13
{code}
When im using JS or Python for put looks like
Py
{code}
2018-10-19 18:31:13.029000
{code}
JS
{code}
"2018-10-19T15:31:13.029Z"
{code}
Same story with Timestamp when
PHP put
{code}
connect(new ClientConfiguration($ENDPOINT));
try {
$cache =
$client->getOrCreateCache("PH_TIMESTAMP")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::TIMESTAMP);
$cache->put(1,(new Timestamp((DateTime::createFromFormat('Y-m-d H:i:s.u',
'2018-10-19 18:31:13.029734'))->getTimestamp() * 1000, 29734)));
} finally {
$client->disconnect();
}
{code}
Py output
{code}
(datetime.datetime(2018, 10, 19, 18, 31, 13), 29734)
{code}
should look like
{code}
(datetime.datetime(2018, 10, 19, 18, 31, 13, 29000), 29734)
{code}
Or JS
{code}
"2018-10-19T15:31:13.000Z"
{code}
should look like
{code}
"2018-10-19T15:31:13.029Z"
{code}
Also wanna to admit that PHP Method Timestamp::fromDateTime(Data) didn't take
nano seconds from date time (thats why in timestamp initialization i am doing
what i do)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9908) thin python: Can't use client with windows
Stepan Pilschikov created IGNITE-9908:
-
Summary: thin python: Can't use client with windows
Key: IGNITE-9908
URL: https://issues.apache.org/jira/browse/IGNITE-9908
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.7
Environment: Windows 10 1803
Python 3.7
Client module installed from latest sources, branch - master
Ignite compiled from latest sources
Reporter: Stepan Pilschikov
Trying to use thin python client on Windows and have exception
Python excetion:
{code}
Traceback (most recent call last):
File "C:\dev\test\put_value.py", line 5, in
cache = client.get_or_create_cache("test_3")
File "[ignite path]\platforms\python\pyignite\client.py", line 306, in
get_or_create_cache
return Cache(self, settings, with_get=True)
File "[ignite path]\platforms\python\pyignite\cache.py", line 116, in __init__
result = func(client, settings)
File "[ignite path]\platforms\python\pyignite\api\cache_config.py", line 151,
in cache_get_or_create
'cache_name': name,
File "[ignite path]\platforms\python\pyignite\queries\__init__.py", line 287,
in perform
response_ctype, recv_buffer = response_struct.parse(conn)
File "[ignite path]\platforms\python\pyignite\queries\__init__.py", line 66,
in parse
buffer = client.recv(ctypes.sizeof(header_class))
File "[ignite path]\platforms\python\pyignite\connection\__init__.py", line
292, in recv
result += self._recv(buffersize-pref_size, flags)
File "[ignite path]\platforms\python\pyignite\connection\__init__.py", line
316, in _recv
raise SocketError('Socket connection broken.')
OSError: Socket connection broken.
{code}
In ignite logs:
{code}
[11:19:20,522][SEVERE][client-connector-#47][ClientListenerNioListener] Failed
to parse client request.
class org.apache.ignite.binary.BinaryObjectException: Unexpected field type
[pos=10, expected=String, actual=0]
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlagNoHandles(BinaryReaderExImpl.java:1679)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.readString(BinaryReaderExImpl.java:1057)
at
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheGetOrCreateWithNameRequest.(ClientCacheGetOrCreateWithNameRequest.java:41)
at
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:342)
at
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:238)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:140)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:45)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
Python code:
{code}
from pyignite import Client
client = Client()
client.connect('127.0.0.1', 10800)
cache = client.get_or_create_cache("test_3")
cache.put("key3", -3.3)
{code}
All others thin clients from same sources and on the same ignite binary works
well
On linux from same sources python client works well too
Troubles only with python and windows
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9982) SQLLine: can't run with option --autoCommit=false or true
[
https://issues.apache.org/jira/browse/IGNITE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662049#comment-16662049
]
Stepan Pilschikov edited comment on IGNITE-9982 at 10/24/18 10:14 AM:
--
Also command `!set autoCommit false` is not changing commit mode, always used
autocommit=true
was (Author: spilschikov):
Also command is not changing commit mode, always used autocommit=true
{code}
!set autoCommit false
{code}
> SQLLine: can't run with option --autoCommit=false or true
> -
>
> Key: IGNITE-9982
> URL: https://issues.apache.org/jira/browse/IGNITE-9982
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to run sqlline with additional options
> {code}
> $ /bin/sqlline.sh --autoCommit=false --color=true --outputFormat=csv
> --showNestedErrs=true --showWarnings=true --verbose=true -u
> jdbc:ignite:thin://127.0.0.1:10800
> {code}
> SQLline is working but with exception on start:
> {code}
> issuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver
> Connecting to jdbc:ignite:thin://127.0.0.1:10800
> Connected to: Apache Ignite (version 2.7.1#20181023-sha1:0ccde7c4)
> Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181023-sha1:0ccde7c4)
> Error: MVCC must be enabled in order to invoke transactional operation:
> COMMIT (state=25000,code=5002)
> java.sql.SQLException: MVCC must be enabled in order to invoke transactional
> operation: COMMIT
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.doCommit(JdbcThinConnection.java:369)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.setAutoCommit(JdbcThinConnection.java:328)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:178)
> at
> sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> {code}
> Without --autoCommit option sqlline running without this exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9982) SQLLine: can't run with option --autoCommit=false or true
Stepan Pilschikov created IGNITE-9982:
-
Summary: SQLLine: can't run with option --autoCommit=false or true
Key: IGNITE-9982
URL: https://issues.apache.org/jira/browse/IGNITE-9982
Project: Ignite
Issue Type: Bug
Components: mvcc, sql
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Trying to run sqlline with additional options
{code}
$ /bin/sqlline.sh --autoCommit=false --color=true --outputFormat=csv
--showNestedErrs=true --showWarnings=true --verbose=true -u
jdbc:ignite:thin://127.0.0.1:10800
{code}
SQLline is running but with exception:
{code}
issuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver
Connecting to jdbc:ignite:thin://127.0.0.1:10800
Connected to: Apache Ignite (version 2.7.1#20181023-sha1:0ccde7c4)
Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181023-sha1:0ccde7c4)
Error: MVCC must be enabled in order to invoke transactional operation: COMMIT
(state=25000,code=5002)
java.sql.SQLException: MVCC must be enabled in order to invoke transactional
operation: COMMIT
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.doCommit(JdbcThinConnection.java:369)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.setAutoCommit(JdbcThinConnection.java:328)
at sqlline.DatabaseConnection.connect(DatabaseConnection.java:178)
at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
at sqlline.Commands.connect(Commands.java:1095)
at sqlline.Commands.connect(Commands.java:1001)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.initArgs(SqlLine.java:566)
at sqlline.SqlLine.begin(SqlLine.java:643)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
Without --autoCommit option sqlline running without this exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9982) SQLLine: can't run with option --autoCommit=false or true
[
https://issues.apache.org/jira/browse/IGNITE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9982:
--
Description:
Trying to run sqlline with additional options
{code}
$ /bin/sqlline.sh --autoCommit=false --color=true --outputFormat=csv
--showNestedErrs=true --showWarnings=true --verbose=true -u
jdbc:ignite:thin://127.0.0.1:10800
{code}
SQLline is working but with exception on start:
{code}
issuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver
Connecting to jdbc:ignite:thin://127.0.0.1:10800
Connected to: Apache Ignite (version 2.7.1#20181023-sha1:0ccde7c4)
Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181023-sha1:0ccde7c4)
Error: MVCC must be enabled in order to invoke transactional operation: COMMIT
(state=25000,code=5002)
java.sql.SQLException: MVCC must be enabled in order to invoke transactional
operation: COMMIT
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.doCommit(JdbcThinConnection.java:369)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.setAutoCommit(JdbcThinConnection.java:328)
at sqlline.DatabaseConnection.connect(DatabaseConnection.java:178)
at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
at sqlline.Commands.connect(Commands.java:1095)
at sqlline.Commands.connect(Commands.java:1001)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.initArgs(SqlLine.java:566)
at sqlline.SqlLine.begin(SqlLine.java:643)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
Without --autoCommit option sqlline running without this exception
was:
Trying to run sqlline with additional options
{code}
$ /bin/sqlline.sh --autoCommit=false --color=true --outputFormat=csv
--showNestedErrs=true --showWarnings=true --verbose=true -u
jdbc:ignite:thin://127.0.0.1:10800
{code}
SQLline is running but with exception:
{code}
issuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver
Connecting to jdbc:ignite:thin://127.0.0.1:10800
Connected to: Apache Ignite (version 2.7.1#20181023-sha1:0ccde7c4)
Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181023-sha1:0ccde7c4)
Error: MVCC must be enabled in order to invoke transactional operation: COMMIT
(state=25000,code=5002)
java.sql.SQLException: MVCC must be enabled in order to invoke transactional
operation: COMMIT
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.doCommit(JdbcThinConnection.java:369)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.setAutoCommit(JdbcThinConnection.java:328)
at sqlline.DatabaseConnection.connect(DatabaseConnection.java:178)
at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
at sqlline.Commands.connect(Commands.java:1095)
at sqlline.Commands.connect(Commands.java:1001)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.initArgs(SqlLine.java:566)
at sqlline.SqlLine.begin(SqlLine.java:643)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
Transaction isolation: TRANSACTION_REPEATABLE_READ
{code}
Without --autoCommit option sqlline running without this exception
> SQLLine: can't run with option
[jira] [Commented] (IGNITE-9982) SQLLine: can't run with option --autoCommit=false or true
[
https://issues.apache.org/jira/browse/IGNITE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662049#comment-16662049
]
Stepan Pilschikov commented on IGNITE-9982:
---
Also command is not changing commit mode, always used autocommit=true
{code}
!set autoCommit false
{code}
> SQLLine: can't run with option --autoCommit=false or true
> -
>
> Key: IGNITE-9982
> URL: https://issues.apache.org/jira/browse/IGNITE-9982
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to run sqlline with additional options
> {code}
> $ /bin/sqlline.sh --autoCommit=false --color=true --outputFormat=csv
> --showNestedErrs=true --showWarnings=true --verbose=true -u
> jdbc:ignite:thin://127.0.0.1:10800
> {code}
> SQLline is working but with exception on start:
> {code}
> issuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver
> Connecting to jdbc:ignite:thin://127.0.0.1:10800
> Connected to: Apache Ignite (version 2.7.1#20181023-sha1:0ccde7c4)
> Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181023-sha1:0ccde7c4)
> Error: MVCC must be enabled in order to invoke transactional operation:
> COMMIT (state=25000,code=5002)
> java.sql.SQLException: MVCC must be enabled in order to invoke transactional
> operation: COMMIT
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.doCommit(JdbcThinConnection.java:369)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.setAutoCommit(JdbcThinConnection.java:328)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:178)
> at
> sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> {code}
> Without --autoCommit option sqlline running without this exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9991) thin clients: can't use array as cache key for PHP, JS and Python clients
[
https://issues.apache.org/jira/browse/IGNITE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9991:
--
Summary: thin clients: can't use array as cache key for PHP, JS and Python
clients (was: thin clients: can't get cache by array key for PHP, JS and
Python clients)
> thin clients: can't use array as cache key for PHP, JS and Python clients
> -
>
> Key: IGNITE-9991
> URL: https://issues.apache.org/jira/browse/IGNITE-9991
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to put cache with key as values array
> Put Py code
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
> {code}
> Get
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> print(cache.get([True, False] key_hint=BoolArrayObject))
> {code}
> output: null
> Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9991) thin clients: can't get cache by array key for PHP, JS and Python clients
Stepan Pilschikov created IGNITE-9991:
-
Summary: thin clients: can't get cache by array key for PHP, JS
and Python clients
Key: IGNITE-9991
URL: https://issues.apache.org/jira/browse/IGNITE-9991
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Trying to put cache with key as values array
Put Py code
{code}
cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
{code}
Get
{code}
cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
print(cache.get([True, False] key_hint=BoolArrayObject))
{code}
output: null
Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9991) thin clients: can't use array as cache key for PHP, JS and Python clients
[
https://issues.apache.org/jira/browse/IGNITE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665253#comment-16665253
]
Stepan Pilschikov commented on IGNITE-9991:
---
[~alexey.kosenchuk] [~Melnichuk]
Oh, ive tried. but used List, now understand that i was wrong, sorry
> thin clients: can't use array as cache key for PHP, JS and Python clients
> -
>
> Key: IGNITE-9991
> URL: https://issues.apache.org/jira/browse/IGNITE-9991
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Minor
>
> Trying to put cache with key as values array
> Put Py code
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
> {code}
> Get
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> print(cache.get([True, False] key_hint=BoolArrayObject))
> {code}
> output: null
> Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: thin_benches_v4.pdf > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_clients_bench_results.pdf, thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671314#comment-16671314 ] Stepan Pilschikov commented on IGNITE-9824: --- New benches results [^thin_benches_v4.pdf] - latest ignite sources (optimized python) > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_clients_bench_results.pdf, thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671569#comment-16671569 ] Stepan Pilschikov edited comment on IGNITE-9824 at 11/1/18 12:49 PM: - Previous bench run was wrong, because hosts configuration is not identical others Also for best comparison ive take latest ignite nightly release and run clients from latest commit and 7e547b139143f08e707d0f084f4ce677c9ee6ec0 (where python clients was merged) [^thin_benches_v5.pdf] - latest report with comparison charts was (Author: spilschikov): Previous bench run is wrong, because hosts configuration is not identical others Also for best comparison ive take latest ignite nightly release and run clients from latest commit and 7e547b139143f08e707d0f084f4ce677c9ee6ec0 (where python clients was merged) [^thin_benches_v5.pdf] - latest report with comparison charts > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v5.pdf, thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671569#comment-16671569 ] Stepan Pilschikov commented on IGNITE-9824: --- Previous bench run is wrong, because hosts configuration is not identical others Also for best comparison ive take latest ignite nightly release and run clients from latest commit and 7e547b139143f08e707d0f084f4ce677c9ee6ec0 (where python clients was merged) [^thin_benches_v5.pdf] - latest report with comparison charts > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v5.pdf, thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: thin_benches_v5.pdf > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v5.pdf, thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671569#comment-16671569 ] Stepan Pilschikov edited comment on IGNITE-9824 at 11/1/18 12:54 PM: - Previous bench run was wrong, because hosts configuration is not identical others Also for best comparison ive take latest ignite nightly release and run clients from latest commit and 7e547b139143f08e707d0f084f4ce677c9ee6ec0 (where python clients was merged) [^thin_benches_v6.pdf] - latest report with comparison charts was (Author: spilschikov): Previous bench run was wrong, because hosts configuration is not identical others Also for best comparison ive take latest ignite nightly release and run clients from latest commit and 7e547b139143f08e707d0f084f4ce677c9ee6ec0 (where python clients was merged) [^thin_benches_v5.pdf] - latest report with comparison charts > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v6.pdf, thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: (was: thin_benches_v5.pdf) > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v6.pdf, thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: thin_benches_v6.pdf > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v6.pdf, thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10014) MVCC usability: Improve description for concurrent operation exceptions
Stepan Pilschikov created IGNITE-10014:
--
Summary: MVCC usability: Improve description for concurrent
operation exceptions
Key: IGNITE-10014
URL: https://issues.apache.org/jira/browse/IGNITE-10014
Project: Ignite
Issue Type: Improvement
Components: mvcc
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Fix For: 2.8
autocommit=false
{code}
create table test(id int primary key, field_int int, field_var varchar(50))
with "template=partitioned, ATOMICITY=TRANSACTIONAL_SNAPSHOT";
insert into test(id, field_int, field_var) values (1, 1, 'test_1');
first user: `select * from test`
second user: `update test set field_var = 'updated by second user' where id =
1`
second user: `commit`
second user: `select * from test`
first user: `update test set field_var = 'updated by first user' where id =
1` -> java.sql.SQLException: Cannot serialize transaction due to write
conflict...
first user: `select * from test` -> java.sql.SQLException: Transaction is
already completed.
first user: `commit` -> java.sql.SQLException: Failed to execute DDL statement
first user: `select * from test`
second user: `select * from test`
second user: `commit`
second user: `select * from test`
{code}
Now unclear to get that i should use rollback instead of commit after
"Transaction is already completed" exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686303#comment-16686303 ] Stepan Pilschikov commented on IGNITE-9824: --- Latest run for all clients plus C++ - [^thin_benches_v7.pdf] [C++ bench code|https://gist.github.com/pilshchikov/99dcddf90c1ef184c3f9dd9aa50be973] > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v6.pdf, thin_benches_v7.pdf, thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: thin_benches_v7.pdf > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v6.pdf, thin_benches_v7.pdf, thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: thin_clients_bench_results.pdf > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_clients_bench_results.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments and comments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Description: Benchmarks for all existed ignite thin clients Case: - Running 1 or 3 nodes on first host - Running code on second host Code: - [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] - [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] Results in attachments was: Benchmarks for all existed ignite thin clients Case: - Running 1 or 3 nodes on first host - Running code on second host Code: - [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] - [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] Results in attachments and comments > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_clients_bench_results.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9824) Thin clients benches
Stepan Pilschikov created IGNITE-9824: - Summary: Thin clients benches Key: IGNITE-9824 URL: https://issues.apache.org/jira/browse/IGNITE-9824 Project: Ignite Issue Type: Test Components: thin client Environment: Ignite 2.7 Java 8 NodeJS 10.+ PHP 7.2.7 Python 3.6 Reporter: Stepan Pilschikov Benchmarks for all existed ignite thin clients Case: - Running 1 or 3 nodes on first host - Running code on second host Code: - [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] - [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] Results in attachments and comments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: thin_clients_bench_results_v2.pdf > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16644926#comment-16644926 ] Stepan Pilschikov commented on IGNITE-9824: --- To clerify benches results was applied new test strategy bench case: - Clear nodes work directory - Run ignite on first host (1 or 3 nodes) - Run metric collector script on first host [code|https://gist.github.com/pilshchikov/feed72bab1751d153f27a12011a86a6d] - Run on of new benches on second host: -- [NodeJS|https://gist.github.com/pilshchikov/1b4cad3bf8f933519e4724e148b1d9ac] -- [Python|https://gist.github.com/pilshchikov/397e4f740df7d981c1937ad0471a13db] -- [PHP|https://gist.github.com/pilshchikov/0240092de20064a4ffe9a14bfe267877] -- [JAVA|https://gist.github.com/pilshchikov/807176afab27293ef2d3490c653e009b] Env: - hosts located in same network - benches running several times (results are equals) and teked best one - hosts: Ubuntu 16, 16 CPU, 96 Gb RAM Results: - [^thin_clients_bench_results_v2.pdf] > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16644926#comment-16644926 ] Stepan Pilschikov edited comment on IGNITE-9824 at 10/10/18 1:09 PM: - To clerify benches results was applied new test strategy bench case: - Clear nodes work directory - Run ignite on first host (1 or 3 nodes) - Run metric collector script on first host [code|https://gist.github.com/pilshchikov/feed72bab1751d153f27a12011a86a6d] - Run on of new benches on second host: -- [NodeJS|https://gist.github.com/pilshchikov/1b4cad3bf8f933519e4724e148b1d9ac] -- [Python|https://gist.github.com/pilshchikov/397e4f740df7d981c1937ad0471a13db] -- [PHP|https://gist.github.com/pilshchikov/0240092de20064a4ffe9a14bfe267877] -- [JAVA|https://gist.github.com/pilshchikov/807176afab27293ef2d3490c653e009b] Env: - hosts located in same network - benches running several times (results are equals) and taken best one - hosts: Ubuntu 16, 16 CPU, 96 Gb RAM Results: - [^thin_clients_bench_results_v2.pdf] was (Author: spilschikov): To clerify benches results was applied new test strategy bench case: - Clear nodes work directory - Run ignite on first host (1 or 3 nodes) - Run metric collector script on first host [code|https://gist.github.com/pilshchikov/feed72bab1751d153f27a12011a86a6d] - Run on of new benches on second host: -- [NodeJS|https://gist.github.com/pilshchikov/1b4cad3bf8f933519e4724e148b1d9ac] -- [Python|https://gist.github.com/pilshchikov/397e4f740df7d981c1937ad0471a13db] -- [PHP|https://gist.github.com/pilshchikov/0240092de20064a4ffe9a14bfe267877] -- [JAVA|https://gist.github.com/pilshchikov/807176afab27293ef2d3490c653e009b] Env: - hosts located in same network - benches running several times (results are equals) and teked best one - hosts: Ubuntu 16, 16 CPU, 96 Gb RAM Results: - [^thin_clients_bench_results_v2.pdf] > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_clients_bench_results.pdf, > thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9453) REST: UUID column type displayed like byte array
Stepan Pilschikov created IGNITE-9453:
-
Summary: REST: UUID column type displayed like byte array
Key: IGNITE-9453
URL: https://issues.apache.org/jira/browse/IGNITE-9453
Project: Ignite
Issue Type: Bug
Components: rest
Affects Versions: 2.5
Reporter: Stepan Pilschikov
Case:
- Create table with uuid
{code:sql}
CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
{code}
- Execute `select * from test` query with rest
{code:bash}
curl
"http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
{code}
Actual:
{code:json}
{
"successStatus": 0,
"sessionToken": null,
"error": null,
"response": {
"items": [],
"last": true,
"fieldsMetadata": [
{
"schemaName": "PUBLIC",
"typeName": "TEST",
"fieldName": "ID",
"fieldTypeName": "java.lang.Integer"
},
{
"schemaName": "PUBLIC",
"typeName": "TEST",
"fieldName": "FIELD",
"fieldTypeName": "java.lang.String"
},
{
"schemaName": "PUBLIC",
"typeName": "TEST",
"fieldName": "UUID",
"fieldTypeName": "[B"
}
],
"queryId": 0
}
}
{code}
Expected:
uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
Stepan Pilschikov created IGNITE-11008: -- Summary: JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH Key: IGNITE-11008 URL: https://issues.apache.org/jira/browse/IGNITE-11008 Project: Ignite Issue Type: Bug Components: jdbc Affects Versions: 2.7 Reporter: Stepan Pilschikov Fix For: 2.8 Found redundant spaces in org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns "IS_GENERATEDCOLUMN " "BUFFER_LENGTH " -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10782) javadoc description for ml.math.exceptions.preprocessing and ml.selection.scoring.evaluator
Stepan Pilschikov created IGNITE-10782: -- Summary: javadoc description for ml.math.exceptions.preprocessing and ml.selection.scoring.evaluator Key: IGNITE-10782 URL: https://issues.apache.org/jira/browse/IGNITE-10782 Project: Ignite Issue Type: Bug Components: documentation, ml Affects Versions: 2.7 Reporter: Stepan Pilschikov Fix For: 2.8 Need to add modules description for - org.apache.ignite.ml.math.exceptions.preprocessing - org.apache.ignite.ml.selection.scoring.evaluator Located in ignite/docs/overview-summary.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10782) javadoc description for ml.math.exceptions.preprocessing and ml.selection.scoring.evaluator
[ https://issues.apache.org/jira/browse/IGNITE-10782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-10782: --- Description: Need to add modules description for - org.apache.ignite.ml.math.exceptions.preprocessing - org.apache.ignite.ml.selection.scoring.evaluator Located in ignite/docs/overview-summary.html was: Need to add modules description for - org.apache.ignite.ml.math.exceptions.preprocessing - org.apache.ignite.ml.selection.scoring.evaluator Located in ignite/docs/overview-summary.html > javadoc description for ml.math.exceptions.preprocessing and > ml.selection.scoring.evaluator > --- > > Key: IGNITE-10782 > URL: https://issues.apache.org/jira/browse/IGNITE-10782 > Project: Ignite > Issue Type: Bug > Components: documentation, ml >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Priority: Minor > Fix For: 2.8 > > > Need to add modules description for > - org.apache.ignite.ml.math.exceptions.preprocessing > - org.apache.ignite.ml.selection.scoring.evaluator > Located in ignite/docs/overview-summary.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10691) thin clients: PY, PHP and NodeJS clients different UUID format
Stepan Pilschikov created IGNITE-10691:
--
Summary: thin clients: PY, PHP and NodeJS clients different UUID
format
Key: IGNITE-10691
URL: https://issues.apache.org/jira/browse/IGNITE-10691
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Fix For: 2.8
Trying to put uuid with PY or PHP or NodeJS client and get from Java or C++
client have different results
Python put
{code}
cache = client.get_or_create_cache("UUID_PY")
cache.put(1, UUID("d597be47-949e-475b-8918-44ca836798a3"), key_hint=IntObject,
value_hint=UUIDObject)
{code}
Java get
{code}
ClientCache cache = igniteClient.getOrCreateCache("UUID_PY");
UUID id = cache.get(1);
System.out.println(id);
{code}
Java output
{code}
5b479e94-47be-97d5-a398-6783ca441889
{code}
Same for C++ thin client
And they looks like mixed up in a different order
Python: {code}d597be47-949e-475b-8918-44ca836798a3{code}
Java: {code}5b479e94-47be-97d5-a398-6783ca441889{code}
For example take "ca" in 7-8 number from the end of java uuid
On left we have "83", but in python "83" stay on right side from "ca"
Different for "44" which is on right for Java but on left for Python
NodeJS put
5fbeee4e-b2a6-44dc-99ac-6444d7fe7df6
{code}
cache = (await igniteClient.getOrCreateCache("UUID_JS"))
.setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER)
.setValueType(ObjectType.PRIMITIVE_TYPE.UUID);
key = 1;
value = [95,190,238,78,178,166,68,220,153,172,100,68,215,254,125,246];
await cache.put(key, value);
{code}
Py get
{code}
cache = client.get_or_create_cache("UUID_JS")
result = cache.get(1, key_hint=IntObject)
print(result)
{code}
Py output
{code}
5fbeee4e-b2a6-44dc-99ac-6444d7fe7df6
{code}
Java get
{code}
ClientCache cache = igniteClient.getOrCreateCache("UUID_JS");
UUID id = cache.get(1);
System.out.println(id);
{code}
Java output
{code}
dc44a6b2-4eee-be5f-f67d-fed74464ac99
{code}
PHP put
[238,15,47,237,224,122,66,220,170,89,127,143,199,56,10,205] =
"ee0f2fed-e07a-42dc-aa59-7f8fc7380acd"
{code}
$cache =
$client->getOrCreateCache("UUID_PH")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::UUID);
$cache->put(1,[238,15,47,237,224,122,66,220,170,89,127,143,199,56,10,205]);
{code}
JS get
{code}
cache = (await igniteClient.getOrCreateCache("UUID_PH"))
.setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER)
.setValueType(ObjectType.PRIMITIVE_TYPE.UUID);
result = (await cache.get(1));
{code}
JS output
{code}
238 15 47 237 224 122 66 220 170 89 127 143 199 56 10 205
{code}
Java get
{code}
ClientCache cache = igniteClient.getOrCreateCache("UUID_PH");
UUID id = cache.get(1);
System.out.println(id);
{code}
Java output
{code}
dc427ae0-ed2f-0fee-cd0a-38c78f7f59aa
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10691) thin clients: PY, PHP and NodeJS clients mixed up UUID taken from Java or C++ client
[
https://issues.apache.org/jira/browse/IGNITE-10691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-10691:
---
Summary: thin clients: PY, PHP and NodeJS clients mixed up UUID taken from
Java or C++ client (was: thin clients: PY, PHP and NodeJS clients different
UUID format)
> thin clients: PY, PHP and NodeJS clients mixed up UUID taken from Java or
> C++ client
> -
>
> Key: IGNITE-10691
> URL: https://issues.apache.org/jira/browse/IGNITE-10691
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
> Fix For: 2.8
>
>
> Trying to put uuid with PY or PHP or NodeJS client and get from Java or C++
> client have different results
> Python put
> {code}
> cache = client.get_or_create_cache("UUID_PY")
> cache.put(1, UUID("d597be47-949e-475b-8918-44ca836798a3"),
> key_hint=IntObject, value_hint=UUIDObject)
> {code}
> Java get
> {code}
> ClientCache cache = igniteClient.getOrCreateCache("UUID_PY");
> UUID id = cache.get(1);
> System.out.println(id);
> {code}
> Java output
> {code}
> 5b479e94-47be-97d5-a398-6783ca441889
> {code}
> Same for C++ thin client
> And they looks like mixed up in a different order
> Python: {code}d597be47-949e-475b-8918-44ca836798a3{code}
> Java: {code}5b479e94-47be-97d5-a398-6783ca441889{code}
> For example take "ca" in 7-8 number from the end of java uuid
> On left we have "83", but in python "83" stay on right side from "ca"
> Different for "44" which is on right for Java but on left for Python
> NodeJS put
> 5fbeee4e-b2a6-44dc-99ac-6444d7fe7df6
> {code}
> cache = (await igniteClient.getOrCreateCache("UUID_JS"))
> .setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER)
> .setValueType(ObjectType.PRIMITIVE_TYPE.UUID);
> key = 1;
> value = [95,190,238,78,178,166,68,220,153,172,100,68,215,254,125,246];
> await cache.put(key, value);
> {code}
> Py get
> {code}
> cache = client.get_or_create_cache("UUID_JS")
> result = cache.get(1, key_hint=IntObject)
> print(result)
> {code}
> Py output
> {code}
> 5fbeee4e-b2a6-44dc-99ac-6444d7fe7df6
> {code}
> Java get
> {code}
> ClientCache cache = igniteClient.getOrCreateCache("UUID_JS");
> UUID id = cache.get(1);
> System.out.println(id);
> {code}
> Java output
> {code}
> dc44a6b2-4eee-be5f-f67d-fed74464ac99
> {code}
> PHP put
> [238,15,47,237,224,122,66,220,170,89,127,143,199,56,10,205] =
> "ee0f2fed-e07a-42dc-aa59-7f8fc7380acd"
> {code}
> $cache =
> $client->getOrCreateCache("UUID_PH")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::UUID);
> $cache->put(1,[238,15,47,237,224,122,66,220,170,89,127,143,199,56,10,205]);
> {code}
> JS get
> {code}
> cache = (await igniteClient.getOrCreateCache("UUID_PH"))
> .setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER)
> .setValueType(ObjectType.PRIMITIVE_TYPE.UUID);
> result = (await cache.get(1));
> {code}
> JS output
> {code}
> 238 15 47 237 224 122 66 220 170 89 127 143 199 56 10 205
> {code}
> Java get
> {code}
> ClientCache cache = igniteClient.getOrCreateCache("UUID_PH");
> UUID id = cache.get(1);
> System.out.println(id);
> {code}
> Java output
> {code}
> dc427ae0-ed2f-0fee-cd0a-38c78f7f59aa
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10447) thin nodejs: can't execute example AuthTlsExample.js
[
https://issues.apache.org/jira/browse/IGNITE-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709801#comment-16709801
]
Stepan Pilschikov commented on IGNITE-10447:
[~alexey.kosenchuk] yeah, issue can be closed
> thin nodejs: can't execute example AuthTlsExample.js
>
>
> Key: IGNITE-10447
> URL: https://issues.apache.org/jira/browse/IGNITE-10447
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: ekaterina.vergizova
>Priority: Major
>
> Trying to run script from nodejs/examples/AuthTlsExample.js but connection
> failed
> using latest [CI
> build|https://ci.ignite.apache.org/viewLog.html?buildId=2410261=Releases_NightlyRelease_ObsoleteApacheIgniteNightlyReleaseAssembleBinaries=artifacts]
> Output:
> {code}
> $ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
> Client is stopped
> [localhost:10800] Connection failed: Error: Client network socket
> disconnected before secure TLS connection was established
> ERROR: [localhost:10800] Connection failed: Error: Client network socket
> disconnected before secure TLS connection was established
> {code}
> config.xml
> {code}
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
> value="/ignite/modules/platforms/nodejs/examples/certs/keystore.jks"/>
>
> value="/ignite/modules/platforms/nodejs/examples/certs/truststore.jks"/>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703196#comment-16703196 ] Stepan Pilschikov commented on IGNITE-9824: --- Latest run for all clients plus C++ with multi connection - [^thin_benches_v8.pdf] C++ bench code as [previous|https://gist.github.com/pilshchikov/99dcddf90c1ef184c3f9dd9aa50be973] but with connection string like "node.1.ip:10800,node.2.ip:10800,node.3.ip:10800" > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v6.pdf, thin_benches_v7.pdf, thin_benches_v8.pdf, > thin_clients_bench_results.pdf, thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9824) Thin clients benches
[ https://issues.apache.org/jira/browse/IGNITE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-9824: -- Attachment: thin_benches_v8.pdf > Thin clients benches > > > Key: IGNITE-9824 > URL: https://issues.apache.org/jira/browse/IGNITE-9824 > Project: Ignite > Issue Type: Test > Components: thin client > Environment: Ignite 2.7 > Java 8 > NodeJS 10.+ > PHP 7.2.7 > Python 3.6 >Reporter: Stepan Pilschikov >Priority: Major > Attachments: thin_bench_simple_put_v3.pdf, thin_benches_v4.pdf, > thin_benches_v6.pdf, thin_benches_v7.pdf, thin_benches_v8.pdf, > thin_clients_bench_results.pdf, thin_clients_bench_results_v2.pdf > > > Benchmarks for all existed ignite thin clients > Case: > - Running 1 or 3 nodes on first host > - Running code on second host > Code: > - > [NodeJS|https://gist.github.com/pilshchikov/8a4bdb03a8304136c22c9bf7217ee447] > - [PHP|https://gist.github.com/pilshchikov/b4351d78ad59e9cd923689c2e387bc80] > - > [Python|https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb] > - [Java|https://gist.github.com/pilshchikov/08096c78b425e00166a2ffa2aa5f49ce] > Results in attachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10447) thin nodejs: can't execute example AuthTlsExample.js
[
https://issues.apache.org/jira/browse/IGNITE-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704731#comment-16704731
]
Stepan Pilschikov commented on IGNITE-10447:
[~alexey.kosenchuk] Thanks for help
Found that i used string file path instead of reading key content with
FS.readFileSync method
> thin nodejs: can't execute example AuthTlsExample.js
>
>
> Key: IGNITE-10447
> URL: https://issues.apache.org/jira/browse/IGNITE-10447
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: ekaterina.vergizova
>Priority: Major
>
> Trying to run script from nodejs/examples/AuthTlsExample.js but connection
> failed
> using latest [CI
> build|https://ci.ignite.apache.org/viewLog.html?buildId=2410261=Releases_NightlyRelease_ObsoleteApacheIgniteNightlyReleaseAssembleBinaries=artifacts]
> Output:
> {code}
> $ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
> Client is stopped
> [localhost:10800] Connection failed: Error: Client network socket
> disconnected before secure TLS connection was established
> ERROR: [localhost:10800] Connection failed: Error: Client network socket
> disconnected before secure TLS connection was established
> {code}
> config.xml
> {code}
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
> value="/ignite/modules/platforms/nodejs/examples/certs/keystore.jks"/>
>
> value="/ignite/modules/platforms/nodejs/examples/certs/truststore.jks"/>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10358) thin python: put collections have no data type specification
[ https://issues.apache.org/jira/browse/IGNITE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697285#comment-16697285 ] Stepan Pilschikov edited comment on IGNITE-10358 at 11/23/18 3:38 PM: -- [~Melnichuk] Great Problem with collections is solved All types in all But in this branch i find out that python working bad with Decimal's Example with output: https://gist.github.com/pilshchikov/335db29e6e748c6ce334e0cb6251179e This behavior same for NodeJS, PHP, Java and affecting all special types (Collections, Arrays, Maps) Master branch does not have this issue Or im doing something wrong? For same problem with data type "Map" i should create another ticket? was (Author: spilschikov): [~Melnichuk] Great Problem with collections is solved All types in all But in this branch i find out that python working bad with Decimal's Example with output: https://gist.github.com/pilshchikov/335db29e6e748c6ce334e0cb6251179e This behavior same for NodeJS, PHP, Java and affecting all special types (Collections, Arrays, Maps) Master branch does not have this issue For same problem with data type "Map" i should create another ticket? > thin python: put collections have no data type specification > > > Key: IGNITE-10358 > URL: https://issues.apache.org/jira/browse/IGNITE-10358 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: 2.8 > > > Trying to put collection with Integers through python thin client and get > through others clients > Value type in others clients specified as "collection with Integers" > > During GET operation clients throwing exceptions that "type wrong, expected > Integer type but getting Long type" (because python collection data types are > not specified) > Python put and php and js get code/output: > https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 > Also same behavior right for Map data type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10358) thin python: put collections have no data type specification
[ https://issues.apache.org/jira/browse/IGNITE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697285#comment-16697285 ] Stepan Pilschikov commented on IGNITE-10358: [~Melnichuk] Great Problem with collections is solved All types in all But in this branch i find out that python working bad with Decimal's Example with output: https://gist.github.com/pilshchikov/335db29e6e748c6ce334e0cb6251179e This behavior same for NodeJS, PHP, Java and affecting all special types (Collections, Arrays, Maps) Master branch does not have this issue For same problem with data type "Map" i should create another ticket? > thin python: put collections have no data type specification > > > Key: IGNITE-10358 > URL: https://issues.apache.org/jira/browse/IGNITE-10358 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: 2.8 > > > Trying to put collection with Integers through python thin client and get > through others clients > Value type in others clients specified as "collection with Integers" > > During GET operation clients throwing exceptions that "type wrong, expected > Integer type but getting Long type" (because python collection data types are > not specified) > Python put and php and js get code/output: > https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 > Also same behavior right for Map data type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10358) thin python: put collections have no data type specification
[ https://issues.apache.org/jira/browse/IGNITE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-10358: --- Description: Trying to put collection with Integers through python thin client and get through others clients Value type in others clients specified as "collection with Integers" During GET operation clients throwing exceptions that "type wrong, expected Integer type but getting Long type" (because python collection data types are not specified) Python put and php and js get code/output: https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 Also same behavior right for Map data type was: Trying to put collection with Integers through python thin client and get through others clients Value type in others clients specified as "collection with Integers" During GET operation clients throwing exceptions that "type wrong, expected Integer type but getting Long type" (because python collection data types are not specified) Python put and php and js get code/output: https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 > thin python: put collections have no data type specification > > > Key: IGNITE-10358 > URL: https://issues.apache.org/jira/browse/IGNITE-10358 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Priority: Major > Fix For: 2.8 > > > Trying to put collection with Integers through python thin client and get > through others clients > Value type in others clients specified as "collection with Integers" > > During GET operation clients throwing exceptions that "type wrong, expected > Integer type but getting Long type" (because python collection data types are > not specified) > Python put and php and js get code/output: > https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 > Also same behavior right for Map data type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10358) thin python: put collections have no data type specification
Stepan Pilschikov created IGNITE-10358: -- Summary: thin python: put collections have no data type specification Key: IGNITE-10358 URL: https://issues.apache.org/jira/browse/IGNITE-10358 Project: Ignite Issue Type: Bug Components: thin client Affects Versions: 2.7 Reporter: Stepan Pilschikov Fix For: 2.8 Trying to put collection with Integers through python thin client and get through others clients Value type in others clients specified as "collection with Integers" During GET operation clients throwing exceptions that "type wrong, expected Integer type but getting Long type" (because python collection data types are not specified) Python put and php and js get code/output: https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10358) thin python: put collections have no data type specification
[ https://issues.apache.org/jira/browse/IGNITE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16699020#comment-16699020 ] Stepan Pilschikov commented on IGNITE-10358: [~isapego] yeah, all works fine, can be merged > thin python: put collections have no data type specification > > > Key: IGNITE-10358 > URL: https://issues.apache.org/jira/browse/IGNITE-10358 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: 2.8 > > > Trying to put collection with Integers through python thin client and get > through others clients > Value type in others clients specified as "collection with Integers" > > During GET operation clients throwing exceptions that "type wrong, expected > Integer type but getting Long type" (because python collection data types are > not specified) > Python put and php and js get code/output: > https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 > Also same behavior right for Map data type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10447) thin nodejs: can't execute example AuthTlsExample.js
Stepan Pilschikov created IGNITE-10447:
--
Summary: thin nodejs: can't execute example AuthTlsExample.js
Key: IGNITE-10447
URL: https://issues.apache.org/jira/browse/IGNITE-10447
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Trying to run script from nodejs/examples/AuthTlsExample.js but connection
failed
Output:
{code}
$ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
Client is stopped
[localhost:10800] Connection failed: Error: Client network socket disconnected
before secure TLS connection was established
ERROR: [localhost:10800] Connection failed: Error: Client network socket
disconnected before secure TLS connection was established
{code}
config.xml
{code}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10447) thin nodejs: can't execute example AuthTlsExample.js
[
https://issues.apache.org/jira/browse/IGNITE-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-10447:
---
Description:
Trying to run script from nodejs/examples/AuthTlsExample.js but connection
failed
using latest nightly build from ci.ignite.apache.org
Output:
{code}
$ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
Client is stopped
[localhost:10800] Connection failed: Error: Client network socket disconnected
before secure TLS connection was established
ERROR: [localhost:10800] Connection failed: Error: Client network socket
disconnected before secure TLS connection was established
{code}
config.xml
{code}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>
{code}
was:
Trying to run script from nodejs/examples/AuthTlsExample.js but connection
failed
Output:
{code}
$ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
Client is stopped
[localhost:10800] Connection failed: Error: Client network socket disconnected
before secure TLS connection was established
ERROR: [localhost:10800] Connection failed: Error: Client network socket
disconnected before secure TLS connection was established
{code}
config.xml
{code}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>
{code}
> thin nodejs: can't execute example AuthTlsExample.js
>
>
> Key: IGNITE-10447
> URL: https://issues.apache.org/jira/browse/IGNITE-10447
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to run script from nodejs/examples/AuthTlsExample.js but connection
> failed
> using latest nightly build from ci.ignite.apache.org
> Output:
> {code}
> $ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
> Client is stopped
> [localhost:10800] Connection failed: Error: Client network socket
> disconnected before secure TLS connection was established
> ERROR: [localhost:10800] Connection failed: Error: Client network socket
> disconnected before secure TLS connection was established
> {code}
> config.xml
> {code}
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
> value="/ignite/modules/platforms/nodejs/examples/certs/keystore.jks"/>
>
> value="/ignite/modules/platforms/nodejs/examples/certs/truststore.jks"/>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10447) thin nodejs: can't execute example AuthTlsExample.js
[
https://issues.apache.org/jira/browse/IGNITE-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-10447:
---
Description:
Trying to run script from nodejs/examples/AuthTlsExample.js but connection
failed
using latest [CI
build|https://ci.ignite.apache.org/viewLog.html?buildId=2410261=Releases_NightlyRelease_ObsoleteApacheIgniteNightlyReleaseAssembleBinaries=artifacts]
Output:
{code}
$ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
Client is stopped
[localhost:10800] Connection failed: Error: Client network socket disconnected
before secure TLS connection was established
ERROR: [localhost:10800] Connection failed: Error: Client network socket
disconnected before secure TLS connection was established
{code}
config.xml
{code}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>
{code}
was:
Trying to run script from nodejs/examples/AuthTlsExample.js but connection
failed
using latest nightly build from ci.ignite.apache.org
Output:
{code}
$ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
Client is stopped
[localhost:10800] Connection failed: Error: Client network socket disconnected
before secure TLS connection was established
ERROR: [localhost:10800] Connection failed: Error: Client network socket
disconnected before secure TLS connection was established
{code}
config.xml
{code}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>
{code}
> thin nodejs: can't execute example AuthTlsExample.js
>
>
> Key: IGNITE-10447
> URL: https://issues.apache.org/jira/browse/IGNITE-10447
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to run script from nodejs/examples/AuthTlsExample.js but connection
> failed
> using latest [CI
> build|https://ci.ignite.apache.org/viewLog.html?buildId=2410261=Releases_NightlyRelease_ObsoleteApacheIgniteNightlyReleaseAssembleBinaries=artifacts]
> Output:
> {code}
> $ ignite/modules/platforms/nodejs/examples$ node AuthTlsExample.js
> Client is stopped
> [localhost:10800] Connection failed: Error: Client network socket
> disconnected before secure TLS connection was established
> ERROR: [localhost:10800] Connection failed: Error: Client network socket
> disconnected before secure TLS connection was established
> {code}
> config.xml
> {code}
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
> value="/ignite/modules/platforms/nodejs/examples/certs/keystore.jks"/>
>
> value="/ignite/modules/platforms/nodejs/examples/certs/truststore.jks"/>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10358) thin python: put collections have no data type specification
[ https://issues.apache.org/jira/browse/IGNITE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697285#comment-16697285 ] Stepan Pilschikov edited comment on IGNITE-10358 at 11/26/18 12:51 PM: --- [~Melnichuk] Great Problem with collections is solved But in this branch i found that python works bad with Decimal's Example with output: https://gist.github.com/pilshchikov/335db29e6e748c6ce334e0cb6251179e This behavior same for NodeJS, PHP, Java and affecting all special types (Collections, Arrays, Maps) Master branch does not have this issue Or im doing something wrong? For same problem with data type "Map" i should create another ticket? was (Author: spilschikov): [~Melnichuk] Great Problem with collections is solved All types in all But in this branch i find out that python working bad with Decimal's Example with output: https://gist.github.com/pilshchikov/335db29e6e748c6ce334e0cb6251179e This behavior same for NodeJS, PHP, Java and affecting all special types (Collections, Arrays, Maps) Master branch does not have this issue Or im doing something wrong? For same problem with data type "Map" i should create another ticket? > thin python: put collections have no data type specification > > > Key: IGNITE-10358 > URL: https://issues.apache.org/jira/browse/IGNITE-10358 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: 2.8 > > > Trying to put collection with Integers through python thin client and get > through others clients > Value type in others clients specified as "collection with Integers" > > During GET operation clients throwing exceptions that "type wrong, expected > Integer type but getting Long type" (because python collection data types are > not specified) > Python put and php and js get code/output: > https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 > Also same behavior right for Map data type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
[
https://issues.apache.org/jira/browse/IGNITE-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9620:
--
Description:
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Exception in node logs:
{code}
[17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
class org.apache.ignite.internal.processors.query.IgniteSQLException:
Transaction is already completed.
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
Works for any query which is throwing mvcc missmatch exception
After commit select query works again
was:
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
[jira] [Created] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
Stepan Pilschikov created IGNITE-9620:
-
Summary: MVCC: select throwing `Transaction is already completed`
exception after mvcc missmatch
Key: IGNITE-9620
URL: https://issues.apache.org/jira/browse/IGNITE-9620
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Exception in node logs:
{code}
[17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
class org.apache.ignite.internal.processors.query.IgniteSQLException:
Transaction is already completed.
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
Works for any query which are throwing mvcc missmatch exception
After commit select query works again
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
[
https://issues.apache.org/jira/browse/IGNITE-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9620:
--
Description:
Using sqlline with autoCommit=true
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Exception in node logs:
{code}
[17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
class org.apache.ignite.internal.processors.query.IgniteSQLException:
Transaction is already completed.
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
Works for any query which is throwing mvcc missmatch exception
After commit select query works again
was:
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
[jira] [Updated] (IGNITE-9621) MVCC: sqlline warning that transactions are not supported
[
https://issues.apache.org/jira/browse/IGNITE-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9621:
--
Description:
MVCC enabled
--autoCommit=true
In sqlline first initial lines throwing warning message:
{code}
[1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver[m
[1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
[1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
[1;34mDriver: Apache Ignite Thin JDBC Driver (version
2.7.1#19700101-sha1:)[m
[1;34mAutocommit status: false[m
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
setTransactionIsolation
WARNING: Transactions are not supported.
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
getTransactionIsolation
WARNING: Transactions are not supported.
[1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
sqlline version 1.3.0
0: jdbc:ignite:thin://127.0.0.1:10800>
{code}
was:
MVCC enabled
--autoCommit=true
In sqlline first initial lines throwing warning message:
```
[1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver[m
[1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
[1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
[1;34mDriver: Apache Ignite Thin JDBC Driver (version
2.7.1#19700101-sha1:)[m
[1;34mAutocommit status: false[m
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
setTransactionIsolation
WARNING: Transactions are not supported.
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
getTransactionIsolation
WARNING: Transactions are not supported.
[1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
sqlline version 1.3.0
0: jdbc:ignite:thin://127.0.0.1:10800>
```
> MVCC: sqlline warning that transactions are not supported
> -
>
> Key: IGNITE-9621
> URL: https://issues.apache.org/jira/browse/IGNITE-9621
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> MVCC enabled
> --autoCommit=true
> In sqlline first initial lines throwing warning message:
> {code}
> [1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver[m
> [1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
> [1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
> [1;34mDriver: Apache Ignite Thin JDBC Driver (version
> 2.7.1#19700101-sha1:)[m
> [1;34mAutocommit status: false[m
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> setTransactionIsolation
> WARNING: Transactions are not supported.
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> getTransactionIsolation
> WARNING: Transactions are not supported.
> [1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
> sqlline version 1.3.0
> 0: jdbc:ignite:thin://127.0.0.1:10800>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9621) MVCC: sqlline warning that transactions are not supported
Stepan Pilschikov created IGNITE-9621: - Summary: MVCC: sqlline warning that transactions are not supported Key: IGNITE-9621 URL: https://issues.apache.org/jira/browse/IGNITE-9621 Project: Ignite Issue Type: Bug Components: mvcc Affects Versions: 2.7 Reporter: Stepan Pilschikov MVCC enabled --autoCommit=true In sqlline first initial lines throwing warning message: ``` [1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' '' org.apache.ignite.IgniteJdbcThinDriver[m [1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m [1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m [1;34mDriver: Apache Ignite Thin JDBC Driver (version 2.7.1#19700101-sha1:)[m [1;34mAutocommit status: false[m Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection setTransactionIsolation WARNING: Transactions are not supported. Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection getTransactionIsolation WARNING: Transactions are not supported. [1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m sqlline version 1.3.0 0: jdbc:ignite:thin://127.0.0.1:10800> ``` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
[
https://issues.apache.org/jira/browse/IGNITE-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9620:
--
Description:
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Exception in node logs:
{code}
[17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
class org.apache.ignite.internal.processors.query.IgniteSQLException:
Transaction is already completed.
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
Works for any query which is throwing mvcc missmatch exception
After commit select query works again
was:
Using sqlline with autoCommit=true
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
[jira] [Updated] (IGNITE-9621) MVCC: sqlline warning that transactions are not supported
[
https://issues.apache.org/jira/browse/IGNITE-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9621:
--
Description:
MVCC enabled
--autoCommit=false
In sqlline first initial lines throwing warning message:
{code}
[1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver[m
[1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
[1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
[1;34mDriver: Apache Ignite Thin JDBC Driver (version
2.7.1#19700101-sha1:)[m
[1;34mAutocommit status: false[m
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
setTransactionIsolation
WARNING: Transactions are not supported.
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
getTransactionIsolation
WARNING: Transactions are not supported.
[1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
sqlline version 1.3.0
0: jdbc:ignite:thin://127.0.0.1:10800>
{code}
was:
MVCC enabled
--autoCommit=true
In sqlline first initial lines throwing warning message:
{code}
[1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver[m
[1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
[1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
[1;34mDriver: Apache Ignite Thin JDBC Driver (version
2.7.1#19700101-sha1:)[m
[1;34mAutocommit status: false[m
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
setTransactionIsolation
WARNING: Transactions are not supported.
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
getTransactionIsolation
WARNING: Transactions are not supported.
[1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
sqlline version 1.3.0
0: jdbc:ignite:thin://127.0.0.1:10800>
{code}
> MVCC: sqlline warning that transactions are not supported
> -
>
> Key: IGNITE-9621
> URL: https://issues.apache.org/jira/browse/IGNITE-9621
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Stepan Pilschikov
>Priority: Major
> Fix For: 2.7
>
>
> MVCC enabled
> --autoCommit=false
> In sqlline first initial lines throwing warning message:
> {code}
> [1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver[m
> [1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
> [1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
> [1;34mDriver: Apache Ignite Thin JDBC Driver (version
> 2.7.1#19700101-sha1:)[m
> [1;34mAutocommit status: false[m
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> setTransactionIsolation
> WARNING: Transactions are not supported.
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> getTransactionIsolation
> WARNING: Transactions are not supported.
> [1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
> sqlline version 1.3.0
> 0: jdbc:ignite:thin://127.0.0.1:10800>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9625) ML: Can't build ignite binaries because java doc exception
Stepan Pilschikov created IGNITE-9625:
-
Summary: ML: Can't build ignite binaries because java doc exception
Key: IGNITE-9625
URL: https://issues.apache.org/jira/browse/IGNITE-9625
Project: Ignite
Issue Type: Bug
Components: ml
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Exception:
{code}
Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException
has occured: Execution failed due to: Class doesn't have description in file:
/target/javadoc/core/org/apache/ignite/ml/composition/boosting/GDBTrainer.GDBModel.html
Class doesn't have description in file:
/target/javadoc/core/org/apache/ignite/ml/trainers/DatasetTrainer.EmptyDatasetException.html
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9642) Examples: can't compile springdata examples
Stepan Pilschikov created IGNITE-9642:
-
Summary: Examples: can't compile springdata examples
Key: IGNITE-9642
URL: https://issues.apache.org/jira/browse/IGNITE-9642
Project: Ignite
Issue Type: Bug
Components: examples
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Can't compile springdata examples from sources
{code}
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3.890 s
[INFO] Finished at: 2018-09-19T08:27:16Z
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on
project ignite-examples: Compilation failure: Compilation failure:
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[23,49]
package org.apache.ignite.springdata20.repository does not exist
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[24,56]
package org.apache.ignite.springdata20.repository.config does not exist
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[25,56]
package org.apache.ignite.springdata20.repository.config does not exist
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[34,43]
cannot find symbol
[ERROR] symbol: class IgniteRepository
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[33,2]
cannot find symbol
[ERROR] symbol: class RepositoryConfig
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[25,49]
package org.apache.ignite.springdata20.repository does not exist
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[26,56]
package org.apache.ignite.springdata20.repository.config does not exist
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[27,57]
package org.apache.ignite.springdata20.repository.support does not exist
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[43,2]
cannot find symbol
[ERROR] symbol: class EnableIgniteRepositories
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[56,6]
cannot find symbol
[ERROR] symbol: class Query
[ERROR] location: interface
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[62,13]
cannot find symbol
[ERROR] symbol: method deleteAll()
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[64,60]
cannot find symbol
[ERROR] symbol: method count()
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[101,13]
cannot find symbol
[ERROR] symbol: method
save(java.util.TreeMap)
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[103,49]
cannot find symbol
[ERROR] symbol: method count()
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[111,29]
cannot find symbol
[ERROR] symbol: method findById(long)
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
[..sources..]/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[122,40]
cannot find symbol
[ERROR] symbol: method findAllById(java.util.ArrayList)
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR] -> [Help 1]
[ERROR]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
Stepan Pilschikov created IGNITE-11593: -- Summary: python thin client: insert and select VARBINARY data type through SQL Key: IGNITE-11593 URL: https://issues.apache.org/jira/browse/IGNITE-11593 Project: Ignite Issue Type: Bug Components: thin client Reporter: Stepan Pilschikov varbin data type select is getting not parsed array of integer values Example: https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[ https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-11593: --- Affects Version/s: 2.7 > python thin client: insert and select VARBINARY data type through SQL > - > > Key: IGNITE-11593 > URL: https://issues.apache.org/jira/browse/IGNITE-11593 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Priority: Major > > varbin data type select is getting not parsed array of integer values > Example: > https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11366) python thin client: add python examples in release build
Stepan Pilschikov created IGNITE-11366: -- Summary: python thin client: add python examples in release build Key: IGNITE-11366 URL: https://issues.apache.org/jira/browse/IGNITE-11366 Project: Ignite Issue Type: Improvement Affects Versions: 2.7 Reporter: Stepan Pilschikov Examples directory should be added in release build because they exists in sources and they really help to understand how to work with this client I think they understandable enough for end user Also they have readme.md which is contain link on examples documentation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11366) python thin client: add python examples in release build
[ https://issues.apache.org/jira/browse/IGNITE-11366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Pilschikov updated IGNITE-11366: --- Description: Examples directory should be added in release build because they exists in sources and they really help to understand how to work with this client I think they understandable enough for end user Also they have readme.md which is contain link on examples documentation What should be in release build in /ignite/platforms/python * examples (dir) * pyignite (dir) * requirements (dir) * LICENSE * README.md * setup.py was: Examples directory should be added in release build because they exists in sources and they really help to understand how to work with this client I think they understandable enough for end user Also they have readme.md which is contain link on examples documentation > python thin client: add python examples in release build > > > Key: IGNITE-11366 > URL: https://issues.apache.org/jira/browse/IGNITE-11366 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Priority: Major > > Examples directory should be added in release build because they exists in > sources and they really help to understand how to work with this client > I think they understandable enough for end user > Also they have readme.md which is contain link on examples documentation > > What should be in release build in /ignite/platforms/python > * examples (dir) > * pyignite (dir) > * requirements (dir) > * LICENSE > * README.md > * setup.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11102) ODBC: Uninstall windows driver with different binaries version
Stepan Pilschikov created IGNITE-11102:
--
Summary: ODBC: Uninstall windows driver with different binaries
version
Key: IGNITE-11102
URL: https://issues.apache.org/jira/browse/IGNITE-11102
Project: Ignite
Issue Type: Bug
Components: odbc
Reporter: Stepan Pilschikov
Failed to uninstall ignite dirver with different version of binary file
platforms\cpp\bin\odbc\ignite-odbc-amd64.msi
{code}
cmd> msiexec.exe /i ignite-2.5.0\platforms\cpp\bin\odbc\ignite-odbc-amd64.msi
/n - OK
cmd> msiexec.exe /uninstall
ignite-2.6.0\platforms\cpp\bin\odbc\ignite-odbc-amd64.msi /n - Error: Different
version of product already installed
{code}
It failed between all versions of ignite 2.7 -> 2.6, 2.6 -> 2.5 e.t.c.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11766) cpp: JVM library not found for openjdk 11 on windows
Stepan Pilschikov created IGNITE-11766:
--
Summary: cpp: JVM library not found for openjdk 11 on windows
Key: IGNITE-11766
URL: https://issues.apache.org/jira/browse/IGNITE-11766
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Trying to run compiled ignite.exe from platforms/cpp on windows
{code}
An error occurred: JVM library is not found (did you set JAVA_HOME environment
variable?)
{code}
Think problem that platforms\cpp\jni\os\win\src\utils -> JAVA_DDL =
"\\jre\\bin\\server\\jvm.dll"
searching for jre in jdk dir ectory
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
[ https://issues.apache.org/jira/browse/IGNITE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937837#comment-16937837 ] Stepan Pilschikov commented on IGNITE-11008: [~kcheng.mvp] Thanks for contribution. I definitely a wrong person to help in PR process or TC things. Better to ask [~Mmuzaf] or Ignite dev list > JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH > -- > > Key: IGNITE-11008 > URL: https://issues.apache.org/jira/browse/IGNITE-11008 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: kcheng.mvp >Priority: Minor > Fix For: 2.8 > > > Found redundant spaces in > org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns > "IS_GENERATEDCOLUMN " > "BUFFER_LENGTH " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12673) ML examples logging
Stepan Pilschikov created IGNITE-12673: -- Summary: ML examples logging Key: IGNITE-12673 URL: https://issues.apache.org/jira/browse/IGNITE-12673 Project: Ignite Issue Type: Bug Components: examples, ml Affects Versions: 2.8 Reporter: Stepan Pilschikov Compile of several minor fixes for ML examples: 1. In TutorialStepByStepExample we running 17 examples First 12 logging is pretty good and looks like "Tutorial step N: name" -> model -> accuracy -> "Tutorial step N: completed" But then starting with 13 this pattern is kind of broke, step start and step completion is missing 2. Step_8_CV_with_Param_Grid_and_metrics_and_pipeline is haven't step completion log 3. Complete log for Step_9_Scaling_With_Stacking looks like 'Tutorial step 5 (scaling) example completed' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
Stepan Pilschikov created IGNITE-12573:
--
Summary: Copy ML dependencies to other standalone pom files in
examples
Key: IGNITE-12573
URL: https://issues.apache.org/jira/browse/IGNITE-12573
Project: Ignite
Issue Type: Task
Components: examples
Affects Versions: 2.8
Reporter: Stepan Pilschikov
2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
{color:#9876aa}<{color}{color:#e8bf6a}dependency{color}{color:#9876aa}>
{color}{color:#9876aa}
<{color}{color:#e8bf6a}groupId{color}{color:#9876aa}>{color}org.apache.ignite{color:#9876aa}
{color}{color:#9876aa}
<{color}{color:#e8bf6a}artifactId{color}{color:#9876aa}>{color}ignite-ml-tensorflow-model-parser{color:#9876aa}
{color}{color:#9876aa}
<{color}{color:#e8bf6a}version{color}{color:#9876aa}>{color}${project.version}{color:#9876aa}
{color}{color:#9876aa}{color}
{color:#9876aa}<{color}{color:#e8bf6a}dependency{color}{color:#9876aa}>
{color}{color:#9876aa}
<{color}{color:#e8bf6a}groupId{color}{color:#9876aa}>{color}org.apache.ignite{color:#9876aa}
{color}{color:#9876aa}
<{color}{color:#e8bf6a}artifactId{color}{color:#9876aa}>{color}ignite-ml-h2o-model-parser{color:#9876aa}
{color}{color:#9876aa}
<{color}{color:#e8bf6a}version{color}{color:#9876aa}>{color}${project.version}{color:#9876aa}
{color}{color:#9876aa}{color}
Need to copy this libraries from original pom.xml because examples in released
build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12587) ML examples failed on start
[
https://issues.apache.org/jira/browse/IGNITE-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-12587:
---
Description:
New release build comes with lost data sets for ML 2.8
Steps:
- Try to run any ML examples used MLSandboxDatasets
(org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample
for examples)
Actual:
- FileNotFoundException
{code}
Exception in thread "main" java.io.FileNotFoundException:
modules/ml/src/main/resources/datasets/boston_housing_dataset.txt
at
org.apache.ignite.ml.util.SandboxMLCache.fillCacheWith(SandboxMLCache.java:119)
at
org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample.main(TrainingWithCustomPreprocessorsExample.java:62)
{code}
Release build -
https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8
was:
New release build comes with lost data sets for ML 2.8
Steps:
- Try to run any ML examples used MLSandboxDatasets
(org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample
for examples)
Actual:
- FileNotFoundException
{code}
Exception in thread "main" java.io.FileNotFoundException:
modules/ml/src/main/resources/datasets/boston_housing_dataset.txt
at
org.apache.ignite.ml.util.SandboxMLCache.fillCacheWith(SandboxMLCache.java:119)
at
org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample.main(TrainingWithCustomPreprocessorsExample.java:62)
{code}
> ML examples failed on start
> ---
>
> Key: IGNITE-12587
> URL: https://issues.apache.org/jira/browse/IGNITE-12587
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Affects Versions: 2.8
> Environment: Java 8
> Linux/Win
>Reporter: Stepan Pilschikov
>Priority: Blocker
>
> New release build comes with lost data sets for ML 2.8
> Steps:
> - Try to run any ML examples used MLSandboxDatasets
> (org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample
> for examples)
> Actual:
> - FileNotFoundException
> {code}
> Exception in thread "main" java.io.FileNotFoundException:
> modules/ml/src/main/resources/datasets/boston_housing_dataset.txt
> at
> org.apache.ignite.ml.util.SandboxMLCache.fillCacheWith(SandboxMLCache.java:119)
> at
> org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample.main(TrainingWithCustomPreprocessorsExample.java:62)
> {code}
> Release build -
> https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12588) Failed to run MLeap or Spark examples
Stepan Pilschikov created IGNITE-12588:
--
Summary: Failed to run MLeap or Spark examples
Key: IGNITE-12588
URL: https://issues.apache.org/jira/browse/IGNITE-12588
Project: Ignite
Issue Type: Bug
Components: ml, spark
Affects Versions: 2.8
Environment: Java 8
Ubuntu/Win 10
Reporter: Stepan Pilschikov
New release build comes with missed class
org.apache.ignite.ml.mleap.MLeapModelParser
Now i can't build any spark examples
Steps:
- Try to mvn clean package -P scala
Actual:
-
{code:java}
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[34,34]
package org.apache.ignite.ml.mleap does not exist
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,26]
cannot find symbol
symbol: class MLeapModelParser
location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,56]
cannot find symbol
symbol: class MLeapModelParser
location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12587) ML examples failed on start
Stepan Pilschikov created IGNITE-12587:
--
Summary: ML examples failed on start
Key: IGNITE-12587
URL: https://issues.apache.org/jira/browse/IGNITE-12587
Project: Ignite
Issue Type: Bug
Components: ml
Affects Versions: 2.8
Environment: Java 8
Linux/Win
Reporter: Stepan Pilschikov
New release build comes with lost data sets for ML 2.8
Steps:
- Try to run any ML examples used MLSandboxDatasets
(org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample
for examples)
Actual:
- FileNotFoundException
{code}
Exception in thread "main" java.io.FileNotFoundException:
modules/ml/src/main/resources/datasets/boston_housing_dataset.txt
at
org.apache.ignite.ml.util.SandboxMLCache.fillCacheWith(SandboxMLCache.java:119)
at
org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample.main(TrainingWithCustomPreprocessorsExample.java:62)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12588) Failed to run MLeap or Spark examples
[
https://issues.apache.org/jira/browse/IGNITE-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-12588:
---
Description:
New release build comes with missed class
org.apache.ignite.ml.mleap.MLeapModelParser
Now i can't build any spark examples
Steps:
- Try to mvn clean package -P scala
Actual:
-
{code:java}
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[34,34]
package org.apache.ignite.ml.mleap does not exist
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,26]
cannot find symbol
symbol: class MLeapModelParser
location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,56]
cannot find symbol
symbol: class MLeapModelParser
location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
{code}
Release build -
https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8
was:
New release build comes with missed class
org.apache.ignite.ml.mleap.MLeapModelParser
Now i can't build any spark examples
Steps:
- Try to mvn clean package -P scala
Actual:
-
{code:java}
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[34,34]
package org.apache.ignite.ml.mleap does not exist
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,26]
cannot find symbol
symbol: class MLeapModelParser
location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
[ERROR]
/apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,56]
cannot find symbol
symbol: class MLeapModelParser
location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
{code}
> Failed to run MLeap or Spark examples
> -
>
> Key: IGNITE-12588
> URL: https://issues.apache.org/jira/browse/IGNITE-12588
> Project: Ignite
> Issue Type: Bug
> Components: ml, spark
>Affects Versions: 2.8
> Environment: Java 8
> Ubuntu/Win 10
>Reporter: Stepan Pilschikov
>Priority: Blocker
>
> New release build comes with missed class
> org.apache.ignite.ml.mleap.MLeapModelParser
> Now i can't build any spark examples
> Steps:
> - Try to mvn clean package -P scala
> Actual:
> -
> {code:java}
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[34,34]
> package org.apache.ignite.ml.mleap does not exist
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,26]
> cannot find symbol
> symbol: class MLeapModelParser
> location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,56]
> cannot find symbol
> symbol: class MLeapModelParser
> location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
> {code}
>
> Release build -
> https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12588) Failed to run MLeap or Spark examples
[
https://issues.apache.org/jira/browse/IGNITE-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-12588:
---
Environment:
Java 8
Ubuntu/Win 10
Release build -
https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8
was:
Java 8
Ubuntu/Win 10
> Failed to run MLeap or Spark examples
> -
>
> Key: IGNITE-12588
> URL: https://issues.apache.org/jira/browse/IGNITE-12588
> Project: Ignite
> Issue Type: Bug
> Components: ml, spark
>Affects Versions: 2.8
> Environment: Java 8
> Ubuntu/Win 10
> Release build -
> https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8
>Reporter: Stepan Pilschikov
>Priority: Blocker
>
> New release build comes with missed class
> org.apache.ignite.ml.mleap.MLeapModelParser
> Now i can't build any spark examples
> Steps:
> - Try to mvn clean package -P scala
> Actual:
> -
> {code:java}
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[34,34]
> package org.apache.ignite.ml.mleap does not exist
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,26]
> cannot find symbol
> symbol: class MLeapModelParser
> location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,56]
> cannot find symbol
> symbol: class MLeapModelParser
> location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12588) Failed to run MLeap or Spark examples
[
https://issues.apache.org/jira/browse/IGNITE-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-12588:
---
Environment:
Java 8
Ubuntu/Win 10
was:
Java 8
Ubuntu/Win 10
Release build -
https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8
> Failed to run MLeap or Spark examples
> -
>
> Key: IGNITE-12588
> URL: https://issues.apache.org/jira/browse/IGNITE-12588
> Project: Ignite
> Issue Type: Bug
> Components: ml, spark
>Affects Versions: 2.8
> Environment: Java 8
> Ubuntu/Win 10
>Reporter: Stepan Pilschikov
>Priority: Blocker
>
> New release build comes with missed class
> org.apache.ignite.ml.mleap.MLeapModelParser
> Now i can't build any spark examples
> Steps:
> - Try to mvn clean package -P scala
> Actual:
> -
> {code:java}
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[34,34]
> package org.apache.ignite.ml.mleap does not exist
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,26]
> cannot find symbol
> symbol: class MLeapModelParser
> location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
> [ERROR]
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,56]
> cannot find symbol
> symbol: class MLeapModelParser
> location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
