Great work
Best Regards,
Igor
On Wed, Nov 16, 2022 at 1:50 PM Ivan Daschinsky
wrote:
> The Apache Ignite Community is pleased to announce the release of
> Apache IGNITE python thin client (pyignite) 0.6.0.
>
> This new release is mostly the maintenance one. However, there ar
The Apache Ignite Community is pleased to announce the release of
Apache IGNITE python thin client (pyignite) 0.6.0.
This new release is mostly the maintenance one. However, there are some new
important features and fixes:
1. Fixed non-intuitive automatically setting of flag use_ssl when the
The Apache Ignite Community is pleased to announce the release of
Apache IGNITE python thin client (pyignite) 0.5.2.
This new release of python thin client contains bugfixes and it is
recommended to update.
Namely:
1. Fixed incorrect partial read from socket in sync client
1. Fixed nested object
The Apache Ignite Community is pleased to announce the release of
Apache IGNITE python thin client (pyignite) 0.5.1.
This new release of python thin client contains bugfixes and a few new
features
Namely:
1. Event listeners to connection events and query events
2. Optional client's side hand
The Apache Ignite Community is pleased to announce the release of
Apache IGNITE python thin client (pyignite) 0.5.0.
This new release of python thin client contains new cool features:
Namely:
1. Transactions support
2. Expiry policy support.
3. Performance improvement of asyncio version
4. Few
3:49 Ivan Daschinsky :
> >> >
> >> > > Igor, I suppose that you are probably right. But there is no need to
> >> > > notice or deprecate something. This functionality is not released yet
> >> > >
> >> > > вт, 15 июн. 2021 г.,
ht. But there is no need to
>> > > notice or deprecate something. This functionality is not released yet
>> > >
>> > > вт, 15 июн. 2021 г., 23:41 Igor Sapego :
>> > >
>> > >> Hi Igniters,
>> > >>
>> > >> I
gt;
> > > Igor, I suppose that you are probably right. But there is no need to
> > > notice or deprecate something. This functionality is not released yet
> > >
> > > вт, 15 июн. 2021 г., 23:41 Igor Sapego :
> > >
> > >> Hi Igniters,
> >
ht. But there is no need to
> > notice or deprecate something. This functionality is not released yet
> >
> > вт, 15 июн. 2021 г., 23:41 Igor Sapego :
> >
> >> Hi Igniters,
> >>
> >> I've noticed a weird behaviour of python thin client. In those pla
., 23:49 Ivan Daschinsky :
> Igor, I suppose that you are probably right. But there is no need to
> notice or deprecate something. This functionality is not released yet
>
> вт, 15 июн. 2021 г., 23:41 Igor Sapego :
>
>> Hi Igniters,
>>
>> I've noticed a weird beh
Igor, I suppose that you are probably right. But there is no need to notice
or deprecate something. This functionality is not released yet
вт, 15 июн. 2021 г., 23:41 Igor Sapego :
> Hi Igniters,
>
> I've noticed a weird behaviour of python thin client. In those places where
> w
Hi Igniters,
I've noticed a weird behaviour of python thin client. In those places where
we have
timeouts or any other parameters that take time in some places we treat it
like integer
number of milliseconds, in others it can take both floats (as a number of
seconds)
and ints (numb
should add travis integration per commit and pr. Tests could
>>>> be run
>>>> > > against latest dockered image of ignite
>>>> > > 3. There should be ability to run tests against multiple pythons on
>>>> TC
>>>> > > 4. For th
ess, travis should be the first
>> > option.
>> > > TC suite should be used only to check that compatibility is not broken
>> > > and when new functionality is developed (rare case).
>> > >
>> > > I've prepared fix [3], yo
The Apache Ignite Community is pleased to announce the release of
Apache IGNITE python thin client (pyignite) 0.4.0.
This new release of python thin client contains a lot of changes.
Namely:
1. Partition awareness support.
2. Asyncio support.
3. Numerous performance fixes.
4. Numerous bug fixes
Ivan Daschinsky created IGNITE-14595:
Summary: ExpiryPolicy support to python thin client
Key: IGNITE-14595
URL: https://issues.apache.org/jira/browse/IGNITE-14595
Project: Ignite
Issue
Igniters!
I suppose it is time to finally release new version of python thin client
Recently, multiple bug fixes, features and other goodies have been
implemented.
For example:
1. Partition awareness.
2. Asyncio support.
3. Cluster API support.
4. Multiple performance improvements, especially for
Igor Sapego created IGNITE-14465:
Summary: Add the ability to activate the cluster via the Python
thin client
Key: IGNITE-14465
URL: https://issues.apache.org/jira/browse/IGNITE-14465
Project: Ignite
Ivan Daschinskiy created IGNITE-14429:
-
Summary: Python thin client cache.get_size works not as expected
and PeekModes are incorrect.
Key: IGNITE-14429
URL: https://issues.apache.org/jira/browse/IGNITE-14429
Ivan Daschinskiy created IGNITE-14240:
-
Summary: Handle authentication error on python thin client properly
Key: IGNITE-14240
URL: https://issues.apache.org/jira/browse/IGNITE-14240
Project
Ivan Daschinskiy created IGNITE-14186:
-
Summary: Develop C module for python thin client to speedup
hashcode calculation
Key: IGNITE-14186
URL: https://issues.apache.org/jira/browse/IGNITE-14186
Igor Sapego created IGNITE-14058:
Summary: Python Thin client: get boolean type return integers
Key: IGNITE-14058
URL: https://issues.apache.org/jira/browse/IGNITE-14058
Project: Ignite
for travis. It
> uses
> > > tox [5], the most common tool to run tests in multiple environments.
> > > There are few environments set up in tox.ini -- with and without
> docker,
> > > with or without ssl, etc. This helped a lot
> > > to setup travis CI
etc. This helped a lot
> > to setup travis CI build (you can see in commits list of PR) and simplify
> > run tests for developers. Also docker-compose was introduced
> > to help python thin client developers.
> >
> > But I need some assistance for TC:
> > 1. There i
Ivan Daschinskiy created IGNITE-13967:
-
Summary: Refactor and imrpove performance of python thin client
marshaller
Key: IGNITE-13967
URL: https://issues.apache.org/jira/browse/IGNITE-13967
mmon tool to run tests in multiple environments.
> There are few environments set up in tox.ini -- with and without docker,
> with or without ssl, etc. This helped a lot
> to setup travis CI build (you can see in commits list of PR) and simplify
> run tests for developers. Also docker-comp
d (you can see in commits list of PR) and simplify
run tests for developers. Also docker-compose was introduced
to help python thin client developers.
But I need some assistance for TC:
1. There is outdated python setuptools on TC agents, so tests cannot be run
with updated pytest etc.
2. Multip
ivandasch commented on a change in pull request #1:
URL:
https://github.com/apache/ignite-python-thin-client/pull/1#discussion_r548627959
##
File path: docker-compose.yml
##
@@ -0,0 +1,34 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor
isapego commented on a change in pull request #1:
URL:
https://github.com/apache/ignite-python-thin-client/pull/1#discussion_r548558576
##
File path: docker-compose.yml
##
@@ -0,0 +1,34 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor
ivandasch opened a new pull request #1:
URL: https://github.com/apache/ignite-python-thin-client/pull/1
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
Ivan Daschinskiy created IGNITE-13903:
-
Summary: Python thin client tests automation.
Key: IGNITE-13903
URL: https://issues.apache.org/jira/browse/IGNITE-13903
Project: Ignite
Issue Type
Igor Sapego created IGNITE-13863:
Summary: Python thin client hangs when object has Boolean field
Key: IGNITE-13863
URL: https://issues.apache.org/jira/browse/IGNITE-13863
Project: Ignite
Archita Sukhwani created IGNITE-13862:
-
Summary: Python Thin Client: put_all operation on a huge
dictionary (say 1 keys) results in connection timeout, same happens with
multiple consecutive put operations using a for loop unless a sleep
Igor Sapego created IGNITE-13735:
Summary: Move Python thin client to a separate git repo
Key: IGNITE-13735
URL: https://issues.apache.org/jira/browse/IGNITE-13735
Project: Ignite
Issue Type
Hello, Igniters.
JFYI
Currently, we don’t test SSL mode for Python Thin Client.
I and Andrey Kuznetsov are working on IGNITE-12718 [1] «Python Thin Client add
an ability to specify keyfile password»
To test existed SSL support and new feature I need to update «ThinClient:
Python» job [2]
I
Stephen Darlington created IGNITE-12867:
---
Summary: Python thin client: support for DB-API
Key: IGNITE-12867
URL: https://issues.apache.org/jira/browse/IGNITE-12867
Project: Ignite
Andrey Kuznetsov created IGNITE-12718:
-
Summary: Python Thin Client: add an ability to specify keyfile
password
Key: IGNITE-12718
URL: https://issues.apache.org/jira/browse/IGNITE-12718
Project
Denis Mekhanikov created IGNITE-11854:
-
Summary: Serialization of arrays of primitives in python thin
client is not optimal
Key: IGNITE-11854
URL: https://issues.apache.org/jira/browse/IGNITE-11854
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
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
Dmitry Melnichuk created IGNITE-11303:
-
Summary: Python thin client: best effort affinity
Key: IGNITE-11303
URL: https://issues.apache.org/jira/browse/IGNITE-11303
Project: Ignite
Issue
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
> >> 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.
> >>>
&g
e/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
s 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,
>> >
>&
ows 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
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 I
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
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
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/disp
Hi,
I've just merged Python thin client to the master and ignite-2.7
Also, I like how the python's results improved and now are comparable to
node.js.
Great job, guys!
Best Regards,
Igor
On Sat, Oct 13, 2018 at 3:53 PM Степан Пильщиков
wrote:
> Hi
>
> Made new run an
Hi
Made new run and client definitely become faster
I think its right direction for improvements
Also rerun java bench with compiler=none option
All results you can get in https://issues.apache.org/jira/browse/IGNITE-9824
(last comment)
сб, 13 окт. 2018 г. в 4:56, Pavel Petroshenko :
> Hi Step
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
Igor,
I fixed my files.
Dmitry
On 10/13/18 12:14 AM, Igor Sapego wrote:
Dmitry,
I've run the tests and it appears that there are a lot of files without
Apache
licenses in Python client: [1] (See Unapproved licenses list).
Can you either add headers or exclude file from the check, if you can
Dmitry,
I've run the tests and it appears that there are a lot of files without
Apache
licenses in Python client: [1] (See Unapproved licenses list).
Can you either add headers or exclude file from the check, if you can not
add one? I.e. to this list: [2]
[1] -
https://ci.ignite.apache.org/repos
Igor Sapego created IGNITE-9852:
---
Summary: Create TeamCity suite for Python thin client
Key: IGNITE-9852
URL: https://issues.apache.org/jira/browse/IGNITE-9852
Project: Ignite
Issue Type: Task
Ok, I've filed a ticket [1] for the performance investigation and targeted
it to 2.8. Feel free to assign it to yourself.
I'm going to merge the ticket to master and ignite-2.7 branches by the
end of the week, if no one have any objections.
[1] - https://issues.apache.org/jira/browse/IGNITE-9850
Stepan,
Thank you for answering my question and for the updated results.
I have ran the profiler (cProfile) against the benchmark code you
provided and have not found any particular bottleneck. One cycle took me
434 μs, which is the same order of magnitude as your result.
I will need more ti
Dmitry,
pip install -e from latest sources
On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk,
wrote:
> Stepan!
>
> Please tell me one thing about how you created the environment for your
> benchmarks, namely: how did you install the Python client. Did you just
> do `pip install pyignite`, or did you
Stepan!
Please tell me one thing about how you created the environment for your
benchmarks, namely: how did you install the Python client. Did you just
do `pip install pyignite`, or did you pull my working branch from the
downstream repository and did `pip install -e
ignite/modules/platforms/
Dmitry,
Thanks for review
Agree with all suggestions.
Made and run new benches without any redundant operations (prints, time
calculation), only with "put" in "while true" cycle (almost)
Case description, environment, results and code in ticket
https://issues.apache.org/jira/browse/IGNITE-9824 (
Stepan!
Can you please update the benchmarks based on my suggestions earlier in
this thread: use a cleaner time profiling for the loop, remove
unnecessary operations (string formatting, rounding operations), stick
to the primitive int value for put operations (agree with Vladimir,
let's keep
Hi Dmitry,
I agree with your comments on benchmarking code. As more fair alternative
we may measure time of loading N elements into the cache, so that it will
be necessary to call time() only twice. However, provided that we have real
network here, and according to numbers one PUT in Python client
Hi, Stepan!
I looked at the benchmark code and the overall methodics, discussed it
with fellow programmers, and came up with basically two remarks.
First of all, I think, the key for the good (or, at least,
unobjectionable) measurement is to isolate the object being measured
from the influen
Hi, all
Tried to compare new thin client performance and made similar benchmarks for
each one
And result not so good for python
Ticket with results and bench code:
https://issues.apache.org/jira/browse/IGNITE-9824
Py code src:
https://gist.github.com/pilshchikov/8aff4e30d83f8bac20c5a4a9c3917abb
>
>> On Fri, Sep 21, 2018 at 3:04 PM Prachi Garg wrote:
>>
>> Hi Dmitry,
>>
>> Thank you for taking the time to explain me everything in such detail :)
>>
>> I am trying to do this because I have to document. In general, I am
>> assuming that
g in such detail :)
>
> I am trying to do this because I have to document. In general, I am
> assuming that a Python thin client user would already have Python installed
> and be using it. So, I would not suggest adding any disclaimers regarding
> Python installation.
>
> The exam
Hi Dmitry,
Thank you for taking the time to explain me everything in such detail :)
I am trying to do this because I have to document. In general, I am
assuming that a Python thin client user would already have Python installed
and be using it. So, I would not suggest adding any disclaimers
t; Also, the installation instruction you have provided are for unix users.
> What are the installation instructions for Windows users?
I tried to be OS-agnostic in the docs. Please tell me, what part of
my instructions does not work on Windows.
On 9/20/18 7:32 AM, Prachi Gar
t;
> > Also, the installation instruction you have provided are for unix users.
> > What are the installation instructions for Windows users?
>
> I tried to be OS-agnostic in the docs. Please tell me, what part of my
> instructions does not work on Windows.
>
>
for unix users.
> What are the installation instructions for Windows users?
I tried to be OS-agnostic in the docs. Please tell me, what part of my
instructions does not work on Windows.
On 9/20/18 7:32 AM, Prachi Garg wrote:
Hi Dmitry,
I tried to follow the instructions for the Python thin
Hi Dmitry,
I tried to follow the instructions for the Python thin client installation
[1].
~$ pip install pyignite
Requirement already satisfied: pyignite in
./Downloads/ignite-python/modules/platforms/python (0.3.1)
Requirement already satisfied: typing==3.6.4 in
/Library/Frameworks
Hi Dmitry,
Not sure if you are aware but all documentation for the thin clients will
be moved to readme.io. Here is the ticket for Python thin clients -
https://issues.apache.org/jira/browse/IGNITE-9522
I am already working on it. So if you make any changes to the docs in your
repo, please let me
Great job.
Best Regards,
Igor
On Tue, Sep 18, 2018 at 11:35 AM Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:
> Igor,
>
> All examples are in 'ignite/modules/platforms/python/examples'.
>
> I put examples in separate Python files mostly to be able to
> automatically confirm their ope
Igor,
All examples are in 'ignite/modules/platforms/python/examples'.
I put examples in separate Python files mostly to be able to
automatically confirm their operability. All the lengthy explanations
and cross-references are in the main documentation:
https://apache-ignite-binary-protocol-c
Dmitry,
Sorry, I was not clear enough. What I mean is that Ignite distributed
by both source and binary releases. Binary releases contain platforms
code, which is needed to write your own application in the language,
but does not contain developer stuff, such as tests, documentation
generating scr
Igor,
I am in doubt here because I am not fully comprehend the meaning of
"binary release". But if it is somehow related to the "distribution"
thing, I would dare to suggest the following options:
1. Copy nothing. Just do
```
$ python setup.py bdist_wheel
$ twine upload dist/*
```
during th
Ok, good.
Now, what is about installation? Which directories/files
need to be copied to ignite's binary release?
Best Regards,
Igor
On Fri, Sep 14, 2018 at 4:51 AM Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:
> Igor,
>
> The commented code (lines 95-96) gives an error if executed.
Igor,
The commented code (lines 95-96) gives an error if executed. The error
is stated just below, in lines 98-100. It is explained here:
https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/examples.html#create
I found out by trial and error that a cache, created with SQL DD
Ok, now everything's running.
API looks good to me. I have a single question about example code:
What these comments are for - [1]?
[1] -
https://github.com/nobitlost/ignite/blob/ignite-7782/modules/platforms/python/examples/create_binary.py#L95
Best Regards,
Igor
On Thu, Sep 13, 2018 at 12:52
Igor,
Yes, it's my bad, sorry. Just merged the Ignite master with my branch.
On 9/12/18 8:47 PM, Igor Sapego wrote:
Pavel,
Yes, I did. I tried completely clean environment, followed the same
steps and got the same error. Then I removed attr, and out of sudden
everything started working.
Dmitry
Pavel,
Yes, I did. I tried completely clean environment, followed the same
steps and got the same error. Then I removed attr, and out of sudden
everything started working.
Dmitry,
Thanks, now it's more clear:
Handshake error: Unsupported version. Server expects binary protocol
version 1.1.0. Clien
Igor,
I have just commited an improvment to the HandshakeError message
generation algorithm. I hope it is now easier to understand what expects
what in case of binary protocol version mismatch.
Thank you for pointing this out.
On 9/12/18 2:13 AM, Igor Sapego wrote:
I managed to start tests,
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
I managed to start tests, and now I'm getting the following message:
pyignite.exceptions.HandshakeError: Handshake error: Unsupported
version. Expected protocol version: 1.1.0.
It would be useful to print "Unexpected version" itself, because I can
not understand what is the issue.
Best Regards,
Igor,
I literally followed the steps you describe, but unfortunately could not
reproduce the error.
The only clue I got is that your site-packages already have the newer
version of attrs (18.2.0 against 18.1.0 as of pyignite requirements).
But this should not be an issue, since pytest-runner
Prachi Garg created IGNITE-9522:
---
Summary: Document Python thin client
Key: IGNITE-9522
URL: https://issues.apache.org/jira/browse/IGNITE-9522
Project: Ignite
Issue Type: Task
Guys, I've cloned your repository, run pip3 install -e .
then run pip3 install -r requirements/* over all the requirements,
and finally run python ./setup.py pytest, but get the following output:
running pytest
Searching for attrs==18.1.0
Best match: attrs 18.1.0
Using /home/isapego/.local/lib/py
Got it, sounds good!
On Tue, Sep 4, 2018 at 10:54 AM, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:
> Dmitriy,
>
> It would be quite messy to implement with Python modular system.
>
> First of all, Python 2 and Python 3 are different languages with a small
> common subset of syntax ru
Dmitriy,
It would be quite messy to implement with Python modular system.
First of all, Python 2 and Python 3 are different languages with a small
common subset of syntax rules. That's why what we see in a stack trace
is a syntax error, and not a “missing feature” error.
Second, there is no
Dmitriy,
setuptools sounds like an installation step. Does it make sense to add a
check during startup of a client?
D.
On Tue, Sep 4, 2018 at 7:25 AM, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:
> Nikolay,
>
> There is indeed a feature in `setuptools` I just learned about, which
>
Nikolay,
There is indeed a feature in `setuptools` I just learned about, which
would help in this case (and I believe the case you demonstrated can be
quite typical, thank you for pointing it out). It gives user a clever
message in the end of a stack trace like
> UnsupportedPythonVersion: py
00, Dmitry Melnichuk пишет:
> Hello, Nikolay!
>
> Thank you for your interest in Python thin client.
>
> The traceback suggests that you using Python 2.7. Unfortunately, my
> client supports only Python versions 3.4 and later.
>
> Since you are using the latest Ubuntu OS, chance
Hello, Nikolay!
Thank you for your interest in Python thin client.
The traceback suggests that you using Python 2.7. Unfortunately, my
client supports only Python versions 3.4 and later.
Since you are using the latest Ubuntu OS, chances are you already have a
recent Python 3 installed. Try
Hello, Dmitry.
I tried to build your lib locally and it failed.
Error message and pip version are below.
Seems, we have to fix developer instructions.
Do we need specific version of pip or something?
I tried to use default versions.
I using Ubuntu Linux.
dragon:~/src/ignite/modules/platforms/py
Hello, Igniters!
Please review my work on Ignite thin client library written in Python 3.
Pull request:
https://github.com/apache/ignite/pull/4278
Jira issue with initial proposal:
https://issues.apache.org/jira/browse/IGNITE-7782
The documentation is temporarily available at:
https://apache-i
96 matches
Mail list logo
