Re: Signing off Ignite for export beyond the U.S.

Hi Denis, Info about Python, PHP, Node.JS thin clients: The clients itself do not contain any cryptographic code but use the features provided by the underlying platforms. Python client uses Python's SSL lib [1] which is a wrapper over OpenSSL [2]. Python 2.7 and Python 3.4 require OpenSSL 1.

Can't use array as a cache key from thin clients (ignite-9991)

The problem is reproduced with Java, NodeJs, PHP, Python thin clients. This seems the server's issue. Can an expert in the server have a look, please? The details are in the jira [1] Thanks, -Alexey [1] https://issues.apache.org/jira/browse/IGNITE-9991

Re: Thin clients all in one

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 Ob

Re: Thin clients all in one

s пт, 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, ever

Re: NodeJS thin client: full API

Done for NodeJs and PHP. Tests added as well. https://issues.apache.org/jira/browse/IGNITE-10022 https://github.com/apache/ignite/pull/5187 -Alexey 24.10.2018 17:41, Igor Sapego пишет: Pavel, Can we add a proper check and throw proper exception when trying to deserialize enum value? NPE does n

Re: Thin clients all in one

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?bui

Re: [RESULT] [VOTE] Apache Ignite 2.7.0 Release (RC2)

NodeJs client: -- Instruction - https://github.com/nobitlost/ignite/blob/ignite--docs/modules/platforms/nodejs/README.md#publish-ignite-nodejs-client-on-npmjscom-instruction Uploaded - https://www.npmjs.com/package/apache-ignite-client PHP client: --- Instruction - http

Re: Thin clients all in one

пт, 30 нояб. 2018 г. в 01:18, Alexey Kosenchuk mailto: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

NodeJS client: scripts for Ignite nodes start/stop, TeamCity integration

Folks, to finalize Jasmine tests for NodeJS thin client there is a need to understand: - what the tests should do in order to start/stop Ignite nodes before/during/after a test case? Are there any scripts available for that? - is there anything else the tests should do in order to integrate wit

NodeJS thin client: full API

Folks, The next version is ready - in the pull request [1] or directly in the repo [2]. The version includes: - full API - full implementation - examples - tests (cover the full API but might need to be updated/extended) - docs The details are in the readme [3] Regards, -Alexey [1] https://gi

Re: NodeJS thin client: full API

Not yet. Need a help with that. -Alexey 11.05.2018 10:58, Dmitriy Setrakyan пишет: This is great! Finally a native NodeJS client for Ignite. Alexey, in addition to the functional tests, were you able to perform any load tests? D. On Fri, May 11, 2018 at 12:07 AM, Alexey Kosenchuk

Re: NodeJS thin client: full API

I can see Timestamp. Are you planning to implement other types, e.g. Decimal, Guid? Best Regards, Igor On Fri, May 11, 2018 at 11:43 AM, Dmitriy Setrakyan wrote: On Fri, May 11, 2018 at 9:14 AM, Alexey Kosenchuk < alexey.kosenc...@nobitlost.com> wrote: Not yet. Need a help with that.

Re: NodeJS thin client: full API

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 re

Re: NodeJS thin client: full API

uest 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...@

Re: NodeJS thin client: full API

- Let's rename SqlDataProcessingExample.js to just SqlExample.js and describe it as an example that shows primary APIs to use with Ignite as with an SQL database. - Let's rename SqlQueryExample.js to SqlQueryEntiriesExample.js. Updated.

Re: Thin clients features wiki page

Hi Igor, "Get Binary Cache" (if it is about getting a complex object in a "binary" form, w/o deserialization) - is supported by NodeJS: BinaryObject is returned for a complex object if an app has not specified another JavaScript Object for deserialization. Maybe worth to add type registration

Re: Thin clients features wiki page

his page deserves to be moved to the readme.io. We'll do that once it's sorted out how to group the thin clients' documentation. -- Denis On Mon, May 14, 2018 at 12:39 PM, Alexey Kosenchuk < alexey.kosenc...@nobitlost.com> wrote: Hi Igor, "Get Binary Cache"

NodeJS client: npm publishing instruction

Denis, below is instruction how to publish/update npm module with Ignite NodeJS client on npmjs. Use it when you decide to publish the client. Another short instruction is how to generate the API spec using jsdoc. Pls place the instructions to appropriate locations. Thanks, -Alexey How to

PHP thin client

Hi folks, PHP thin client is ready for review. Jira with the scope of work - [1]. Implementation, examples, tests: PR - [2], repository - [3]. API spec - [4]. Readme (how to for the client, instructions for the examples and tests, etc.) - [5]. Regards, -Alexey [1] https://issues.apach

Re: PHP thin client

need to edit ignite/assembly/release-fabric-base.xml file and add appropriate "copy" commands. Search "cpp" or "dotnet" for example. Best Regards, Igor On Tue, Sep 4, 2018 at 3:21 PM Igor Sapego wrote: Great, I'll take a look Best Regards, Igor

Re: PHP thin client

2018 at 1:31 AM Alexey Kosenchuk < alexey.kosenc...@nobitlost.com> wrote: Hi Igor, thanks for the review. Pls see below... >> 1. Main page for documentation is empty. What is the main page for documentation? As wrote, the auto-generated API spec is here: https://rawgit.com

Re: PHP thin client

Hi Stepan, 1. Why exists second branches with all documentation? I mean they looks good together, why need to separate? Because finally the docs should not be in the repo (unfortunately) but on readme.io. There is a task for that: https://issues.apache.org/jira/browse/IGNITE-9523 Also, one

Re: PHP thin client

But now in PR we have no readme at all Agree with examples on readme.io, but other information (how to install, how to configurate, install from sources, basic description) may be in sources, it help a lot Or it also should be on readme.io? This question because in other platforms have readme exi

Ignite Thin clients for Node.js, Python, PHP

Hi All! Let us join the party, please ;) As we see, there is Binary Client Protocol to communicate with Ignite cluster and a concept of Thin (lightweight) client. If there are no objections or duplicated plans, we would like to develop Thin Client libs for: - Node.js - Python - PHP Please

Re: Ignite Thin clients for Node.js, Python, PHP

s, please share pointers that might be useful for Alexey. -- Denis On Mon, Feb 19, 2018 at 1:23 PM, Alexey Kosenchuk < alexey.kosenc...@nobitlost.com> wrote: Hi All! Let us join the party, please ;) As we see, there is Binary Client Protocol to communicate with Ignite cluster

Thin client / Binary protocol: questions

Folks, Designing node.js thin lib (IGNITE-) we have the following questions. Could you please have a look and clarify. Thanks, -Alexey - Supported standard types and their type codes. Are defined in the spec: https://apacheignite.readme.io/docs/binary-client-protocol#data-format But, a

Re: Apache Ignite 2.4+ Go language client

Hi Aleksandr, Seems an important missed part is complex objects support. And it's the most difficult part. Actually, it is not possible to implement it correctly basing on the current protocol spec only. If you decide to support it, you should either wait for an updated spec or ask for help.

Re: Apache Ignite 2.4+ Go language client

anks, Aleksandr From: Alexey Kosenchuk Sent: 25 апреля 2018 г. 12:05 To: dev@ignite.apache.org Subject: Re: Apache Ignite 2.4+ Go language client Hi Aleksandr, Seems an important missed part is complex objects support. And it's the most difficult part. Actually, it is not possible to implement

Re: Apache Ignite 2.4+ Go language client

@ignite.apache.org> *Subject: *RE: Apache Ignite 2.4+ Go language client Yes, it’s really challenge to write unit test for OP_QUERY_SQL. ))) Thanks, Aleksandr *From: *Alexey Kosenchuk <mailto:alexey.kosenc...@nobitlost.com> *Sent: *25 апреля 2018 г. 16:33 *To: *dev@ignite.apache.org &l

Re: Node.js client update: rev. 2

Hi Igor, in the newer version (will be available soon) getValues() is changed to getValue() which gives sequential per-element access. The API spec and the setup/run instructions are available with every version. Thanks, -Alexey 08.05.2018 15:14, Igor Sapego пишет: Hi, Pavel, I took a lo

[jira] [Created] (IGNITE-11540) Node.js thin client: best effort affinity

Alexey Kosenchuk created IGNITE-11540: - Summary: Node.js thin client: best effort affinity Key: IGNITE-11540 URL: https://issues.apache.org/jira/browse/IGNITE-11540 Project: Ignite Issue

[jira] [Created] (IGNITE-10022) JS, PHP thin clients: a more meaningful exception when ENUM type is not registered

Alexey Kosenchuk created IGNITE-10022: - Summary: JS, PHP thin clients: a more meaningful exception when ENUM type is not registered Key: IGNITE-10022 URL: https://issues.apache.org/jira/browse/IGNITE-10022

[jira] [Created] (IGNITE-9465) Node.js client: improve complex object flags processing

Alexey Kosenchuk created IGNITE-9465: Summary: Node.js client: improve complex object flags processing Key: IGNITE-9465 URL: https://issues.apache.org/jira/browse/IGNITE-9465 Project: Ignite

[jira] [Created] (IGNITE-7777) Thin Client lib: Node.js

Alexey Kosenchuk created IGNITE-: Summary: Thin Client lib: Node.js Key: IGNITE- URL: https://issues.apache.org/jira/browse/IGNITE- Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-7782) Thin Client lib: Python

Alexey Kosenchuk created IGNITE-7782: Summary: Thin Client lib: Python Key: IGNITE-7782 URL: https://issues.apache.org/jira/browse/IGNITE-7782 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-7783) Thin Client lib: PHP

Alexey Kosenchuk created IGNITE-7783: Summary: Thin Client lib: PHP Key: IGNITE-7783 URL: https://issues.apache.org/jira/browse/IGNITE-7783 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-8014) Node.js client: basic/minimal version

Alexey Kosenchuk created IGNITE-8014: Summary: Node.js client: basic/minimal version Key: IGNITE-8014 URL: https://issues.apache.org/jira/browse/IGNITE-8014 Project: Ignite Issue Type

[jira] [Created] (IGNITE-8039) Binary Client Protocol spec: data types/format clarifications

Alexey Kosenchuk created IGNITE-8039: Summary: Binary Client Protocol spec: data types/format clarifications Key: IGNITE-8039 URL: https://issues.apache.org/jira/browse/IGNITE-8039 Project

[jira] [Created] (IGNITE-8212) Binary Client Protocol spec: Key-Value Queries clarifications

Alexey Kosenchuk created IGNITE-8212: Summary: Binary Client Protocol spec: Key-Value Queries clarifications Key: IGNITE-8212 URL: https://issues.apache.org/jira/browse/IGNITE-8212 Project

[jira] [Created] (IGNITE-8411) Binary Client Protocol spec: other parts clarifications

Alexey Kosenchuk created IGNITE-8411: Summary: Binary Client Protocol spec: other parts clarifications Key: IGNITE-8411 URL: https://issues.apache.org/jira/browse/IGNITE-8411 Project: Ignite