oo big and parsing of such a
> big response seems to be really slow.
> 2. Use ignite odbc driver and pyodbc over it. Both of them work pretty
> well.
>
> вт, 14 мар. 2023 г. в 14:10, Dren Butković :
>
>>
>> Ignite and py client versions:
>>
>> - Apache Ign
Ignite and py client versions:
- Apache Ignite 2.13.0
- pyignite 0.5.2
On Tue, Mar 14, 2023 at 11:46 AM Zhenya Stanilovsky via user <
user@ignite.apache.org> wrote:
> Hi, plz append ignite and py client versions.
>
>
> Hi,
>
> I made a speed comparison of retrieving data from Apache Ignite
Hi,
I made a speed comparison of retrieving data from Apache Ignite using
several methods. All records are in one table, I did not use any WHERE
condition, only a SELECT * FROM TABLE XYZ LIMIT 2.
Test results are:
Apache Ignite
- Apache Ignite REST API - 0.52 seconds
- JDBC - 4
Example of timestamp data, difference is in "," after year.
Ignite 2.7.6 Java 8 ->"Sep 18, 2019 12:57:35 PM"
Ignite 2.13 Java 11 ->"Aug 31, 2022, 12:43:44 PM"
On Thu, Sep 1, 2022 at 9:03 AM Dren Butković
wrote:
> Hi,
>
> I have u
regards
Dren Butković
Hi,
I tested two Python Thin client modules and they do not give the same
connection info.
Python code and exaples:
from pyignite import Client
nodes = [('192.168.50.106', 10800)]
ignite_client = Client(username='ignite', password='ignite', use_ssl=False)
ignite_client.connect(nodes)
Hi,
random string insert/update test fails from time to time.
Tested with python 3.6 , pyignite and Ignite 2.8.0
On Ignite 2.7.6 work fine.
All logs and examples and py code for test in attachment.
Best regards
Dren
[dbutkovic@incumbosstest06 python]$ python3.6 test_insert_update.py
Connected
Hi,
When the number of columns in table is bigger than 10, only first row have
colums values in correct order.
Second row and all other rows have messed up values.
Select via sqlline or jdbc is ok, I noticed this only when working with
python.
Same result is with pyignite and pygridgain module.
