[GitHub] ignite pull request #3988: IGNITE-5965 fix Flaky failure of GridServiceProce...

[andrewmed]

GitHub user andrewmed opened a pull request:

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

IGNITE-5965 fix Flaky failure of GridServiceProcessorMultiNodeConfigS…

Test fixed by decreasing connection timeout. Now 
GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology 
that should have failed earlier because of topology not being updated on nodes 
exit (cause of failures), succeeds but runs > 10 sec. This fix gives 200/200 
success rate, but I am not really sure if the approach is right. Needs reviewing

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrewmed/ignite IGNITE-5965

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3988.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3988


commit 82cf7f21c6532c6d4daa586e77a914b7049ac13a
Author: AMedvedev 
Date:   2018-05-12T21:02:16Z

IGNITE-5965 fix Flaky failure of 
GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology




---

SqlLine script and Java9

[Dmitriy Setrakyan]

Igniters,

Any reason SqlLine tool shipped with Ignite does not work with Java 9? This
is the error I got.


> *The version of JAVA installed in C:\Program Files\Java\jdk-9.0.1 is
> incorrect.*
> *Please point JAVA_HOME variable to installation of JDK 1.7 or JDK 1.8.**You
> can also download latest JDK at http://java.com/download
> .*


D.

Integration with JHipster

[Dmitriy Setrakyan]

Igniters,

Jhipster is a very popular Spring Boot + Angular framework. Many caching
frameworks integrate with it, including EhCache, Hazelcast, and Infinispan:

https://www.jhipster.tech/using-cache/

I think the integration is fairly simple and we should provide our own.

Thoughts?

D.

tracking SQL queries in 2.5

[Dmitriy Setrakyan]

Igniters,

I just noticed this horrible ticket:
https://issues.apache.org/jira/browse/IGNITE-6677

Apparently, a couple of releases back the community added support for
"CREATE TABLE" command and for some reason nobody checked that query
metrics on the created tables do not work.

Do we have any idea of what it would take to fix? If it is a simple fix, I
would like to squeeze it into 2.5 release.

D.

Re: PHP/Python versions for Thin Clients

[Dmitriy Setrakyan]

Pavel,

Can you suggest what would be the advantages and disadvantages of
supporting different versions?

D.

On Sat, May 12, 2018 at 7:21 AM, Pavel Petroshenko 
wrote:

> Igniters,
>
> Are there any strong opinions on which language versions should the Thin
> Clients written in Python and PHP support? Any objections to using PHP 7.1+
> and Python 3.5+?
>
> Thanks,
>
> p.
>

[GitHub] ignite pull request #3987: Refactor setter 'setFieldTypeName'

[andrey916]

GitHub user andrey916 opened a pull request:

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

Refactor setter 'setFieldTypeName'

Refactor setter 'setFieldTypeName' so that it actually refers to the field 
"fieldTypeName"

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrey916/ignite master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3987.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3987


commit d57548e96975fcac21beb51da1f6c241e966cb6e
Author: onufreyko.andrey 
Date:   2018-05-12T10:00:02Z

Refactor setter 'setFieldTypeName'




---

Re: NodeJS thin client: full API

[Alexey Kosenchuk]

Denis,

OK for the legacy docs.

Agree for the core docs (specs, common getting started, etc.).

But who/what does mandate that for totally all Ignite related docs?

Why do not follow an approach which many technologies/products follow? - 
maintain a centralized list of references to different client libs/SDKs 
(sometimes even alternative libs for the same language/platform).
It is possible to mention a "status" of every lib - is it "verified" 
(fully tested, fully documented, etc.) or just a prototype...
And it is not mandated that every lib must be developed/released under 
Apache...


The list could already have references to:
- java client
- .net client
- node.js client (as early access)
- Go client by Aleksandr S. (as prototype)
- Python client by Sergey K. (as prototype)

With this approach the docs naturally come together with a concrete 
client, but may be cross-referenced on readme.io for some clients as well...


-Alexey

12.05.2018 6:37, Denis Magda пишет:

Alexey,

Presently, Ignite hosts all the docs in readme.io without exception. It
means that once your contribution is accepted by the community the Node.JS
docs should be placed on readme.io.

You're right saying that we're planning to migrate from readme.io to
another documentation engine that would allow us storing doc sources in
Ignite repo. It might happen by 2.6 or might take longer.

Thus, we need to host the Node.JS docs on readme.io and edit them there
once your pull-request is merged (it means there wouldn't be docs' copy
added to Ignite repo for now). It's easy to move the docs to readme.io
which understands the standard markdown. I'll ask Prachi to assist here.

--
Denis

On Fri, May 11, 2018 at 1:45 PM, Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com> wrote:


Denis,


As for the docs, are you ready to bring them to readme.io? Just let me

know

and I'll be happy to arrange an account for you and discuss the

structure.

I remember some discussion regarding moving the docs from readme.io to
GitHub pages in 2.6.
No?

In any case, in my opinion, a readme near the code is a right primary
place for the docs for thin clients.
Is there any script/automation to convert .md to readme.io?
Or maybe just place a link from the readme.io to the repo readme?
Manual support of the same docs in two places seems not an effective
solution.

The docs for NodeJS client is ready for review in the repo.
The links and the installation procedure will have to be updated when the
client is integrated into the apache repo and released on npmjs.

-Alexey

PHP/Python versions for Thin Clients

[Pavel Petroshenko]

Igniters,

Are there any strong opinions on which language versions should the Thin
Clients written in Python and PHP support? Any objections to using PHP 7.1+
and Python 3.5+?

Thanks,

p.