[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)
Re: ML examples EvaluatorExample and MultipleMetricsExample looks the same
filled ticket - https://issues.apache.org/jira/browse/IGNITE-12673 чт, 13 февр. 2020 г. в 13:46, Alexey Zinoviev : > I suppose one ticket is enough, collect where all your nites and thoughts > > чт, 13 февр. 2020 г., 12:12 Stepan Pilschikov : > >> And one (three) more thing >> >> 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 >> >> Also want to admin that >> Step_8_CV_with_Param_Grid_and_metrics_and_pipeline is haven't step >> completion log >> And complete log for Step_9_Scaling_With_Stacking looks like 'Tutorial >> step 5 (scaling) example completed' >> >> i don't know, should i made some ticket? One ticket for each problem or >> one for all or you can fix it in one commit? because fixes quite small >> >> ср, 12 февр. 2020 г. в 16:31, Alexey Zinoviev : >> >>> Yes, you are right. Missed resources, I'll remove them tomorrow >>> >>> ср, 12 февр. 2020 г. в 16:23, Stepan Pilschikov < >>> pilshchikov@gmail.com>: >>> >>>> With mnist_tf_model in same directory >>>> All others looks right >>>> >>>> ср, 12 февр. 2020 г. в 16:21, Stepan Pilschikov < >>>> pilshchikov@gmail.com>: >>>> >>>>> Hmm, interesting, got it >>>>> Also found >>>>> apache-ignite-2.8.0-bin/examples/src/main/resources/models/mleap >>>>> I think its also should be removed then >>>>> >>>>> ср, 12 февр. 2020 г. в 16:11, Alexey Zinoviev >>>> >: >>>>> >>>>>> Please, have a look to the next ticket >>>>>> https://issues.apache.org/jira/browse/IGNITE-12659 >>>>>> Also tensorflow packages are blockers for IGFS deprecation and >>>>>> removal. >>>>>> >>>>>> ср, 12 февр. 2020 г. в 15:58, Alexey Zinoviev >>>>> >: >>>>>> >>>>>>> They are not lost, they are removed from release branch due to a lot >>>>>>> of bugs, cves and so on, don't worry about that. >>>>>>> >>>>>>> ср, 12 февр. 2020 г., 14:31 Stepan Pilschikov < >>>>>>> pilshchikov@gmail.com>: >>>>>>> >>>>>>>> Also lost ignite-ml-tensorflow-model-parser and ignite-tensorflow >>>>>>>> in libs/optional >>>>>>>> >>>>>>>> >>>>>>>> ср, 12 февр. 2020 г. в 14:25, Stepan Pilschikov < >>>>>>>> pilshchikov@gmail.com>: >>>>>>>> >>>>>>>>> But now have new problems >>>>>>>>> I build ignite-2.8 build on TC >>>>>>>>> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/5043672 >>>>>>>>> Previous >>>>>>>>> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/4988324 >>>>>>>>> >>>>>>>>> New build much lighter >>>>>>>>> Previous: 5.7 Gb >>>>>>>>> Current: 4.3 Gb >>>>>>>>> And its looks like something missing, on a first look i notice >>>>>>>>> that /libs/optional/ignite-ml-mleap-model-parser lost completely >>>>>>>>> >>>>>>>>> >>>>>>>>> ср, 12 февр. 2020 г. в 14:18, Stepan Pilschikov < >>>>>>>>> pilshchikov@gmail.com>: >>>>>>>>> >>>>>>>>>> Thanks for fix >>>>>>>>>> Duplicated examples deleted and tutorial works on real (1+ node) >>>>>>>>>> cluster now >>>>>>>>>> I think ticket can be closed, have no power here >>>>>>>>>> >>>>>>>>>> вт, 11 февр. 2020 г. в 20:44, Alexey Zinoviev < >>>>>>>>>> zaleslaw@gmail.com>: >>>>>>>>>> >>>>>>>>>>> Sorry, for that, but I it touches ML-related stuff only and >>>>
[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)
Re: ML examples EvaluatorExample and MultipleMetricsExample looks the same
And one (three) more thing 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 Also want to admin that Step_8_CV_with_Param_Grid_and_metrics_and_pipeline is haven't step completion log And complete log for Step_9_Scaling_With_Stacking looks like 'Tutorial step 5 (scaling) example completed' i don't know, should i made some ticket? One ticket for each problem or one for all or you can fix it in one commit? because fixes quite small ср, 12 февр. 2020 г. в 16:31, Alexey Zinoviev : > Yes, you are right. Missed resources, I'll remove them tomorrow > > ср, 12 февр. 2020 г. в 16:23, Stepan Pilschikov >: > >> With mnist_tf_model in same directory >> All others looks right >> >> ср, 12 февр. 2020 г. в 16:21, Stepan Pilschikov < >> pilshchikov@gmail.com>: >> >>> Hmm, interesting, got it >>> Also found >>> apache-ignite-2.8.0-bin/examples/src/main/resources/models/mleap >>> I think its also should be removed then >>> >>> ср, 12 февр. 2020 г. в 16:11, Alexey Zinoviev : >>> >>>> Please, have a look to the next ticket >>>> https://issues.apache.org/jira/browse/IGNITE-12659 >>>> Also tensorflow packages are blockers for IGFS deprecation and removal. >>>> >>>> ср, 12 февр. 2020 г. в 15:58, Alexey Zinoviev : >>>> >>>>> They are not lost, they are removed from release branch due to a lot >>>>> of bugs, cves and so on, don't worry about that. >>>>> >>>>> ср, 12 февр. 2020 г., 14:31 Stepan Pilschikov < >>>>> pilshchikov@gmail.com>: >>>>> >>>>>> Also lost ignite-ml-tensorflow-model-parser and ignite-tensorflow in >>>>>> libs/optional >>>>>> >>>>>> >>>>>> ср, 12 февр. 2020 г. в 14:25, Stepan Pilschikov < >>>>>> pilshchikov@gmail.com>: >>>>>> >>>>>>> But now have new problems >>>>>>> I build ignite-2.8 build on TC >>>>>>> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/5043672 >>>>>>> Previous >>>>>>> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/4988324 >>>>>>> >>>>>>> New build much lighter >>>>>>> Previous: 5.7 Gb >>>>>>> Current: 4.3 Gb >>>>>>> And its looks like something missing, on a first look i notice that >>>>>>> /libs/optional/ignite-ml-mleap-model-parser lost completely >>>>>>> >>>>>>> >>>>>>> ср, 12 февр. 2020 г. в 14:18, Stepan Pilschikov < >>>>>>> pilshchikov@gmail.com>: >>>>>>> >>>>>>>> Thanks for fix >>>>>>>> Duplicated examples deleted and tutorial works on real (1+ node) >>>>>>>> cluster now >>>>>>>> I think ticket can be closed, have no power here >>>>>>>> >>>>>>>> вт, 11 февр. 2020 г. в 20:44, Alexey Zinoviev < >>>>>>>> zaleslaw@gmail.com>: >>>>>>>> >>>>>>>>> Sorry, for that, but I it touches ML-related stuff only and >>>>>>>>> doesn't influence on any another module. >>>>>>>>> I merged them to master later (currently, I have a 4 tickets in a >>>>>>>>> queue). >>>>>>>>> >>>>>>>>> Will keep in mind for the next fixes >>>>>>>>> >>>>>>>>> вт, 11 февр. 2020 г. в 18:58, Maxim Muzafarov : >>>>>>>>> >>>>>>>>>> Alexey, >>>>>>>>>> >>>>>>>>>> Is the approach when we cherry-pick fixes to the 2.8 only after >>>>>>>>>> all >>>>>>>>>> fixes have verified in the master branch better? I just want to be >>>>>>>>>> sure the release branch to be stable enough. >>>>>>>>>> >>>>>>>>>> On Tue, 11 Feb 2020 at 18:36, Alexey Zinoviev < >>>>>>>>>> zaleslaw@gmail.com> wrote: >>>>>>>>>> > >>>>>>>>>> > Fixed both in release branch 2.8. Please verify and let me know >>>>>>>>>> > >>>>>>>>>> > вт, 11 февр. 2020 г. в 14:58, Stepan Pilschikov < >>>>>>>>>> pilshchikov@gmail.com>: >>>>>>>>>> > >>>>>>>>>> > > And one more >>>>>>>>>> > > https://issues.apache.org/jira/browse/IGNITE-12658 - >>>>>>>>>> > > TutorialStepByStepExample example failed if cluster with more >>>>>>>>>> then 1 node >>>>>>>>>> > > >>>>>>>>>> > > вт, 11 февр. 2020 г. в 11:52, Alexey Zinoviev < >>>>>>>>>> zaleslaw@gmail.com>: >>>>>>>>>> > > >>>>>>>>>> > >> Great, thank you so much, will fix next week >>>>>>>>>> > >> >>>>>>>>>> > >> вт, 11 февр. 2020 г., 11:39 Stepan Pilschikov < >>>>>>>>>> pilshchikov@gmail.com >>>>>>>>>> > >> >: >>>>>>>>>> > >> >>>>>>>>>> > >>> Hi, Alexey, could you please looking on one small accident >>>>>>>>>> happen in ML >>>>>>>>>> > >>> examples: >>>>>>>>>> > >>> https://issues.apache.org/jira/browse/IGNITE-12657 - 2 >>>>>>>>>> examples exactly >>>>>>>>>> > >>> the same. >>>>>>>>>> > >>> >>>>>>>>>> > >>> Also want to say that all previous examples have one common >>>>>>>>>> approach for >>>>>>>>>> > >>> meaningful output, like ">>> Something important". In this >>>>>>>>>> two i seeing >>>>>>>>>> > >>> different one, could you please also pay attention to it. >>>>>>>>>> > >>> >>>>>>>>>> > >>> Best regards, >>>>>>>>>> > >>> Stepan >>>>>>>>>> > >>> >>>>>>>>>> > >> >>>>>>>>>> >>>>>>>>>
Re: ML examples EvaluatorExample and MultipleMetricsExample looks the same
With mnist_tf_model in same directory All others looks right ср, 12 февр. 2020 г. в 16:21, Stepan Pilschikov : > Hmm, interesting, got it > Also found apache-ignite-2.8.0-bin/examples/src/main/resources/models/mleap > I think its also should be removed then > > ср, 12 февр. 2020 г. в 16:11, Alexey Zinoviev : > >> Please, have a look to the next ticket >> https://issues.apache.org/jira/browse/IGNITE-12659 >> Also tensorflow packages are blockers for IGFS deprecation and removal. >> >> ср, 12 февр. 2020 г. в 15:58, Alexey Zinoviev : >> >>> They are not lost, they are removed from release branch due to a lot of >>> bugs, cves and so on, don't worry about that. >>> >>> ср, 12 февр. 2020 г., 14:31 Stepan Pilschikov >> >: >>> >>>> Also lost ignite-ml-tensorflow-model-parser and ignite-tensorflow in >>>> libs/optional >>>> >>>> >>>> ср, 12 февр. 2020 г. в 14:25, Stepan Pilschikov < >>>> pilshchikov@gmail.com>: >>>> >>>>> But now have new problems >>>>> I build ignite-2.8 build on TC >>>>> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/5043672 >>>>> Previous >>>>> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/4988324 >>>>> >>>>> New build much lighter >>>>> Previous: 5.7 Gb >>>>> Current: 4.3 Gb >>>>> And its looks like something missing, on a first look i notice that >>>>> /libs/optional/ignite-ml-mleap-model-parser lost completely >>>>> >>>>> >>>>> ср, 12 февр. 2020 г. в 14:18, Stepan Pilschikov < >>>>> pilshchikov@gmail.com>: >>>>> >>>>>> Thanks for fix >>>>>> Duplicated examples deleted and tutorial works on real (1+ node) >>>>>> cluster now >>>>>> I think ticket can be closed, have no power here >>>>>> >>>>>> вт, 11 февр. 2020 г. в 20:44, Alexey Zinoviev >>>>> >: >>>>>> >>>>>>> Sorry, for that, but I it touches ML-related stuff only and doesn't >>>>>>> influence on any another module. >>>>>>> I merged them to master later (currently, I have a 4 tickets in a >>>>>>> queue). >>>>>>> >>>>>>> Will keep in mind for the next fixes >>>>>>> >>>>>>> вт, 11 февр. 2020 г. в 18:58, Maxim Muzafarov : >>>>>>> >>>>>>>> Alexey, >>>>>>>> >>>>>>>> Is the approach when we cherry-pick fixes to the 2.8 only after all >>>>>>>> fixes have verified in the master branch better? I just want to be >>>>>>>> sure the release branch to be stable enough. >>>>>>>> >>>>>>>> On Tue, 11 Feb 2020 at 18:36, Alexey Zinoviev < >>>>>>>> zaleslaw@gmail.com> wrote: >>>>>>>> > >>>>>>>> > Fixed both in release branch 2.8. Please verify and let me know >>>>>>>> > >>>>>>>> > вт, 11 февр. 2020 г. в 14:58, Stepan Pilschikov < >>>>>>>> pilshchikov@gmail.com>: >>>>>>>> > >>>>>>>> > > And one more >>>>>>>> > > https://issues.apache.org/jira/browse/IGNITE-12658 - >>>>>>>> > > TutorialStepByStepExample example failed if cluster with more >>>>>>>> then 1 node >>>>>>>> > > >>>>>>>> > > вт, 11 февр. 2020 г. в 11:52, Alexey Zinoviev < >>>>>>>> zaleslaw@gmail.com>: >>>>>>>> > > >>>>>>>> > >> Great, thank you so much, will fix next week >>>>>>>> > >> >>>>>>>> > >> вт, 11 февр. 2020 г., 11:39 Stepan Pilschikov < >>>>>>>> pilshchikov@gmail.com >>>>>>>> > >> >: >>>>>>>> > >> >>>>>>>> > >>> Hi, Alexey, could you please looking on one small accident >>>>>>>> happen in ML >>>>>>>> > >>> examples: >>>>>>>> > >>> https://issues.apache.org/jira/browse/IGNITE-12657 - 2 >>>>>>>> examples exactly >>>>>>>> > >>> the same. >>>>>>>> > >>> >>>>>>>> > >>> Also want to say that all previous examples have one common >>>>>>>> approach for >>>>>>>> > >>> meaningful output, like ">>> Something important". In this >>>>>>>> two i seeing >>>>>>>> > >>> different one, could you please also pay attention to it. >>>>>>>> > >>> >>>>>>>> > >>> Best regards, >>>>>>>> > >>> Stepan >>>>>>>> > >>> >>>>>>>> > >> >>>>>>>> >>>>>>>
Re: ML examples EvaluatorExample and MultipleMetricsExample looks the same
Hmm, interesting, got it Also found apache-ignite-2.8.0-bin/examples/src/main/resources/models/mleap I think its also should be removed then ср, 12 февр. 2020 г. в 16:11, Alexey Zinoviev : > Please, have a look to the next ticket > https://issues.apache.org/jira/browse/IGNITE-12659 > Also tensorflow packages are blockers for IGFS deprecation and removal. > > ср, 12 февр. 2020 г. в 15:58, Alexey Zinoviev : > >> They are not lost, they are removed from release branch due to a lot of >> bugs, cves and so on, don't worry about that. >> >> ср, 12 февр. 2020 г., 14:31 Stepan Pilschikov > >: >> >>> Also lost ignite-ml-tensorflow-model-parser and ignite-tensorflow in >>> libs/optional >>> >>> >>> ср, 12 февр. 2020 г. в 14:25, Stepan Pilschikov < >>> pilshchikov@gmail.com>: >>> >>>> But now have new problems >>>> I build ignite-2.8 build on TC >>>> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/5043672 >>>> Previous >>>> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/4988324 >>>> >>>> New build much lighter >>>> Previous: 5.7 Gb >>>> Current: 4.3 Gb >>>> And its looks like something missing, on a first look i notice that >>>> /libs/optional/ignite-ml-mleap-model-parser lost completely >>>> >>>> >>>> ср, 12 февр. 2020 г. в 14:18, Stepan Pilschikov < >>>> pilshchikov@gmail.com>: >>>> >>>>> Thanks for fix >>>>> Duplicated examples deleted and tutorial works on real (1+ node) >>>>> cluster now >>>>> I think ticket can be closed, have no power here >>>>> >>>>> вт, 11 февр. 2020 г. в 20:44, Alexey Zinoviev >>>> >: >>>>> >>>>>> Sorry, for that, but I it touches ML-related stuff only and doesn't >>>>>> influence on any another module. >>>>>> I merged them to master later (currently, I have a 4 tickets in a >>>>>> queue). >>>>>> >>>>>> Will keep in mind for the next fixes >>>>>> >>>>>> вт, 11 февр. 2020 г. в 18:58, Maxim Muzafarov : >>>>>> >>>>>>> Alexey, >>>>>>> >>>>>>> Is the approach when we cherry-pick fixes to the 2.8 only after all >>>>>>> fixes have verified in the master branch better? I just want to be >>>>>>> sure the release branch to be stable enough. >>>>>>> >>>>>>> On Tue, 11 Feb 2020 at 18:36, Alexey Zinoviev < >>>>>>> zaleslaw@gmail.com> wrote: >>>>>>> > >>>>>>> > Fixed both in release branch 2.8. Please verify and let me know >>>>>>> > >>>>>>> > вт, 11 февр. 2020 г. в 14:58, Stepan Pilschikov < >>>>>>> pilshchikov@gmail.com>: >>>>>>> > >>>>>>> > > And one more >>>>>>> > > https://issues.apache.org/jira/browse/IGNITE-12658 - >>>>>>> > > TutorialStepByStepExample example failed if cluster with more >>>>>>> then 1 node >>>>>>> > > >>>>>>> > > вт, 11 февр. 2020 г. в 11:52, Alexey Zinoviev < >>>>>>> zaleslaw@gmail.com>: >>>>>>> > > >>>>>>> > >> Great, thank you so much, will fix next week >>>>>>> > >> >>>>>>> > >> вт, 11 февр. 2020 г., 11:39 Stepan Pilschikov < >>>>>>> pilshchikov@gmail.com >>>>>>> > >> >: >>>>>>> > >> >>>>>>> > >>> Hi, Alexey, could you please looking on one small accident >>>>>>> happen in ML >>>>>>> > >>> examples: >>>>>>> > >>> https://issues.apache.org/jira/browse/IGNITE-12657 - 2 >>>>>>> examples exactly >>>>>>> > >>> the same. >>>>>>> > >>> >>>>>>> > >>> Also want to say that all previous examples have one common >>>>>>> approach for >>>>>>> > >>> meaningful output, like ">>> Something important". In this two >>>>>>> i seeing >>>>>>> > >>> different one, could you please also pay attention to it. >>>>>>> > >>> >>>>>>> > >>> Best regards, >>>>>>> > >>> Stepan >>>>>>> > >>> >>>>>>> > >> >>>>>>> >>>>>>
Re: ML examples EvaluatorExample and MultipleMetricsExample looks the same
Also lost ignite-ml-tensorflow-model-parser and ignite-tensorflow in libs/optional ср, 12 февр. 2020 г. в 14:25, Stepan Pilschikov : > But now have new problems > I build ignite-2.8 build on TC > https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/5043672 > Previous > https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/4988324 > > New build much lighter > Previous: 5.7 Gb > Current: 4.3 Gb > And its looks like something missing, on a first look i notice that > /libs/optional/ignite-ml-mleap-model-parser lost completely > > > ср, 12 февр. 2020 г. в 14:18, Stepan Pilschikov >: > >> Thanks for fix >> Duplicated examples deleted and tutorial works on real (1+ node) cluster >> now >> I think ticket can be closed, have no power here >> >> вт, 11 февр. 2020 г. в 20:44, Alexey Zinoviev : >> >>> Sorry, for that, but I it touches ML-related stuff only and doesn't >>> influence on any another module. >>> I merged them to master later (currently, I have a 4 tickets in a queue). >>> >>> Will keep in mind for the next fixes >>> >>> вт, 11 февр. 2020 г. в 18:58, Maxim Muzafarov : >>> >>>> Alexey, >>>> >>>> Is the approach when we cherry-pick fixes to the 2.8 only after all >>>> fixes have verified in the master branch better? I just want to be >>>> sure the release branch to be stable enough. >>>> >>>> On Tue, 11 Feb 2020 at 18:36, Alexey Zinoviev >>>> wrote: >>>> > >>>> > Fixed both in release branch 2.8. Please verify and let me know >>>> > >>>> > вт, 11 февр. 2020 г. в 14:58, Stepan Pilschikov < >>>> pilshchikov@gmail.com>: >>>> > >>>> > > And one more >>>> > > https://issues.apache.org/jira/browse/IGNITE-12658 - >>>> > > TutorialStepByStepExample example failed if cluster with more then >>>> 1 node >>>> > > >>>> > > вт, 11 февр. 2020 г. в 11:52, Alexey Zinoviev < >>>> zaleslaw@gmail.com>: >>>> > > >>>> > >> Great, thank you so much, will fix next week >>>> > >> >>>> > >> вт, 11 февр. 2020 г., 11:39 Stepan Pilschikov < >>>> pilshchikov@gmail.com >>>> > >> >: >>>> > >> >>>> > >>> Hi, Alexey, could you please looking on one small accident happen >>>> in ML >>>> > >>> examples: >>>> > >>> https://issues.apache.org/jira/browse/IGNITE-12657 - 2 examples >>>> exactly >>>> > >>> the same. >>>> > >>> >>>> > >>> Also want to say that all previous examples have one common >>>> approach for >>>> > >>> meaningful output, like ">>> Something important". In this two i >>>> seeing >>>> > >>> different one, could you please also pay attention to it. >>>> > >>> >>>> > >>> Best regards, >>>> > >>> Stepan >>>> > >>> >>>> > >> >>>> >>>
Re: ML examples EvaluatorExample and MultipleMetricsExample looks the same
But now have new problems I build ignite-2.8 build on TC https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/5043672 Previous https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/4988324 New build much lighter Previous: 5.7 Gb Current: 4.3 Gb And its looks like something missing, on a first look i notice that /libs/optional/ignite-ml-mleap-model-parser lost completely ср, 12 февр. 2020 г. в 14:18, Stepan Pilschikov : > Thanks for fix > Duplicated examples deleted and tutorial works on real (1+ node) cluster > now > I think ticket can be closed, have no power here > > вт, 11 февр. 2020 г. в 20:44, Alexey Zinoviev : > >> Sorry, for that, but I it touches ML-related stuff only and doesn't >> influence on any another module. >> I merged them to master later (currently, I have a 4 tickets in a queue). >> >> Will keep in mind for the next fixes >> >> вт, 11 февр. 2020 г. в 18:58, Maxim Muzafarov : >> >>> Alexey, >>> >>> Is the approach when we cherry-pick fixes to the 2.8 only after all >>> fixes have verified in the master branch better? I just want to be >>> sure the release branch to be stable enough. >>> >>> On Tue, 11 Feb 2020 at 18:36, Alexey Zinoviev >>> wrote: >>> > >>> > Fixed both in release branch 2.8. Please verify and let me know >>> > >>> > вт, 11 февр. 2020 г. в 14:58, Stepan Pilschikov < >>> pilshchikov@gmail.com>: >>> > >>> > > And one more >>> > > https://issues.apache.org/jira/browse/IGNITE-12658 - >>> > > TutorialStepByStepExample example failed if cluster with more then 1 >>> node >>> > > >>> > > вт, 11 февр. 2020 г. в 11:52, Alexey Zinoviev < >>> zaleslaw@gmail.com>: >>> > > >>> > >> Great, thank you so much, will fix next week >>> > >> >>> > >> вт, 11 февр. 2020 г., 11:39 Stepan Pilschikov < >>> pilshchikov@gmail.com >>> > >> >: >>> > >> >>> > >>> Hi, Alexey, could you please looking on one small accident happen >>> in ML >>> > >>> examples: >>> > >>> https://issues.apache.org/jira/browse/IGNITE-12657 - 2 examples >>> exactly >>> > >>> the same. >>> > >>> >>> > >>> Also want to say that all previous examples have one common >>> approach for >>> > >>> meaningful output, like ">>> Something important". In this two i >>> seeing >>> > >>> different one, could you please also pay attention to it. >>> > >>> >>> > >>> Best regards, >>> > >>> Stepan >>> > >>> >>> > >> >>> >>
Re: ML examples EvaluatorExample and MultipleMetricsExample looks the same
Thanks for fix Duplicated examples deleted and tutorial works on real (1+ node) cluster now I think ticket can be closed, have no power here вт, 11 февр. 2020 г. в 20:44, Alexey Zinoviev : > Sorry, for that, but I it touches ML-related stuff only and doesn't > influence on any another module. > I merged them to master later (currently, I have a 4 tickets in a queue). > > Will keep in mind for the next fixes > > вт, 11 февр. 2020 г. в 18:58, Maxim Muzafarov : > >> Alexey, >> >> Is the approach when we cherry-pick fixes to the 2.8 only after all >> fixes have verified in the master branch better? I just want to be >> sure the release branch to be stable enough. >> >> On Tue, 11 Feb 2020 at 18:36, Alexey Zinoviev >> wrote: >> > >> > Fixed both in release branch 2.8. Please verify and let me know >> > >> > вт, 11 февр. 2020 г. в 14:58, Stepan Pilschikov < >> pilshchikov@gmail.com>: >> > >> > > And one more >> > > https://issues.apache.org/jira/browse/IGNITE-12658 - >> > > TutorialStepByStepExample example failed if cluster with more then 1 >> node >> > > >> > > вт, 11 февр. 2020 г. в 11:52, Alexey Zinoviev > >: >> > > >> > >> Great, thank you so much, will fix next week >> > >> >> > >> вт, 11 февр. 2020 г., 11:39 Stepan Pilschikov < >> pilshchikov@gmail.com >> > >> >: >> > >> >> > >>> Hi, Alexey, could you please looking on one small accident happen >> in ML >> > >>> examples: >> > >>> https://issues.apache.org/jira/browse/IGNITE-12657 - 2 examples >> exactly >> > >>> the same. >> > >>> >> > >>> Also want to say that all previous examples have one common >> approach for >> > >>> meaningful output, like ">>> Something important". In this two i >> seeing >> > >>> different one, could you please also pay attention to it. >> > >>> >> > >>> Best regards, >> > >>> Stepan >> > >>> >> > >> >> >
Re: ML examples EvaluatorExample and MultipleMetricsExample looks the same
And one more https://issues.apache.org/jira/browse/IGNITE-12658 - TutorialStepByStepExample example failed if cluster with more then 1 node вт, 11 февр. 2020 г. в 11:52, Alexey Zinoviev : > Great, thank you so much, will fix next week > > вт, 11 февр. 2020 г., 11:39 Stepan Pilschikov : > >> Hi, Alexey, could you please looking on one small accident happen in ML >> examples: >> https://issues.apache.org/jira/browse/IGNITE-12657 - 2 examples exactly >> the same. >> >> Also want to say that all previous examples have one common approach for >> meaningful output, like ">>> Something important". In this two i seeing >> different one, could you please also pay attention to it. >> >> Best regards, >> Stepan >> >
[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=1581416
ML examples EvaluatorExample and MultipleMetricsExample looks the same
Hi, Alexey, could you please looking on one small accident happen in ML examples: https://issues.apache.org/jira/browse/IGNITE-12657 - 2 examples exactly the same. Also want to say that all previous examples have one common approach for meaningful output, like ">>> Something important". In this two i seeing different one, could you please also pay attention to it. Best regards, Stepan
[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)
Re: Ignite 2.7.5 Release scope
Forget about link on this bug: https://issues.apache.org/jira/browse/IGNITE-11766 On Fri, Apr 19, 2019, 11:40 Stepan Pilschikov wrote: > Hi, all > > Not so long time ago founded and fixed bug for C++ examples on Windows > with jdk 11 > I think it might be useful for this release > > > On Mon, Apr 15, 2019, 18:39 Dmitriy Pavlov wrote: > >> Hi Igniters, >> >> Unfortunately, Ignite C++ examples cannot build without >> https://issues.apache.org/jira/browse/IGNITE-11195 >> >> So this issue should be included in the scope. >> >> Sincerely, >> Dmitriy Pavlov >> >> пт, 12 апр. 2019 г. в 13:53, Dmitriy Pavlov : >> >> > Hi Igniters, >> > >> > A bit of update: Last change fixing GridUnsafe for Java 12 was merged to >> > master and to 2.7.5 >> > >> > Overnight run contains a number of failures considered as blockers by >> > Apache Ignite Teamcity Bot (comparing to 2.7): >> > - Platform .NET (Inspections) always failed- Critical F.R.: 100,0% >> > - Platform C++ (Linux Clang) & Platform C++ (Linux)* failed in most >> cases >> > - Critical F.R.: 60,0% >> > - Disk Page Compressions - Module is N/A in 2.7.5 >> > - [Inspections] Core - always failed >> > - Hibernate 5.3 - Module is N/A in 2.7.5 >> > - Platform C++ (Win x64 | Release) - also failed in 2.7 >> > >> > And 2 more tests failure considered as blockers (now it is in re-run >> > state). If re-run shows these tests are passing I proceed with RC >> > preparation. >> > >> > Sincerely, >> > Dmitriy Pavlov >> > >> > вт, 9 апр. 2019 г. в 10:03, Dmitriy Pavlov : >> > >> >> Hi, Nikolay, >> >> >> >> thanks for offering help. >> >> >> >> Performance testing of new fix seems to be almost done. >> >> >> >> After merging of the last ticket (I hope it will be tomorrow) I will >> >> continue with RC building. There can be some issues related to scripts. >> >> >> >> Sincerely, >> >> Dmitriy Pavlov >> >> >> >> вт, 9 апр. 2019 г. в 09:53, Nikolay Izhikov : >> >> >> >>> Hello, Dmitriy. >> >>> >> >>> Any news about release? >> >>> Do you need assistance with it? >> >>> >> >>> вт, 2 апр. 2019 г. в 20:04, Dmitriy Pavlov : >> >>> >> >>> > Ivan P., it seems the netty approach you've proposed works well. >> Thank >> >>> you. >> >>> > >> >>> > Igniters, please take a look at following fix: >> >>> > https://github.com/apache/ignite/pull/6384 >> >>> > It allows us to start under Java 12 and under Java 11- (as it). >> >>> > >> >>> > Sincerely, >> >>> > Dmitriy Pavlov >> >>> > >> >>> > пт, 29 мар. 2019 г. в 22:57, Dmitriy Pavlov : >> >>> > >> >>> > > Denis, the issue here is that we don't know for sure. We see just >> one >> >>> > > blocking issue with accessing NioAccessObject. >> >>> > > >> >>> > > And there are 3 different scenario related to this issue fix: >> >>> > > - fixes won't help, and we should find out other options on how to >> >>> create >> >>> > > a direct buffer from pointer - needed for durable memory, Java 12 >> >>> goes >> >>> > to a >> >>> > > later release. >> >>> > > - some fix would help, but other issues come, Java 12 goes to some >> >>> later >> >>> > > release >> >>> > > - some from proposed fixes works, nothing else needs to be done - >> 1-2 >> >>> > days >> >>> > > >> >>> > > If it latest scenario, I would include as much as we can (1-2 days >> >>> extra >> >>> > > are comparable with minimal voting time). >> >>> > > >> >>> > > BTW, I've checked scripts it does not work for me, I will ask >> Andrey >> >>> > > G/Peter for advice on Monday. >> >>> > > >> >>> > > Sincerely, >> >>> > > Dmitriy Pavlov >> >>> > > >> >>> > > >> >>> > > пт, 29 мар. 2019 г. в 20:47, Denis Mag
Re: Ignite 2.7.5 Release scope
Hi, all Not so long time ago founded and fixed bug for C++ examples on Windows with jdk 11 I think it might be useful for this release On Mon, Apr 15, 2019, 18:39 Dmitriy Pavlov wrote: > Hi Igniters, > > Unfortunately, Ignite C++ examples cannot build without > https://issues.apache.org/jira/browse/IGNITE-11195 > > So this issue should be included in the scope. > > Sincerely, > Dmitriy Pavlov > > пт, 12 апр. 2019 г. в 13:53, Dmitriy Pavlov : > > > Hi Igniters, > > > > A bit of update: Last change fixing GridUnsafe for Java 12 was merged to > > master and to 2.7.5 > > > > Overnight run contains a number of failures considered as blockers by > > Apache Ignite Teamcity Bot (comparing to 2.7): > > - Platform .NET (Inspections) always failed- Critical F.R.: 100,0% > > - Platform C++ (Linux Clang) & Platform C++ (Linux)* failed in most cases > > - Critical F.R.: 60,0% > > - Disk Page Compressions - Module is N/A in 2.7.5 > > - [Inspections] Core - always failed > > - Hibernate 5.3 - Module is N/A in 2.7.5 > > - Platform C++ (Win x64 | Release) - also failed in 2.7 > > > > And 2 more tests failure considered as blockers (now it is in re-run > > state). If re-run shows these tests are passing I proceed with RC > > preparation. > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 9 апр. 2019 г. в 10:03, Dmitriy Pavlov : > > > >> Hi, Nikolay, > >> > >> thanks for offering help. > >> > >> Performance testing of new fix seems to be almost done. > >> > >> After merging of the last ticket (I hope it will be tomorrow) I will > >> continue with RC building. There can be some issues related to scripts. > >> > >> Sincerely, > >> Dmitriy Pavlov > >> > >> вт, 9 апр. 2019 г. в 09:53, Nikolay Izhikov : > >> > >>> Hello, Dmitriy. > >>> > >>> Any news about release? > >>> Do you need assistance with it? > >>> > >>> вт, 2 апр. 2019 г. в 20:04, Dmitriy Pavlov : > >>> > >>> > Ivan P., it seems the netty approach you've proposed works well. > Thank > >>> you. > >>> > > >>> > Igniters, please take a look at following fix: > >>> > https://github.com/apache/ignite/pull/6384 > >>> > It allows us to start under Java 12 and under Java 11- (as it). > >>> > > >>> > Sincerely, > >>> > Dmitriy Pavlov > >>> > > >>> > пт, 29 мар. 2019 г. в 22:57, Dmitriy Pavlov : > >>> > > >>> > > Denis, the issue here is that we don't know for sure. We see just > one > >>> > > blocking issue with accessing NioAccessObject. > >>> > > > >>> > > And there are 3 different scenario related to this issue fix: > >>> > > - fixes won't help, and we should find out other options on how to > >>> create > >>> > > a direct buffer from pointer - needed for durable memory, Java 12 > >>> goes > >>> > to a > >>> > > later release. > >>> > > - some fix would help, but other issues come, Java 12 goes to some > >>> later > >>> > > release > >>> > > - some from proposed fixes works, nothing else needs to be done - > 1-2 > >>> > days > >>> > > > >>> > > If it latest scenario, I would include as much as we can (1-2 days > >>> extra > >>> > > are comparable with minimal voting time). > >>> > > > >>> > > BTW, I've checked scripts it does not work for me, I will ask > Andrey > >>> > > G/Peter for advice on Monday. > >>> > > > >>> > > Sincerely, > >>> > > Dmitriy Pavlov > >>> > > > >>> > > > >>> > > пт, 29 мар. 2019 г. в 20:47, Denis Magda : > >>> > > > >>> > >> Folks, > >>> > >> > >>> > >> What are the efforts to support Java 12? Let's do 2.7.6 shortly if > >>> the > >>> > >> fixes are time-consuming. > >>> > >> > >>> > >> - > >>> > >> Denis > >>> > >> > >>> > >> > >>> > >> On Fri, Mar 29, 2019 at 10:08 AM Dmitriy Pavlov < > dpav...@apache.org > >>> > > >>> > >> wrote: > >>> > >> > >>> > >> > Hi Igniters, > >>> > >> > > >>> > >> > I would like to announce code freeze for 2.7.5. Only one open > >>> ticket > >>> > is > >>> > >> > there (reopened): > >>> https://issues.apache.org/jira/browse/IGNITE-11600 > >>> > >> (if > >>> > >> > we > >>> > >> > can't start using Java 12 we should clearly state it in > >>> scripts/code). > >>> > >> > > >>> > >> > We're entering to Stabilization phase for > >>> > >> > > >>> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.5 > >>> > >> and > >>> > >> > only blockers may be included into scope. See > >>> > >> > > >>> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > >>> > for > >>> > >> > more > >>> > >> > details. > >>> > >> > > >>> > >> > Sincerely, > >>> > >> > Dmitriy Pavlov > >>> > >> > > >>> > >> > пт, 29 мар. 2019 г. в 13:51, Dmitriy Pavlov >: > >>> > >> > > >>> > >> > > Hi Denis, > >>> > >> > > > >>> > >> > > I'm not talking about months. In this discussion, Andrey and > >>> Ivan > >>> > >> > proposed > >>> > >> > > a couple of fixes that may help. > >>> > >> > > > >>> > >> > > It will require a day or two to check if it helps. If it not > >>> helpful > >>> > >> then > >>> > >> > > we should modify startup scripts to say clearly that Java 12 > is > >>> not > >>> > >> > > supported. > >>> > >> > > > >>>
[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)
Re: Python examples are missing in Ignite 2.7
Denis, Dmitry Found that https://issues.apache.org/jira/browse/IGNITE-9922 Release process just do not copy this folder And this directory do not copy because of Dmitry concerns described earlier Agreed with Denis that examples folder should be in release build because of: - they really help to understand how client work - they understandable enough even without documentation - actually they contain link on examples documentation on readthedocs.io - others clients have common structure (examples, lib, README.md, artifacts to install package) but python client have not Dmitry talk about PyPI package which is should not contain any redundant files and i agreed with him But Denis talk only about apache-ignite release build binaries Also found https://issues.apache.org/jira/browse/IGNITE-10683 Don't know how new folder is affected on release procedure of PyPi package because ignite do not have fully automated pypi package release process, i told only about release binaries I've open new ticket to add examples in release build: https://issues.apache.org/jira/browse/IGNITE-11366 Dmitry, if you have any objections or improvements for this process you can described theys in ticket чт, 14 февр. 2019 г. в 21:21, Denis Magda : > Dmitry, > > Thanks for looking into this. I think that something went wrong with our > release procedure and we forgot to include the "examples" folder in Ignite > binary package. Sergey K. is checking the release procedures. > > > - > Denis > > > On Tue, Feb 12, 2019 at 7:28 PM Dmitry Melnichuk < > dmitry.melnic...@nobitlost.com> wrote: > > > We just browse through the contents of the latest Ignite bundles [1]. > > > > Source bundle [2] contains the examples all right; they are in this > > folder: > > > > /apache-ignite-2.7.0-src/modules/platforms/python/examples/ > > > > Binary bundle [3] do not contain examples. I'm not totally sure, but > > the reasoning I gave earlier might apply to binary bundle too. > > > > Can anyone who's aware of the bundling procedure/scripts chime in, > > please? > > > > [1] https://ignite.apache.org/download.cgi > > > > [2] > > > > > http://mirrors.standaloneinstaller.com/apache//ignite/2.7.0/apache-ignite-2.7.0-src.zip > > > > [3] > > > > > http://mirrors.standaloneinstaller.com/apache//ignite/2.7.0/apache-ignite-2.7.0-bin.zip > > > > On Wed, 2019-02-13 at 12:49 +1000, Dmitry Melnichuk wrote: > > > Denis, > > > > > > If by “release procedure” you mean the contents of the PyPI package, > > > then it is not a bug, but a deliberate decision, that was documented > > > in > > > README [1]: > > > > > > > Installation > > > > > > > > - for end user > > > > > > > > If you only want to use the pyignite module in your project, do: > > > > > > > > $ pip install pyignite > > > > > > > > -- for developer > > > > > > > > If you want to run tests, examples or build documentation, clone > > > > the > > > > whole repository… > > > > > > The reasoning: > > > > > > 1. The examples do not have much value by themselves. They are useful > > > only in conjunction with the documentation. If we do not ship the > > > documentation via PyPI, then we should not ship the examples either. > > > > > > 2. In production environment, the extra packaged stuff like examples > > > will be just a waste of space. > > > > > > 3. Most Python libraries and frameworks I know of, e.g. Django or > > > Scrapy, use the same approach: they have examples and test apps in > > > the > > > repository and reference them through their docs, but do not ship > > > them > > > via PyPI. > > > > > > [1] > > > > > > https://github.com/apache/ignite/tree/master/modules/platforms/python#installation > > > > > > On Tue, 2019-02-12 at 16:23 -0800, Denis Magda wrote: > > > > Igniters, > > > > > > > > Seems python examples were not added to the release bundle? > > > > > > > https://apacheignite.readme.io/v2.7/docs/python-thin-client#section-running-an-example > > > > > > > > There is no "examples" folder for Python. Any flaws in the release > > > > procedure? > > > > > > > > - > > > > Denis > > > > >
[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)
Re: Thin clients all in one
Hello again
Starting to check compatibility between thin clients in java/c++ and
py/php/nodejs and met some problems
1) Found that UUID mixed in a strange way if we taken it from Java/C++ to
PY/PHP/JS client and backwards
Have issue about it https://issues.apache.org/jira/browse/IGNITE-10691,
please look at it
2) Is more like conversation about seamless experience between all thin
clients
PY/PHP/JS/C++/Java have Timestamp data type which is contain tuple(millis,
nanos)
Main concern about nanos
In PHP/JS/Py Nanos count like "nanoseconds of the last millisecond" but in
Java and C++ its like we have millis and same millis but with nanos and its
strange for PHP/PY/JS if we take Java how is Base thin client
For example in Java we have new Timestamp(11) and it (fastTime=111000,
nanos=11100)
In C++ if we getting this cache we take (millis=11, nanos=11100)
which is kind a right and same as in java
But in py/php/js its look like (millis=11, nanos=0), its kind a
understandable what logic is, but sill different behavior and experience
What you thinking about it?
For now i can't understand why its done how its done, looks like it should
be same but something going wrong
пт, 30 нояб. 2018 г. в 01:18, Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com>:
> Hi Stepan,
>
> pls check the Ignite cfg you use - see the comments in the jira.
>
> Also, the examples executors (including AuthTlsExample) are included
> into NodeJS test suite in TeamCity which run periodically and
> successfully passed. Eg. the latest one:
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2426645&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ThinClientNodeJs
>
> Regards,
> -Alexey
>
> 28.11.2018 17:08, Stepan Pilschikov пишет:
> > Hello again
> >
> > If NodeJS sources found that example AuthTlsExample.js throwing exception
> > during execution
> > Output and grid configuration in
> > https://issues.apache.org/jira/browse/IGNITE-10447
> >
> > Can someone have a look at it?
> >
> > вс, 25 нояб. 2018 г. в 19:11, Stepan Pilschikov <
> pilshchikov@gmail.com>:
> >
> >> My bad,
> >> You right
> >>
> >> вс, 25 нояб. 2018 г. в 05:37, Dmitry Melnichuk <
> >> dmitry.melnic...@nobitlost.com>:
> >>
> >>> Stepan,
> >>>
> >>> AFAIK Map type did always behave correctly on client side, as it does
> >>> now. This is a corresponding piece of my test suite:
> >>>
> >>> ```
> >>> def test_put_get_map(client):
> >>>
> >>> cache = client.get_or_create_cache('test_map_cache')
> >>>
> >>> cache.put(
> >>> 'test_map',
> >>> (
> >>> MapObject.HASH_MAP,
> >>> {
> >>> (123, IntObject): 'test_data',
> >>> 456: ((1, [456, 'inner_test_string', 789]),
> >>> CollectionObject),
> >>> 'test_key': 32.4,
> >>> }
> >>> ),
> >>> value_hint=MapObject
> >>> )
> >>> value = cache.get('test_map')
> >>> assert value == (MapObject.HASH_MAP, {
> >>> 123: 'test_data',
> >>> 456: (1, [456, 'inner_test_string', 789]),
> >>> 'test_key': 32.4,
> >>> })
> >>>
> >>> ```
> >>>
> >>> Or is there another, more specific problem with maps?
> >>>
> >>> Dmitry
> >>>
> >>> On 11/25/18 3:56 AM, Stepan Pilschikov wrote:
> >>>> Dmitry,
> >>>>
> >>>> Great, checked, now all things woks well
> >>>> Hope that Igor made review for this PR
> >>>>
> >>>> But what about Maps? Looks like different ticket? or it can be done in
> >>> same
> >>>> ticket scope?
> >>>>
> >>>> пт, 23 нояб. 2018 г. в 23:58, Dmitry Melnichuk <
> >>>> dmitry.melnic...@nobitlost.com>:
> >>>>
> >>>>> Stepan,
> >>>>>
> >>>>> Sorry, I forgot to update from upstream prior to start working on
> this
> >>>>> issue, and thus brought a regression. My bad. Just merged with the
> >>>>> latest master. Please, check it out again.
> >>>>>
> >>>>> Dmitry
> >>>>>
&
[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)
Re: Thin clients all in one
Hello again
If NodeJS sources found that example AuthTlsExample.js throwing exception
during execution
Output and grid configuration in
https://issues.apache.org/jira/browse/IGNITE-10447
Can someone have a look at it?
вс, 25 нояб. 2018 г. в 19:11, Stepan Pilschikov :
> My bad,
> You right
>
> вс, 25 нояб. 2018 г. в 05:37, Dmitry Melnichuk <
> dmitry.melnic...@nobitlost.com>:
>
>> Stepan,
>>
>> AFAIK Map type did always behave correctly on client side, as it does
>> now. This is a corresponding piece of my test suite:
>>
>> ```
>> def test_put_get_map(client):
>>
>> cache = client.get_or_create_cache('test_map_cache')
>>
>> cache.put(
>> 'test_map',
>> (
>> MapObject.HASH_MAP,
>> {
>> (123, IntObject): 'test_data',
>> 456: ((1, [456, 'inner_test_string', 789]),
>> CollectionObject),
>> 'test_key': 32.4,
>> }
>> ),
>> value_hint=MapObject
>> )
>> value = cache.get('test_map')
>> assert value == (MapObject.HASH_MAP, {
>> 123: 'test_data',
>> 456: (1, [456, 'inner_test_string', 789]),
>> 'test_key': 32.4,
>> })
>>
>> ```
>>
>> Or is there another, more specific problem with maps?
>>
>> Dmitry
>>
>> On 11/25/18 3:56 AM, Stepan Pilschikov wrote:
>> > Dmitry,
>> >
>> > Great, checked, now all things woks well
>> > Hope that Igor made review for this PR
>> >
>> > But what about Maps? Looks like different ticket? or it can be done in
>> same
>> > ticket scope?
>> >
>> > пт, 23 нояб. 2018 г. в 23:58, Dmitry Melnichuk <
>> > dmitry.melnic...@nobitlost.com>:
>> >
>> >> Stepan,
>> >>
>> >> Sorry, I forgot to update from upstream prior to start working on this
>> >> issue, and thus brought a regression. My bad. Just merged with the
>> >> latest master. Please, check it out again.
>> >>
>> >> Dmitry
>> >>
>> >> On 11/24/18 1:37 AM, Stepan Pilschikov wrote:
>> >>> Dmitry,
>> >>>
>> >>> Iv checked and its actually work
>> >>> But a specially in this branch i found another bug
>> >>> Please look at my last comment:
>> >>>
>> >>
>> https://issues.apache.org/jira/browse/IGNITE-10358?focusedCommentId=16697285&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16697285
>> >>>
>> >>> пт, 23 нояб. 2018 г. в 01:21, Dmitry Melnichuk <
>> >>> dmitry.melnic...@nobitlost.com>:
>> >>>
>> >>>> Stepan,
>> >>>>
>> >>>> Thank you for your great job in evaluating Python thin client, as
>> well
>> >>>> as other thin clients.
>> >>>>
>> >>>> There was indeed a bug in Python client regarding the handling of
>> type
>> >>>> hints in Collection type. I created a fix and did a PR under
>> >>>> IGNITE-10358 task, but the same PR is also fixes the problem in
>> >>>> IGNITE-10230 task.
>> >>>>
>> >>>> As of handling the type mapping in gists you provided, I left
>> comments
>> >>>> on both tasks.
>> >>>>
>> >>>> Dmitry
>> >>>>
>> >>>> On 11/21/18 6:37 PM, Stepan Pilschikov wrote:
>> >>>>> Dmitry, Alexey
>> >>>>>
>> >>>>> Thank you for help, this answers help me a lot with understanding
>> how
>> >>>>> clients are work
>> >>>>>
>> >>>>> Not so long time ago i met problem which is have expected behavior,
>> but
>> >>>> its
>> >>>>> may broke some workflows in future for some users
>> >>>>>
>> >>>>> Its all about not specified data types in collections and map's
>> >>>>> All description and examples in
>> >>>>> https://issues.apache.org/jira/browse/IGNITE-10358
>> >>>>>
>> >>>>> Dmitry, can you have a quick look at it and maybe in future somehow
>> fix
>> >>>> it?
>> >>>&g
Re: Thin clients all in one
My bad,
You right
вс, 25 нояб. 2018 г. в 05:37, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Stepan,
>
> AFAIK Map type did always behave correctly on client side, as it does
> now. This is a corresponding piece of my test suite:
>
> ```
> def test_put_get_map(client):
>
> cache = client.get_or_create_cache('test_map_cache')
>
> cache.put(
> 'test_map',
> (
> MapObject.HASH_MAP,
> {
> (123, IntObject): 'test_data',
> 456: ((1, [456, 'inner_test_string', 789]),
> CollectionObject),
> 'test_key': 32.4,
> }
> ),
> value_hint=MapObject
> )
> value = cache.get('test_map')
> assert value == (MapObject.HASH_MAP, {
> 123: 'test_data',
> 456: (1, [456, 'inner_test_string', 789]),
> 'test_key': 32.4,
> })
>
> ```
>
> Or is there another, more specific problem with maps?
>
> Dmitry
>
> On 11/25/18 3:56 AM, Stepan Pilschikov wrote:
> > Dmitry,
> >
> > Great, checked, now all things woks well
> > Hope that Igor made review for this PR
> >
> > But what about Maps? Looks like different ticket? or it can be done in
> same
> > ticket scope?
> >
> > пт, 23 нояб. 2018 г. в 23:58, Dmitry Melnichuk <
> > dmitry.melnic...@nobitlost.com>:
> >
> >> Stepan,
> >>
> >> Sorry, I forgot to update from upstream prior to start working on this
> >> issue, and thus brought a regression. My bad. Just merged with the
> >> latest master. Please, check it out again.
> >>
> >> Dmitry
> >>
> >> On 11/24/18 1:37 AM, Stepan Pilschikov wrote:
> >>> Dmitry,
> >>>
> >>> Iv checked and its actually work
> >>> But a specially in this branch i found another bug
> >>> Please look at my last comment:
> >>>
> >>
> https://issues.apache.org/jira/browse/IGNITE-10358?focusedCommentId=16697285&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16697285
> >>>
> >>> пт, 23 нояб. 2018 г. в 01:21, Dmitry Melnichuk <
> >>> dmitry.melnic...@nobitlost.com>:
> >>>
> >>>> Stepan,
> >>>>
> >>>> Thank you for your great job in evaluating Python thin client, as well
> >>>> as other thin clients.
> >>>>
> >>>> There was indeed a bug in Python client regarding the handling of type
> >>>> hints in Collection type. I created a fix and did a PR under
> >>>> IGNITE-10358 task, but the same PR is also fixes the problem in
> >>>> IGNITE-10230 task.
> >>>>
> >>>> As of handling the type mapping in gists you provided, I left comments
> >>>> on both tasks.
> >>>>
> >>>> Dmitry
> >>>>
> >>>> On 11/21/18 6:37 PM, Stepan Pilschikov wrote:
> >>>>> Dmitry, Alexey
> >>>>>
> >>>>> Thank you for help, this answers help me a lot with understanding how
> >>>>> clients are work
> >>>>>
> >>>>> Not so long time ago i met problem which is have expected behavior,
> but
> >>>> its
> >>>>> may broke some workflows in future for some users
> >>>>>
> >>>>> Its all about not specified data types in collections and map's
> >>>>> All description and examples in
> >>>>> https://issues.apache.org/jira/browse/IGNITE-10358
> >>>>>
> >>>>> Dmitry, can you have a quick look at it and maybe in future somehow
> fix
> >>>> it?
> >>>>>
> >>>>> пт, 26 окт. 2018 г. в 19:05, Dmitry Melnichuk <
> >>>>> dmitry.melnic...@nobitlost.com>:
> >>>>>
> >>>>>> Stepan!
> >>>>>>
> >>>>>> TL/DR: what you got with Python client in your gist is an intended
> >>>>>> behavior.
> >>>>>>
> >>>>>> Explanation: As per docs, Object array contains of type ID (which is
> >>>>>> defaults to -1) and an array of objects.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>
> https://apacheign
Re: Thin clients all in one
Dmitry,
Great, checked, now all things woks well
Hope that Igor made review for this PR
But what about Maps? Looks like different ticket? or it can be done in same
ticket scope?
пт, 23 нояб. 2018 г. в 23:58, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Stepan,
>
> Sorry, I forgot to update from upstream prior to start working on this
> issue, and thus brought a regression. My bad. Just merged with the
> latest master. Please, check it out again.
>
> Dmitry
>
> On 11/24/18 1:37 AM, Stepan Pilschikov wrote:
> > Dmitry,
> >
> > Iv checked and its actually work
> > But a specially in this branch i found another bug
> > Please look at my last comment:
> >
> https://issues.apache.org/jira/browse/IGNITE-10358?focusedCommentId=16697285&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16697285
> >
> > пт, 23 нояб. 2018 г. в 01:21, Dmitry Melnichuk <
> > dmitry.melnic...@nobitlost.com>:
> >
> >> Stepan,
> >>
> >> Thank you for your great job in evaluating Python thin client, as well
> >> as other thin clients.
> >>
> >> There was indeed a bug in Python client regarding the handling of type
> >> hints in Collection type. I created a fix and did a PR under
> >> IGNITE-10358 task, but the same PR is also fixes the problem in
> >> IGNITE-10230 task.
> >>
> >> As of handling the type mapping in gists you provided, I left comments
> >> on both tasks.
> >>
> >> Dmitry
> >>
> >> On 11/21/18 6:37 PM, Stepan Pilschikov wrote:
> >>> Dmitry, Alexey
> >>>
> >>> Thank you for help, this answers help me a lot with understanding how
> >>> clients are work
> >>>
> >>> Not so long time ago i met problem which is have expected behavior, but
> >> its
> >>> may broke some workflows in future for some users
> >>>
> >>> Its all about not specified data types in collections and map's
> >>> All description and examples in
> >>> https://issues.apache.org/jira/browse/IGNITE-10358
> >>>
> >>> Dmitry, can you have a quick look at it and maybe in future somehow fix
> >> it?
> >>>
> >>> пт, 26 окт. 2018 г. в 19:05, Dmitry Melnichuk <
> >>> dmitry.melnic...@nobitlost.com>:
> >>>
> >>>> Stepan!
> >>>>
> >>>> TL/DR: what you got with Python client in your gist is an intended
> >>>> behavior.
> >>>>
> >>>> Explanation: As per docs, Object array contains of type ID (which is
> >>>> defaults to -1) and an array of objects.
> >>>>
> >>>>
> >>>>
> >>
> https://apacheignite.readme.io/docs/binary-client-protocol-data-format#section-object-array
> >>>>
> >>>> Your gist might be fixed accordingly:
> >>>>
> >>>> ```
> >>>> from pyignite import Client
> >>>> from pyignite.datatypes import *
> >>>>
> >>>> OBJECT_ARRAY_TYPE_ID = -1
> >>>> OBJECT_ARRAY_CONTENTS = [1, 2]
> >>>>
> >>>> client = Client()
> >>>> client.connect('127.0.0.1', 10800)
> >>>> cache = client.get_or_create_cache("PY_OBJECT_ARRAY")
> >>>> cache.put(
> >>>>1,
> >>>>(OBJECT_ARRAY_TYPE_ID, OBJECT_ARRAY_CONTENTS),
> >>>>key_hint=IntObject,
> >>>>value_hint=ObjectArrayObject,
> >>>> )
> >>>>
> >>>> # Python output: print(cache.get(1))
> >>>> # (-1, [1, 2])
> >>>> ```
> >>>>
> >>>> The situation is similar with Map and Collection, they have types.
> Types
> >>>> and type IDs are mostly useless in Python, but I left them for
> >>>> interoperability reasons. If you think I should kick them out, just
> let
> >>>> me know.
> >>>>
> >>>> The usage of these 3 data types is documented and tested. You can
> refer
> >>>> to the table in “Data types” section:
> >>>>
> >>>>
> >>>>
> >>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/datatypes/parsers.html
> >>>>
> >>>> The tests are here:
> >>>>
> >>>>
> >>>>
> >>
> https://github.com/apache/ign
Re: Thin clients all in one
Dmitry,
Iv checked and its actually work
But a specially in this branch i found another bug
Please look at my last comment:
https://issues.apache.org/jira/browse/IGNITE-10358?focusedCommentId=16697285&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16697285
пт, 23 нояб. 2018 г. в 01:21, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Stepan,
>
> Thank you for your great job in evaluating Python thin client, as well
> as other thin clients.
>
> There was indeed a bug in Python client regarding the handling of type
> hints in Collection type. I created a fix and did a PR under
> IGNITE-10358 task, but the same PR is also fixes the problem in
> IGNITE-10230 task.
>
> As of handling the type mapping in gists you provided, I left comments
> on both tasks.
>
> Dmitry
>
> On 11/21/18 6:37 PM, Stepan Pilschikov wrote:
> > Dmitry, Alexey
> >
> > Thank you for help, this answers help me a lot with understanding how
> > clients are work
> >
> > Not so long time ago i met problem which is have expected behavior, but
> its
> > may broke some workflows in future for some users
> >
> > Its all about not specified data types in collections and map's
> > All description and examples in
> > https://issues.apache.org/jira/browse/IGNITE-10358
> >
> > Dmitry, can you have a quick look at it and maybe in future somehow fix
> it?
> >
> > пт, 26 окт. 2018 г. в 19:05, Dmitry Melnichuk <
> > dmitry.melnic...@nobitlost.com>:
> >
> >> Stepan!
> >>
> >> TL/DR: what you got with Python client in your gist is an intended
> >> behavior.
> >>
> >> Explanation: As per docs, Object array contains of type ID (which is
> >> defaults to -1) and an array of objects.
> >>
> >>
> >>
> https://apacheignite.readme.io/docs/binary-client-protocol-data-format#section-object-array
> >>
> >> Your gist might be fixed accordingly:
> >>
> >> ```
> >> from pyignite import Client
> >> from pyignite.datatypes import *
> >>
> >> OBJECT_ARRAY_TYPE_ID = -1
> >> OBJECT_ARRAY_CONTENTS = [1, 2]
> >>
> >> client = Client()
> >> client.connect('127.0.0.1', 10800)
> >> cache = client.get_or_create_cache("PY_OBJECT_ARRAY")
> >> cache.put(
> >> 1,
> >> (OBJECT_ARRAY_TYPE_ID, OBJECT_ARRAY_CONTENTS),
> >> key_hint=IntObject,
> >> value_hint=ObjectArrayObject,
> >> )
> >>
> >> # Python output: print(cache.get(1))
> >> # (-1, [1, 2])
> >> ```
> >>
> >> The situation is similar with Map and Collection, they have types. Types
> >> and type IDs are mostly useless in Python, but I left them for
> >> interoperability reasons. If you think I should kick them out, just let
> >> me know.
> >>
> >> The usage of these 3 data types is documented and tested. You can refer
> >> to the table in “Data types” section:
> >>
> >>
> >>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/datatypes/parsers.html
> >>
> >> The tests are here:
> >>
> >>
> >>
> https://github.com/apache/ignite/blob/master/modules/platforms/python/tests/test_datatypes.py#L116-L124
> >>
> >> On 10/26/18 11:57 PM, Stepan Pilschikov wrote:
> >>> Hi, everyone
> >>>
> >>> Create new thread to centralize cross compatibility and others common
> >>> problems between thin clients
> >>>
> >>> Tying to use Object array to exchange different data between JS, PHP
> and
> >>> Python thin clients
> >>>
> >>> JS and PHP simply can't put any type of arrays
> >>> Python can put data, but if you take it, data would be completely
> >>> different, maybe during this put process data is changed
> >>>
> >>> Code and output:
> >>> PHP -
> >> https://gist.github.com/pilshchikov/e887d31d4f2f36923470fead14c7801a
> >>> JS -
> >> https://gist.github.com/pilshchikov/ba49067fd8924ebdf4414ec63838b86d
> >>> Python -
> >>> https://gist.github.com/pilshchikov/f4bbf76e31547e2dca7d4cc5d55bd24f
> >>>
> >>> I'm tried different data types (string, double, float, complex objects,
> >>> just random objects, char, byte, Date), still
> >>>
> >>> How, from my perspective, it should works:
> >>> put array of any type and then get this array.
> >>> Example: put [1,2,3] -> get [1,2,3] or put [new Date(), new Date()] ->
> >>> get [[Date object], [Date object]] (like in java thin client)
> >>>
> >>> Looks like bug in all clients, what you think?
> >>>
> >>> I wanted to try Collections, but i think this type have same problem
> >>
> >
>
>
Re: Thin clients all in one
Dmitry, Alexey
Thank you for help, this answers help me a lot with understanding how
clients are work
Not so long time ago i met problem which is have expected behavior, but its
may broke some workflows in future for some users
Its all about not specified data types in collections and map's
All description and examples in
https://issues.apache.org/jira/browse/IGNITE-10358
Dmitry, can you have a quick look at it and maybe in future somehow fix it?
пт, 26 окт. 2018 г. в 19:05, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Stepan!
>
> TL/DR: what you got with Python client in your gist is an intended
> behavior.
>
> Explanation: As per docs, Object array contains of type ID (which is
> defaults to -1) and an array of objects.
>
>
> https://apacheignite.readme.io/docs/binary-client-protocol-data-format#section-object-array
>
> Your gist might be fixed accordingly:
>
> ```
> from pyignite import Client
> from pyignite.datatypes import *
>
> OBJECT_ARRAY_TYPE_ID = -1
> OBJECT_ARRAY_CONTENTS = [1, 2]
>
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("PY_OBJECT_ARRAY")
> cache.put(
> 1,
> (OBJECT_ARRAY_TYPE_ID, OBJECT_ARRAY_CONTENTS),
> key_hint=IntObject,
> value_hint=ObjectArrayObject,
> )
>
> # Python output: print(cache.get(1))
> # (-1, [1, 2])
> ```
>
> The situation is similar with Map and Collection, they have types. Types
> and type IDs are mostly useless in Python, but I left them for
> interoperability reasons. If you think I should kick them out, just let
> me know.
>
> The usage of these 3 data types is documented and tested. You can refer
> to the table in “Data types” section:
>
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/datatypes/parsers.html
>
> The tests are here:
>
>
> https://github.com/apache/ignite/blob/master/modules/platforms/python/tests/test_datatypes.py#L116-L124
>
> On 10/26/18 11:57 PM, Stepan Pilschikov wrote:
> > Hi, everyone
> >
> > Create new thread to centralize cross compatibility and others common
> > problems between thin clients
> >
> > Tying to use Object array to exchange different data between JS, PHP and
> > Python thin clients
> >
> > JS and PHP simply can't put any type of arrays
> > Python can put data, but if you take it, data would be completely
> > different, maybe during this put process data is changed
> >
> > Code and output:
> > PHP -
> https://gist.github.com/pilshchikov/e887d31d4f2f36923470fead14c7801a
> > JS -
> https://gist.github.com/pilshchikov/ba49067fd8924ebdf4414ec63838b86d
> > Python -
> > https://gist.github.com/pilshchikov/f4bbf76e31547e2dca7d4cc5d55bd24f
> >
> > I'm tried different data types (string, double, float, complex objects,
> > just random objects, char, byte, Date), still
> >
> > How, from my perspective, it should works:
> > put array of any type and then get this array.
> > Example: put [1,2,3] -> get [1,2,3] or put [new Date(), new Date()] ->
> > get [[Date object], [Date object]] (like in java thin client)
> >
> > Looks like bug in all clients, what you think?
> >
> > I wanted to try Collections, but i think this type have same problem
>
[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)
Re: Thin clients all in one
Oh, now i finally understand (PHP and JS). And more, just found tests with usage example (don't now why im just missed it) Thank you Waiting for Dmitry пт, 26 окт. 2018 г. в 18:00, Alexey Kosenchuk < alexey.kosenc...@nobitlost.com>: > thanks, now it's clear. > > For NodeJs and PHP clients: >You cannot use OBJECT_ARRAY constant to specify a field type. This is > true for all non-primitive types. That's why you get ""type" argument > has incorrect value" exception. >Non-primitive types can be specified using special objects. In this > case - ObjectArrayType. >All these are described in the API specs. >So, you need to update your examples: > PHP: setValueType(new ObjectArrayType()) > NodeJs: setValueType(new ObjectArrayType()) or > setValueType(new > ObjectArrayType(ObjectType.PRIMITIVE_TYPE.INTEGER)) (if you want an > array of integers) > > For Python client: >Dmitry will answer. > > Regards, > -Alexey > > 26.10.2018 17:22, Stepan Pilschikov пишет: > > No > > > > Now tried > > code and output - > > https://gist.github.com/pilshchikov/4c02057e624baa54326a1e75b4ee3f46 > > And it looks like it works > > > > пт, 26 окт. 2018 г. в 17:10, Alexey Kosenchuk > > mailto:alexey.kosenc...@nobitlost.com > >>: > > > > Hi Stepan, > > > > Have you tried the same with Java and .net thin clients as well and > > everything work fine? > > > > Thanks, > > -Alexey > > > > 26.10.2018 16:57, Stepan Pilschikov пишет: > > > Hi, everyone > > > > > > Create new thread to centralize cross compatibility and others > > common > > > problems between thin clients > > > > > > Tying to use Object array to exchange different data between JS, > > PHP and > > > Python thin clients > > > > > > JS and PHP simply can't put any type of arrays > > > Python can put data, but if you take it, data would be completely > > > different, maybe during this put process data is changed > > > > > > Code and output: > > > PHP - > > https://gist.github.com/pilshchikov/e887d31d4f2f36923470fead14c7801a > > > JS - > > https://gist.github.com/pilshchikov/ba49067fd8924ebdf4414ec63838b86d > > > Python - > > > > https://gist.github.com/pilshchikov/f4bbf76e31547e2dca7d4cc5d55bd24f > > > > > > I'm tried different data types (string, double, float, complex > > objects, > > > just random objects, char, byte, Date), still > > > > > > How, from my perspective, it should works: > > > put array of any type and then get this array. > > > Example: put [1,2,3] -> get [1,2,3] or put [new Date(), new > > Date()] -> > > > get [[Date object], [Date object]] (like in java thin client) > > > > > > Looks like bug in all clients, what you think? > > > > > > I wanted to try Collections, but i think this type have same > problem > > >
Re: Thin clients all in one
No Now tried code and output - https://gist.github.com/pilshchikov/4c02057e624baa54326a1e75b4ee3f46 And it looks like it works пт, 26 окт. 2018 г. в 17:10, Alexey Kosenchuk < alexey.kosenc...@nobitlost.com>: > Hi Stepan, > > Have you tried the same with Java and .net thin clients as well and > everything work fine? > > Thanks, > -Alexey > > 26.10.2018 16:57, Stepan Pilschikov пишет: > > Hi, everyone > > > > Create new thread to centralize cross compatibility and others common > > problems between thin clients > > > > Tying to use Object array to exchange different data between JS, PHP and > > Python thin clients > > > > JS and PHP simply can't put any type of arrays > > Python can put data, but if you take it, data would be completely > > different, maybe during this put process data is changed > > > > Code and output: > > PHP - > https://gist.github.com/pilshchikov/e887d31d4f2f36923470fead14c7801a > > JS - > https://gist.github.com/pilshchikov/ba49067fd8924ebdf4414ec63838b86d > > Python - > > https://gist.github.com/pilshchikov/f4bbf76e31547e2dca7d4cc5d55bd24f > > > > I'm tried different data types (string, double, float, complex objects, > > just random objects, char, byte, Date), still > > > > How, from my perspective, it should works: > > put array of any type and then get this array. > > Example: put [1,2,3] -> get [1,2,3] or put [new Date(), new Date()] -> > > get [[Date object], [Date object]] (like in java thin client) > > > > Looks like bug in all clients, what you think? > > > > I wanted to try Collections, but i think this type have same problem >
Thin clients all in one
Hi, everyone Create new thread to centralize cross compatibility and others common problems between thin clients Tying to use Object array to exchange different data between JS, PHP and Python thin clients JS and PHP simply can't put any type of arrays Python can put data, but if you take it, data would be completely different, maybe during this put process data is changed Code and output: PHP - https://gist.github.com/pilshchikov/e887d31d4f2f36923470fead14c7801a JS - https://gist.github.com/pilshchikov/ba49067fd8924ebdf4414ec63838b86d Python - https://gist.github.com/pilshchikov/f4bbf76e31547e2dca7d4cc5d55bd24f I'm tried different data types (string, double, float, complex objects, just random objects, char, byte, Date), still How, from my perspective, it should works: put array of any type and then get this array. Example: put [1,2,3] -> get [1,2,3] or put [new Date(), new Date()] -> get [[Date object], [Date object]] (like in java thin client) Looks like bug in all clients, what you think? I wanted to try Collections, but i think this type have same problem
[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)
Re: PHP thin client
And more, If im use ->setValueType(ObjectType::ENUM) during $cache->get(1); it throwing exception that client can't convert BINARY_ENUM to ENUM вт, 23 окт. 2018 г. в 15:57, Stepan Pilschikov : > Thanks, finally fixes are merged > > I have new question > > I'm trying to put Enum object and get it back, but catch exception that > enum is null > > code with output - > https://gist.github.com/pilshchikov/b89c6e25f29da88ac03caa42231a02bc > > Also can't find Enum data type test in sources > > I trying to use Enum in a right way? If answer is Yes, can you please > check this for yourself? > I think its a bug > > вс, 21 окт. 2018 г. в 9:36, Pavel Petroshenko : > >> Hi Stepan, >> >> I submitted a patch and updated JIRA with some comments. Can you please >> give it a try? >> >> Thanks, >> P. >> >> >> On Fri, Oct 19, 2018 at 9:07 AM Stepan Pilschikov < >> pilshchikov@gmail.com> wrote: >> >>> Alexey, >>> >>> Hi >>> >>> I'm trying to use PHP client for some times and discover one problem with >>> DATA and TIMESTAMP data types >>> I'ts appear when you trying to use DATA or TIMESTAMP as cache key >>> >>> All description in ticket: >>> https://issues.apache.org/jira/browse/IGNITE-9951 >>> >>> Can you help with that, please? >>> >>> чт, 11 окт. 2018 г. в 16:02, Igor Sapego : >>> >>> > Alexey, >>> > >>> > Since PHP thin client is now in master, can you please add it to our >>> > "Thin clients features" wiki page, so we can track the feature parity >>> > of our clients? >>> > >>> > [1] - >>> > >>> https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features >>> > >>> > Best Regards, >>> > Igor >>> > >>> > >>> > On Wed, Oct 10, 2018 at 2:56 PM Vladimir Ozerov >>> > wrote: >>> > >>> > > I am not sure there is an answer. This is just how we handled it >>> before. >>> > > IMO both approaches works fine. BTW, I already merged Vyacheslav's PR >>> > > several hours ago. >>> > > >>> > > On Wed, Oct 10, 2018 at 1:24 PM Igor Sapego >>> wrote: >>> > > >>> > >> Vyacheslav, >>> > >> >>> > >> In this case, we should do the same with all existing doxygen >>> > >> files, not only this one (see files with .dxg extension) >>> > >> >>> > >> Vova, Pavel, >>> > >> >>> > >> Were there historically any reasons to exclude doxygen files >>> > >> from check instead of adding a license header? >>> > >> >>> > >> Best Regards, >>> > >> Igor >>> > >> >>> > >> >>> > >> On Tue, Oct 9, 2018 at 11:49 PM Vyacheslav Daradur < >>> daradu...@gmail.com >>> > > >>> > >> wrote: >>> > >> >>> > >>> Great work guys, thanks! >>> > >>> >>> > >>> I've noticed TC fails in the build plan "Licenses Headers" which >>> Igor >>> > >>> have fixed already by excluding Doxyfile from checking. >>> > >>> >>> > >>> I've filled a ticket [1] and I'd suggest fixing the test in another >>> > >>> way by adding the license header to Doxyfile. >>> > >>> >>> > >>> Igor, please, have a look at prepared PR [2] (tests passed [3]). >>> > >>> >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-9832 >>> > >>> [2] https://github.com/apache/ignite/pull/4938/files >>> > >>> [3] https://ci.ignite.apache.org/viewLog.html?buildId=2046206 >>> > >>> On Tue, Oct 9, 2018 at 6:31 PM Igor Sapego >>> wrote: >>> > >>> > >>> > >>> > As the seem to be everything OK with the code and tests and >>> > >>> > no one had any comment for quite some time, I've merged the >>> > >>> > PHP to Ignite's master. >>> > >>> > >>> > >>> > Great job, guys! >>> > >>> > >>> > >>> > >>> > >>> > Best Regards, >&
Re: PHP thin client
Thanks, finally fixes are merged I have new question I'm trying to put Enum object and get it back, but catch exception that enum is null code with output - https://gist.github.com/pilshchikov/b89c6e25f29da88ac03caa42231a02bc Also can't find Enum data type test in sources I trying to use Enum in a right way? If answer is Yes, can you please check this for yourself? I think its a bug вс, 21 окт. 2018 г. в 9:36, Pavel Petroshenko : > Hi Stepan, > > I submitted a patch and updated JIRA with some comments. Can you please > give it a try? > > Thanks, > P. > > > On Fri, Oct 19, 2018 at 9:07 AM Stepan Pilschikov < > pilshchikov@gmail.com> wrote: > >> Alexey, >> >> Hi >> >> I'm trying to use PHP client for some times and discover one problem with >> DATA and TIMESTAMP data types >> I'ts appear when you trying to use DATA or TIMESTAMP as cache key >> >> All description in ticket: >> https://issues.apache.org/jira/browse/IGNITE-9951 >> >> Can you help with that, please? >> >> чт, 11 окт. 2018 г. в 16:02, Igor Sapego : >> >> > Alexey, >> > >> > Since PHP thin client is now in master, can you please add it to our >> > "Thin clients features" wiki page, so we can track the feature parity >> > of our clients? >> > >> > [1] - >> > >> https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features >> > >> > Best Regards, >> > Igor >> > >> > >> > On Wed, Oct 10, 2018 at 2:56 PM Vladimir Ozerov >> > wrote: >> > >> > > I am not sure there is an answer. This is just how we handled it >> before. >> > > IMO both approaches works fine. BTW, I already merged Vyacheslav's PR >> > > several hours ago. >> > > >> > > On Wed, Oct 10, 2018 at 1:24 PM Igor Sapego >> wrote: >> > > >> > >> Vyacheslav, >> > >> >> > >> In this case, we should do the same with all existing doxygen >> > >> files, not only this one (see files with .dxg extension) >> > >> >> > >> Vova, Pavel, >> > >> >> > >> Were there historically any reasons to exclude doxygen files >> > >> from check instead of adding a license header? >> > >> >> > >> Best Regards, >> > >> Igor >> > >> >> > >> >> > >> On Tue, Oct 9, 2018 at 11:49 PM Vyacheslav Daradur < >> daradu...@gmail.com >> > > >> > >> wrote: >> > >> >> > >>> Great work guys, thanks! >> > >>> >> > >>> I've noticed TC fails in the build plan "Licenses Headers" which >> Igor >> > >>> have fixed already by excluding Doxyfile from checking. >> > >>> >> > >>> I've filled a ticket [1] and I'd suggest fixing the test in another >> > >>> way by adding the license header to Doxyfile. >> > >>> >> > >>> Igor, please, have a look at prepared PR [2] (tests passed [3]). >> > >>> >> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-9832 >> > >>> [2] https://github.com/apache/ignite/pull/4938/files >> > >>> [3] https://ci.ignite.apache.org/viewLog.html?buildId=2046206 >> > >>> On Tue, Oct 9, 2018 at 6:31 PM Igor Sapego >> wrote: >> > >>> > >> > >>> > As the seem to be everything OK with the code and tests and >> > >>> > no one had any comment for quite some time, I've merged the >> > >>> > PHP to Ignite's master. >> > >>> > >> > >>> > Great job, guys! >> > >>> > >> > >>> > >> > >>> > Best Regards, >> > >>> > Igor >> > >>> > >> > >>> > >> > >>> > On Wed, Sep 19, 2018 at 1:00 AM Prachi Garg >> > >>> wrote: >> > >>> > >> > >>> > > Hi Stephan, Alexey >> > >>> > > >> > >>> > > That's exactly what readme.io contains - installation >> > instructions, >> > >>> > > configuration, and examples for key-value, sql, etc. for thin >> > >>> clients. For >> > >>> > > example, see these documentati
Re: Python thin client
Oh, nice Thanks for quick response I've check against JS and PHP, now its works properly Igor, can you approve this patch? сб, 20 окт. 2018 г. в 0:57, Dmitry Melnichuk : > Stepan, > > My bad. I got the Decimal part of Ignite thin client protocol > specification totally wrong. > > Just submitted a patch tested against Java thin client. Please evaluate. > > On 10/20/18 2:00 AM, Stepan Pilschikov wrote: > > Dmitry, > > > > One more thing > > Discover that Decimal data type can't be getting by others clients > > > > Make ticket with description: > > https://issues.apache.org/jira/browse/IGNITE-9950 > > > > Please, can you help to investigate this problem? > > > > ср, 17 окт. 2018 г. в 23:14, Stepan Pilschikov < > pilshchikov@gmail.com>: > > > >> Dmitry, > >> > >> Great, now client works properly on all OS > >> Thanks > >> > >> I hope PR will be merged soon > >> > >> Igor, can please help with that? > >> > >> ср, 17 окт. 2018 г. в 20:48, Dmitry Melnichuk < > >> dmitry.melnic...@nobitlost.com>: > >> > >>> Stepan, > >>> > >>> Sadly, it was a C `long` data type size mismatch between Windows and > >>> other OSes. I investigated this issue and offered a pull request. > >>> > >>> https://github.com/apache/ignite/pull/5017 > >>> > >>> On 10/17/18 6:29 PM, Stepan Pilschikov wrote: > >>>> Dmitry, > >>>> > >>>> I've trying to use python thin client with Ignite 2.7 it dosn't work > >>>> Please help to investigate > >>>> Problem reproduced on several others machines > >>>> > >>>> Issue: > >>>> https://issues.apache.org/jira/browse/IGNITE-9908 > >>>> > >>> > >> > > > >
Re: PHP thin client
Alexey, Hi I'm trying to use PHP client for some times and discover one problem with DATA and TIMESTAMP data types I'ts appear when you trying to use DATA or TIMESTAMP as cache key All description in ticket: https://issues.apache.org/jira/browse/IGNITE-9951 Can you help with that, please? чт, 11 окт. 2018 г. в 16:02, Igor Sapego : > Alexey, > > Since PHP thin client is now in master, can you please add it to our > "Thin clients features" wiki page, so we can track the feature parity > of our clients? > > [1] - > https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features > > Best Regards, > Igor > > > On Wed, Oct 10, 2018 at 2:56 PM Vladimir Ozerov > wrote: > > > I am not sure there is an answer. This is just how we handled it before. > > IMO both approaches works fine. BTW, I already merged Vyacheslav's PR > > several hours ago. > > > > On Wed, Oct 10, 2018 at 1:24 PM Igor Sapego wrote: > > > >> Vyacheslav, > >> > >> In this case, we should do the same with all existing doxygen > >> files, not only this one (see files with .dxg extension) > >> > >> Vova, Pavel, > >> > >> Were there historically any reasons to exclude doxygen files > >> from check instead of adding a license header? > >> > >> Best Regards, > >> Igor > >> > >> > >> On Tue, Oct 9, 2018 at 11:49 PM Vyacheslav Daradur > > >> wrote: > >> > >>> Great work guys, thanks! > >>> > >>> I've noticed TC fails in the build plan "Licenses Headers" which Igor > >>> have fixed already by excluding Doxyfile from checking. > >>> > >>> I've filled a ticket [1] and I'd suggest fixing the test in another > >>> way by adding the license header to Doxyfile. > >>> > >>> Igor, please, have a look at prepared PR [2] (tests passed [3]). > >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-9832 > >>> [2] https://github.com/apache/ignite/pull/4938/files > >>> [3] https://ci.ignite.apache.org/viewLog.html?buildId=2046206 > >>> On Tue, Oct 9, 2018 at 6:31 PM Igor Sapego wrote: > >>> > > >>> > As the seem to be everything OK with the code and tests and > >>> > no one had any comment for quite some time, I've merged the > >>> > PHP to Ignite's master. > >>> > > >>> > Great job, guys! > >>> > > >>> > > >>> > Best Regards, > >>> > Igor > >>> > > >>> > > >>> > On Wed, Sep 19, 2018 at 1:00 AM Prachi Garg > >>> wrote: > >>> > > >>> > > Hi Stephan, Alexey > >>> > > > >>> > > That's exactly what readme.io contains - installation > instructions, > >>> > > configuration, and examples for key-value, sql, etc. for thin > >>> clients. For > >>> > > example, see these documentation pages for Node.js (currently > hidden > >>> in the > >>> > > latest version of the doc) : > >>> > > > >>> > > https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client > >>> > > > >>> > > > >>> > https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-initialization-and-configuration > >>> > > > >>> https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-key-value > >>> > > https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-sql > >>> > > > >>> > https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-binary-types > >>> > > > https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-security > >>> > > > >>> > > This how Python and PHP thin clients will also be documented on > >>> readme.io > >>> > > > >>> > > -Prachi > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > On Tue, Sep 18, 2018 at 3:26 AM, Stepan Pilshchikov < > >>> > > pilshchikov@gmail.com> wrote: > >>> > > > >>> > > > > You know, I'm confused with all this documentation stuff... > >>> > > > > For nodejs client all docs were moved from the repo to > readme.io > >>> but > >>> > > > the > >>> > > > > readme.md keeps the installation instructions (duplicated with > >>> > > > > readme.io). Probably, that's ok. > >>> > > > > Will add similar short readme.md to the PHP PR. > >>> > > > > >>> > > > Its good > >>> > > > > >>> > > > What i think (and how it partially now): > >>> > > > All user documentation should be on readme.io (how to install, > >>> use it, > >>> > > > configurate, description for examples) > >>> > > > All developers documentation (how to release, how to start > develop) > >>> > > and(!) > >>> > > > basic description should be in repository > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > -- > >>> > > > Sent from: > http://apache-ignite-developers.2346864.n4.nabble.com/ > >>> > > > > >>> > > > >>> > >>> > >>> > >>> -- > >>> Best Regards, Vyacheslav D. > >>> > >> >
Re: Python thin client
Dmitry, One more thing Discover that Decimal data type can't be getting by others clients Make ticket with description: https://issues.apache.org/jira/browse/IGNITE-9950 Please, can you help to investigate this problem? ср, 17 окт. 2018 г. в 23:14, Stepan Pilschikov : > Dmitry, > > Great, now client works properly on all OS > Thanks > > I hope PR will be merged soon > > Igor, can please help with that? > > ср, 17 окт. 2018 г. в 20:48, Dmitry Melnichuk < > dmitry.melnic...@nobitlost.com>: > >> Stepan, >> >> Sadly, it was a C `long` data type size mismatch between Windows and >> other OSes. I investigated this issue and offered a pull request. >> >> https://github.com/apache/ignite/pull/5017 >> >> On 10/17/18 6:29 PM, Stepan Pilschikov wrote: >> > Dmitry, >> > >> > I've trying to use python thin client with Ignite 2.7 it dosn't work >> > Please help to investigate >> > Problem reproduced on several others machines >> > >> > Issue: >> > https://issues.apache.org/jira/browse/IGNITE-9908 >> > >> >
[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)
Re: Python thin client
Dmitry, Great, now client works properly on all OS Thanks I hope PR will be merged soon Igor, can please help with that? ср, 17 окт. 2018 г. в 20:48, Dmitry Melnichuk < dmitry.melnic...@nobitlost.com>: > Stepan, > > Sadly, it was a C `long` data type size mismatch between Windows and > other OSes. I investigated this issue and offered a pull request. > > https://github.com/apache/ignite/pull/5017 > > On 10/17/18 6:29 PM, Stepan Pilschikov wrote: > > Dmitry, > > > > I've trying to use python thin client with Ignite 2.7 it dosn't work > > Please help to investigate > > Problem reproduced on several others machines > > > > Issue: > > https://issues.apache.org/jira/browse/IGNITE-9908 > > >
Re: Python thin client
Dmitry, I've trying to use python thin client with Ignite 2.7 it dosn't work Please help to investigate Problem reproduced on several others machines Issue: https://issues.apache.org/jira/browse/IGNITE-9908 вт, 16 окт. 2018 г. в 4:36, Dmitry Melnichuk : > Igor, > > I do not have access to edit wiki pages, so please fill it. > > All the features are supported, except for: > > - Query API: ScanQuery with filter, > - Binary API: Get object in BinaryObject form, BinaryObject building, > - Additional Features: Best effort affinity, > - Type registration: Enum registration, Type name registration. > > On 10/15/18 9:17 PM, Igor Sapego wrote: > > Dmitry, > > > > Since Python thin client is now in master, can you please add it to our > > "Thin clients features" wiki page, so we can track the feature parity > > of our clients? Or just tell me which features are supported, so I can > fill > > it myself. > > > > [1] - > > https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features > > > > Best Regards, > > Igor > > >
[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&pageSize=10&cacheName=SQL_PUBLIC_TEST&qry=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-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] [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)
