eference [1]. @Alexey Kosenchuk , @Pavel
>Petroshenko could you please help with this? I
>have a feeling you shared this instruction before, but it might have been
>lost in dev list archives. Apologize for that.
>- Python, NodeJS and PHP API Docs need to be uploaded
Igor, I can give it a look.
Thomas, can you please create a Pull Request for your changes so that it's
easier to review and discuss them?
Thanks!
- p.
On Wed, Jan 23, 2019 at 2:19 AM Igor Sapego wrote:
> Great job!
>
> Forwarding to devlist.
>
> Are there Node.js guys that can take a look?
>
Pavel Petroshenko created IGNITE-10230:
--
Summary: Putting collection of timestamps fails on python thin
client
Key: IGNITE-10230
URL: https://issues.apache.org/jira/browse/IGNITE-10230
Project
gor
>
>
> On Wed, Oct 24, 2018 at 5:34 PM Pavel Petroshenko
> wrote:
>
> > Hi Stepan,
> >
> > Nodejs and PHP clients do not support enum type registration (and hence
> no
> > tests). So enum type must be registered from somewhere else in order to
> be
>
Hi Stepan,
Nodejs and PHP clients do not support enum type registration (and hence no
tests). So enum type must be registered from somewhere else in order to be
put or get from the Thin clients.
If you register the type say from Java, then put/get for Enum values should
work from the Thin clients
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
wrote:
> Alexey,
>
> Hi
>
> I'm trying to use PHP client for some times and discover one problem with
> DATA and TIMESTAMP data types
Hi Stepan,
Re your performance questions.
Firstly, please pull out the latest sources from the ignite-7782 branch as
it has some performance optimizations recently implemented.
Secondly, Hotspot is a pretty advanced dynamic adaptive compiler and it's
not fair to compare it to a purely interprete
Pavel Petroshenko created IGNITE-9758:
-
Summary: Document data injection via the REST API
Key: IGNITE-9758
URL: https://issues.apache.org/jira/browse/IGNITE-9758
Project: Ignite
Issue
gt;
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 1 окт. 2018 г. в 3:51, Pavel Petroshenko :
>
> > Igniters,
> >
> > Is there a way to put user defined objects (in BinaryObject or whatever
> > another format) via the REST APIs [1]? According to the docs it
Igniters,
Is there a way to put user defined objects (in BinaryObject or whatever
another format) via the REST APIs [1]? According to the docs it's not
supported, but I wonder if by any chance it's implemented somewhere and is
just not officially released yet...
Thanks,
Pavel
[1] https://apachei
Hi Igor,
Did you have to do anything special to make the tests eventually run?
p.
On Tue, Sep 11, 2018 at 9:13 AM, Igor Sapego wrote:
> I managed to start tests, and now I'm getting the following message:
>
> pyignite.exceptions.HandshakeError: Handshake error: Unsupported
> version. Expected
8 в 21:49 +0300, Nikolay Izhikov пишет:
> > PR is fully ready.
> >
> > I'm waiting final approve from Vladimir Ozerov.
> >
> > Hope, This will be merged in master on Monday :).
> >
> > В Пт, 24/08/2018 в 11:47 -0700, Pavel Petroshenko пишет:
> > &
; I'm edit thin protocol in that ticket.
> I can't support changes in Python and PHP clients, because, they are not
> merged in master, yet.
> Write me, If you have any questions about new fields.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-6055
>
> В Чт, 23/
Hi Nikolay,
Python [1], PHP [2], and Node.js [3] thin clients will get into the release.
Thanks,
p.
[1] https://jira.apache.org/jira/browse/IGNITE-7782
[2] https://jira.apache.org/jira/browse/IGNITE-7783
[3] https://jira.apache.org/jira/browse/IGNITE-
On Tue, Aug 21, 2018 at 12:20 PM, Dmit
Yes, already looking...
Pavel
On Wed, Aug 15, 2018 at 5:39 PM, Denis Magda wrote:
> Pavel,
>
> Could you please look into this issue? Guess we've got the first Node.JS
> user even before it was officially released.
>
> --
> Denis
>
> -- Forwarded message -
> From: Eran Betzalel
Hi Denis, Nikolay,
The proposed 2.7 release timing sounds reasonable to me.
Python [1], PHP [2], and Node.js [3] thin clients should take the train.
p.
[1] https://jira.apache.org/jira/browse/IGNITE-7782
[2] https://jira.apache.org/jira/browse/IGNITE-7783
[3] https://jira.apache.org/jira/browse/
Hi Denis,
There are no "binaries" for Node.js and Python that you can download. These
Thin Clients are distributed and installed by a package management system
(npm, pip): which resolves all the dependencies and deploys necessary
components to the appropriate system locations. So instead of downlo
obitlost/ignite/tree/master/modules/platforms/nodejs
On Thu, Jun 7, 2018 at 5:05 PM, Pavel Petroshenko
wrote:
> Hi Ivan,
>
> Thanks for taking care of this. I will give the scripts a try and get back
> to you if any questions.
>
> Could you please update the JIRA ticket [1] so
Thank, Vladimir.
Denis, confirming, AI 2.5 is not supported.
However, all the tests and examples happily pass on the latest master (as
of today). So please use it for testing.
Thanks,
p.
On Thu, Jun 7, 2018 at 12:33 AM, Vladimir Ozerov
wrote:
> Denis,
>
> No, AI 2.5 is not supported.
>
> чт,
018 г. в 20:05, Denis Magda :
>
> > Hi Pavel,
> >
> > Thanks for prompt improvements. I'll check them this week.
> >
> > --
> > Denis
> >
> > On Sun, May 27, 2018 at 5:04 PM, Pavel Petroshenko <
> pa...@petroshenko.com>
> &
Hi Igor,
That's a great idea! This would make the client developers' lives much
easier.
Pavel
On Mon, Jun 4, 2018 at 3:54 AM, Igor Sapego wrote:
> Igniters,
>
> Currently, our thin client specification is kept on readme.io [1].
> However, sometimes to introduce new features while keeping
> bac
Hi Denis,
Thanks for your feedback on the documentation! I addressed all your
comments from https://issues.apache.org/jira/browse/IGNITE-8589.
Please let me know if you have any questions.
Thanks,
p.
On Thu, May 24, 2018 at 12:42 PM, Pavel Petroshenko
wrote:
> Hi Denis,
>
> That
>
> Denis, Pavel, what do you think?
>
> D.
>
> On Thu, May 24, 2018 at 2:11 PM, Pavel Petroshenko
> wrote:
>
> > As Denis said, there is no need to download the entire Ignite repo to
> > install the client. Once published the client is going to be installed
om there without
> touching the whole Ignite binary release.
>
> However, those who download the whole Ignite binary distribution will find
> node.js there (as well as .NET, C++, JDBC and ODBC).
>
> --
> Denis
>
> On Thu, May 24, 2018 at 1:06 PM, Dmitriy Setrakyan
> wro
Hi Denis,
That's a good point, thanks. This should be a part of the "Usage" section.
I'll follow up in JIRA.
p.
On Thu, May 24, 2018 at 10:49 AM, Denis Magda wrote:
> Pavel,
>
> Recalled that we've not described how to authenticate and set up SSL from
> the client side. Please consider this fo
Fair enough. Consistency with the other clients is a good argument.
p.
On Thu, May 24, 2018 at 11:44 AM, Dmitriy Setrakyan
wrote:
> On Thu, May 24, 2018 at 11:42 AM, Igor Sapego wrote:
>
> > Well, all other clients have the same version as Ignite.
> > Are there any reasons to make a Node.js cl
; 1. Sounds OK for me.
> 2. Since Node.js client is going to be included in Ignite releases,
> I guess it make sense to align its version with the version of
> Ignite, i.e. 2.6, etc...
>
> Best Regards,
> Igor
>
> On Thu, May 24, 2018 at 9:02 AM, Pavel Petroshen
Igniters,
I'm finalizing the docs (with regards to installation instructions) for the
Node.js Thin Client at readme.io. And I've got a couple of questions.
1. Does the name "apache-ignite-client" for the Node.js Thin Client
npm module sound good to everyone? This name will be used to install the
It works, thanks Vitaliy!
p.
On Sun, May 20, 2018 at 1:16 PM, Vitaliy Osipov
wrote:
> Pavel. Hi
>
> The necessary rights have been added. Check please.
>
> On 19 May 2018 at 01:48, Pavel Petroshenko wrote:
>
>> Thank you, Denis! I need to have a role to be abl
s
>
>
> On Fri, May 18, 2018 at 9:44 AM, Pavel Petroshenko
> wrote:
>
> > Hi,
> >
> > Can anyone please grant TC permissions to manage jobs (reorder, etc) to:
> >
> > ekaterina.vergizova
> > alexey.kosenchuk
> > pavel.petroshenko
> >
> > Thanks!
> > p.
> >
>
Hi,
Can anyone please grant TC permissions to manage jobs (reorder, etc) to:
ekaterina.vergizova
alexey.kosenchuk
pavel.petroshenko
Thanks!
p.
-2017/
On Sat, May 12, 2018 at 6:21 AM, Dmitriy Setrakyan
wrote:
> 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:
>
> &g
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.
Igniters,
Is the schedule for v2.6 finalized already? If I want a feature/component
I'm working on to get into the release, when should it be (code/feature)
frozen? Thanks.
p.
th you separately.
>-
>
>
> [1]
> https://github.com/nobitlost/ignite/blob/master/modules/
> clients/nodejs/examples/SqlQueryExample.js#L68
> [2] https://apacheignite-sql.readme.io/docs/getting-started
>
> --
> Denis
>
> On Wed, Apr 11, 2018 at 6:45 PM, Pavel
Igniters,
Just to give you an update on the next iteration of the Ignite Node.js thin
client implementation.
The second iteration is available for review/testing.
The changes are available in the pull request [1] or directly from our
repository [2].
The short README file [3] covers:
- the list
>From our point of view option (3) makes the most sense (if it works for the
ASF, as Denis pointed out).
Option (2) implies too much overhead, which may not be worth it.
(1) is the least convenient approach for such independent projects as
Client libs, however it's clear where it comes from. So it
Igniters,
Just to keep everyone posted, we've filed the issue to improve the Binary
Client Protocol specification:
https://issues.apache.org/jira/browse/IGNITE-8039
We'll keep it updated with more findings.
If someone can help with cleaning it up and addressing the questions in the
spec, that w
38 matches
Mail list logo