[jira] [Created] (IGNITE-13696) [ML] Tutorial examples fails
Stepan Pilschikov created IGNITE-13696:
--
Summary: [ML] Tutorial examples fails
Key: IGNITE-13696
URL: https://issues.apache.org/jira/browse/IGNITE-13696
Project: Ignite
Issue Type: Bug
Components: examples, ml
Affects Versions: 2.9
Reporter: Stepan Pilschikov
Trying to run Tutorial examples from repository or from binary release and meet
error results. Looks like a bug
org.apache.ignite.examples.ml.tutorial.Step_1_Read_and_Learn (all other
tutorials have same issue)
{code}
>>> Trained model: if (x0 > 2.5000) then if (x1 > 2.5000) then if (x2 > 0.5000)
>>> then if (x1 > 4.5000) then return 0. else if (x2 > 1.5000) then return
>>> 0. else return 0. else return 0. else if (x2 > 0.5000) then if
>>> (x2 > 3.5000) then if (x1 > 0.5000) then return 0. else return 0.
>>> else if (x2 > 1.5000) then return 0. else return 1. else if (x1 >
>>> 0.5000) then if (x1 > 1.5000) then return 0. else return 0. else
>>> return 0. else if (x2 > 0.5000) then if (x1 > 0.5000) then if (x1 >
>>> 1.5000) then if (x1 > 2.5000) then return 1. else return 1. else if
>>> (x2 > 3.5000) then return 0. else return 1. else if (x2 > 1.5000)
>>> then if (x0 > 1.5000) then return 1. else return 1. else if (x0 >
>>> 1.5000) then return 1. else return 1. else if (x0 > 1.5000) then if
>>> (x1 > 2.5000) then return 1. else if (x1 > 1.5000) then return 0.
>>> else return 0. else if (x1 > 0.5000) then if (x1 > 1.5000) then return
>>> 1. else return 1. else return 1.
>>> Accuracy 0.7117737003058104
>>> Test Error 0.28822629969418956
>>> Tutorial step 1 (read and learn) example completed.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13675) Devnotes in C++ platforms pointed that windows cmake not yet supported
Stepan Pilschikov created IGNITE-13675: -- Summary: Devnotes in C++ platforms pointed that windows cmake not yet supported Key: IGNITE-13675 URL: https://issues.apache.org/jira/browse/IGNITE-13675 Project: Ignite Issue Type: Bug Components: documentation, platforms Reporter: Stepan Pilschikov Currently in devnotes written that windows cmake not yet supported which is wrong https://github.com/apache/ignite/blob/b986cf6f2250858b92e4eda52f9269077659229c/modules/platforms/cpp/DEVNOTES.txt#L11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13661) Example for transactions in thin clients
Stepan Pilschikov created IGNITE-13661: -- Summary: Example for transactions in thin clients Key: IGNITE-13661 URL: https://issues.apache.org/jira/browse/IGNITE-13661 Project: Ignite Issue Type: Wish Components: examples, thin client Reporter: Stepan Pilschikov We have no examples for many main features in thin clients Not so long time ago was added transactions in Dotnet It's better to add appropriate examples for these features -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12846) Docs: ml package org.apache.ignite.ml.knn.utils.indices have no description in binary release
Stepan Pilschikov created IGNITE-12846:
--
Summary: Docs: ml package org.apache.ignite.ml.knn.utils.indices
have no description in binary release
Key: IGNITE-12846
URL: https://issues.apache.org/jira/browse/IGNITE-12846
Project: Ignite
Issue Type: Bug
Components: documentation
Affects Versions: 2.8
Reporter: Stepan Pilschikov
apache-ignite-2.8.0-bin/docs/javadoc/overview-summary.html does not contain
description block for org.apache.ignite.ml.knn.utils.indices
Actual:
{code}
org.apache.ignite.ml.knn.utils.indices
{code}
Expected:
{code}
org.apache.ignite.ml.knn.utils.indices
[Some description]
{code}
--
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-12658) [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1 node
Stepan Pilschikov created IGNITE-12658:
--
Summary: [ML][Examples] TutorialStepByStepExample failed on
cluster with more then 1 node
Key: IGNITE-12658
URL: https://issues.apache.org/jira/browse/IGNITE-12658
Project: Ignite
Issue Type: Bug
Components: examples, ml
Affects Versions: 2.8
Environment: Ubuntu/Win
Java 8
Reporter: Stepan Pilschikov
Steps to reproduce:
1. Run Ignite node with org.apache.ignite.examples.ExampleNodeStartup (1 node
will be enough)
2. Run org.apache.ignite.examples.ml.tutorial.TutorialStepByStepExample
Actual:
On Step_8_CV_with_Param_Grid_and_metrics starting to throw a lot of exceptions
{code:java}
Train with p: 2 and maxDeep: 1
>>> Trained model: if (x1 > 0.4368) then return 1. else return 0.
>>> Accuracy 0.7679083094555874
>>> Test Error 0.2320916905444126
>>> Tutorial step 8 (cross-validation) example completed.
[13:25:40] Ignite node stopped OK [uptime=00:00:17.453]
>>> Tutorial step 8 (cross-validation with param grid) example started.
[13:25:40]__
[13:25:40] / _/ ___/ |/ / _/_ __/ __/
[13:25:40] _/ // (7 7// / / / / _/
[13:25:40] /___/\___/_/|_/___/ /_/ /___/
[13:25:40]
[13:25:40] ver. 2.8.0#20200130-sha1:f478aa56
[13:25:40] 2020 Copyright(C) Apache Software Foundation
[13:25:40]
[13:25:40] Ignite documentation: http://ignite.apache.org
[13:25:40]
[13:25:40] Quiet mode.
[13:25:40] ^-- Logging to file
'/opt/buildagent/work/d501ae8146bd8253/i2test/var/suite-examples/app-ignite/work/log/ignite-e156b2f2.log'
[13:25:40] ^-- Logging by 'Log4JLogger [quiet=true, config=null]'
[13:25:40] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[13:25:40]
[13:25:40] OS: Linux 4.15.0-65-generic amd64
[13:25:40] VM information: Java(TM) SE Runtime Environment 1.8.0_221-b11 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 25.221-b11
[13:25:40] Please set system property '-Djava.net.preferIPv4Stack=true' to
avoid possible problems in mixed environments.
[13:25:40] Configured plugins:
[13:25:40] ^-- ml-inference-plugin 1.0.0
[13:25:40] ^-- null
[13:25:40]
[13:25:40] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
[tryStop=false, timeout=0, super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT
[13:25:40] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
message queues growth on sender and receiver sides.
[13:25:40] Security status [authentication=off, tls/ssl=off]
[13:25:41] Performance suggestions for grid (fix if possible)
[13:25:41] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[13:25:41] ^-- Disable grid events (remove 'includeEventTypes' from
configuration)
[13:25:41] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[13:25:41] ^-- Set max direct memory size if getting 'OOME: Direct buffer
memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
[13:25:41] ^-- Disable processing of calls to System.gc() (add
'-XX:+DisableExplicitGC' to JVM options)
[13:25:41] Refer to this page for more performance suggestions:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[13:25:41]
[13:25:41] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[13:25:41] Data Regions Configured:
[13:25:41] ^-- Default_Region [initSize=500.0 MiB, maxSize=18.9 GiB,
persistence=false, lazyMemoryAllocation=true]
[13:25:41]
[13:25:41] Ignite node started OK (id=e156b2f2)
[13:25:41] Topology snapshot [ver=20, locNode=e156b2f2, servers=2, clients=0,
state=ACTIVE, CPUs=5, offheap=38.0GB, heap=3.0GB]
[13:25:41] ^-- Baseline [id=0, size=2, online=2, offline=0]
[2020-02-11 13:25:42,428][ERROR][sys-#593][GridTaskWorker] Failed to obtain
remote job result policy for result from ComputeTask.result(..) method (will
fail the whole task): GridJobResultImpl [job=C2
[c=o.a.i.ml.dataset.impl.cache.util.ComputeUtils$DeployableCallable@30e27659],
sib=GridJobSiblingImpl [sesId=f9aced33071-e156b2f2-d116-4389-bd43-8536dc59,
jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
nodeId=f1135598-73c8-4324-92af-45c110a6a637, isJobDone=false],
jobCtx=GridJobContextImpl
[jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59, timeoutObj=null,
attrs=HashMap {}], node=TcpDiscoveryNode
[id=f1135598-73c8-4324-92af-45c110a6a637,
consistentId=127.0.0.1,192.168.112.2:47500, addrs=ArrayList [127.0.0.1,
192.168.112.2], sockAddrs=HashSet [/127.0.0.1:47500,
87bf29244900/192.168.112.2:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1581416741501, loc=false, ver=2.8.0#20200130-sha1:f478aa56,
isClient=false], ex=class o.a.i.IgniteException: Failed to deserialize object
[jira] [Created] (IGNITE-12657) ML examples EvaluatorExample and MultipleMetricsExample looks the same
Stepan Pilschikov created IGNITE-12657: -- Summary: ML examples EvaluatorExample and MultipleMetricsExample looks the same Key: IGNITE-12657 URL: https://issues.apache.org/jira/browse/IGNITE-12657 Project: Ignite Issue Type: Bug Components: examples, ml Affects Versions: 2.8 Reporter: Stepan Pilschikov Examples org.apache.ignite.examples.ml.selection.scoring.EvaluatorExample and org.apache.ignite.examples.ml.selection.scoring.MultipleMetricsExample Looks exactly the same I think MultipleMetricsExample is wrong because description told about using KNNClassificationTrainer but actually used SVMLinearClassificationTrainer -- 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] [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] [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] [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] [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] [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-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] [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] [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] [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] [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] [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] [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] [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-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-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] [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] [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-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-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] [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] [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-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] [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-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] [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] [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] [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-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-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)
