Hi,
Added as a contributor to the JIRA project.
Best Regards,
Igor
On Fri, Sep 1, 2023 at 12:55 PM Андрей Хитрин
wrote:
> Hello everyone!
>
> My name is Andrei Khitrin. I want to contribute to Ignite. I've already
> filled several issues, and now am ready to send small patches. My ASF JIRA
>
Congrats, guys!
Best Regards,
Igor
On Thu, Nov 17, 2022 at 4:39 PM Вячеслав Коптилин
wrote:
> Dear Igniters,
>
> I'm happy to announce that the 1st beta version of Ignite 3 is out!
>
> On top of the functionality that was previously released, Beta 5 adds the
> following major features:
> -
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 are some
> new
+1 (binding)
Best Regards,
Igor
On Tue, Nov 15, 2022 at 11:10 PM Vladislav Pyatkov
wrote:
> +1
>
> On Tue, Nov 15, 2022 at 3:35 PM Denis C wrote:
> >
> > +1
> >
> > вт, 15 нояб. 2022 г. в 13:33, Alexander Lapin :
> >
> > > +1
> > >
> > > вт, 15 нояб. 2022 г. в 08:48, Pavel Tupitsyn :
> > >
>
+1
Best Regards,
Igor
On Mon, Nov 14, 2022 at 5:23 PM Ivan Daschinsky
wrote:
> >>
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.6.0.rc0/examples.html
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.6.0.rc1/examples.html
>
> пн, 14 нояб. 2022 г. в
+1
Best Regards,
Igor
On Fri, Nov 11, 2022 at 5:41 PM Ivan Daschinsky
wrote:
> Dear Igniters!
>
> Release candidate binaries for subj are uploaded and ready for vote
> You can find them here:
> https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.0.rc0
>
> If you follow the link above,
+1
Github Actions look great to me.
Best Regards,
Igor
On Mon, Nov 7, 2022 at 5:38 PM Ivan Daschinsky wrote:
> Hi, Igniters!
>
> I suppose it is time to release pyignite 0.6.0, since we have released our
> previous release more than a year ago.
>
> Firstly, python 3.6 reached its EOL, the
+1 from me
Best Regards,
Igor
On Wed, Nov 2, 2022 at 3:48 AM Stanislav Lukyanov
wrote:
> Igniters,
>
> The initial code freeze date for 3.0.0 beta 1 was missed, so we need to
> pick a new timeline.
>
> There are currently 5 tickets in progress or in review that are in the
> scope, with
Guys,
I've merged https://issues.apache.org/jira/browse/IGNITE-17590 to main and
I really think it should be included in this release, because without it
current
C++ client implementation is pretty much useless. And it does not affect any
other parts of the product except for the C++ part anyway
Pavel,
Great, this feature showed great results in Ignite 2, so It's a good idea
to implement
it in Ignite 3 as well.
The IEP itself looks good to me, except it's not clear how a server would
know when
assignment has changed.
Regardless of the Tracking Assignment Changes section, I like the
19, 2022 at 10:55 PM Igor Sapego wrote:
> >
> > Andrey,
> >
> > 1. If a server generates a UUID that already exists it can check and just
> > re-generate it straight away
> > as a check is just a simple map lookup.
> >
> > 2. Well, yes. This
I like the closable iterator approach more as well. The difference in API
is not as critical in my opinion, as we have a lot of differences in thick
and
thin APIs already and users would normally seek thin client examples and
not just re-use thick client code with thin client.
Best Regards,
Igor
+1
Best Regards,
Igor
On Fri, Jun 10, 2022 at 1:37 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> +1
>
> On Thu, Jun 9, 2022 at 9:17 AM Alexander Polovtcev <
> alexpolovt...@gmail.com>
> wrote:
>
> > Looks good, so many great features! +1
> >
> > On Thu, Jun 9, 2022 at 6:42
so, do I understand correctly that a server has enough information
> >> about client connections so it will be possible to observe a
> >> connections list on the server? It would be useful for cluster
> >> monitoring purposes.
> >>
> >> On Tue, May 17, 2022
e of a secured cluster it does not matter, because
> authentication/authorization keeps intruders out.
>
>
> On Mon, May 16, 2022 at 11:07 PM Igor Sapego wrote:
>
> > Hi, Igniters
> >
> > I've prepared an IEP for Ignite 3 Client Lifecycle [1]. The main idea is
> to
Hi, Igniters
I've prepared an IEP for Ignite 3 Client Lifecycle [1]. The main idea is to
define client lifecycle as well as core algorithms and mechanisms used by
clients. This proposal can be used as a reference for implementation of a
new client for Ignite when dealing with such problems as:
Feature seems useful for me as it makes connection management more robust
and
predictable.
I agree with Pavel, that we should print warning when heartbeat period is
larger than
idle timeout, but I see a problem here as idle timeout is configured on
server and is not
known to clients, while
+1 (binding)
Best Regards,
Igor
On Tue, Jan 25, 2022 at 10:44 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> +1 (binding)
>
> On Tue, Jan 25, 2022 at 11:43 AM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Dear Community,
> >
> > Ignite 3 is moving
Pavel,
What is ClientOperationType? Will it list basically all operations or only
types like Idempotent, NonIdempotent?
Best Regards,
Igor
On Wed, Nov 24, 2021 at 5:21 PM Pavel Tupitsyn wrote:
> Igniters,
>
> I've prepared a proposal about thin client retry behavior.
> Please review and let
Sorry,
I meant we need to publish the package as part of RC, so it can be reviewed.
Best Regards,
Igor
On Thu, Oct 14, 2021 at 11:34 AM Igor Sapego wrote:
> Val,
>
> I think we need to upload the nuget package we want to upload so the
> community
> would know what we are
Val,
I think we need to upload the nuget package we want to upload so the
community
would know what we are going to upload and can check that everything is
right.
WDYT?
Best Regards,
Igor
On Wed, Oct 13, 2021 at 8:03 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Pavel,
>
>
Kevin,
Basically, to change this we need people who would actively drive
development of the client and be active community members.
Best Regards,
Igor
On Mon, Sep 27, 2021 at 6:02 PM Ivan Daschinsky wrote:
> Hi! I can share my experience how to drive this activity. Personally, I've
> driven
Hi guys,
Why can not a user implement such context on application level?
I believe Ignite provides all necessary tools for that. User can just
implement such a context as user type and pass it to services they
need. Are the arguments why would Ignite need a separate feature
for such a use case?
Sounds good, no objections from my side.
Best Regards,
Igor
On Wed, Oct 6, 2021 at 11:46 AM Stanislav Lukyanov
wrote:
> Hi Igniters,
>
> I found the following usability issue with java thin client API.
>
> Whenever you do `try (IgniteClient client = Ignition.startClient(cfg))`,
> you're
Sounds very reasonable to me.
+1
Though the default comparator should be implemented very carefully
as we had issues with comparison of binary objects in 2.x
Best Regards,
Igor
On Thu, Sep 9, 2021 at 4:04 PM Pavel Tupitsyn wrote:
> Igniters,
>
> Tuple in Ignite 3.x is a replacement for
I actually agree with Pavel, at least at putAll() part. We require a Map
from user
when we do not really need a Map in this method. What we really need here is
an iterable collection of pairs. Can not see why user can not pass for
example an
array here.
Now, when we talk about getAll() method
+1
Best Regards,
Igor
On Thu, Sep 9, 2021 at 8:33 PM Maxim Muzafarov wrote:
> +1
>
> On Thu, 9 Sept 2021 at 14:08, Nikolay Izhikov wrote:
> >
> > +1 to release ASAP.
> >
> > > 9 сент. 2021 г., в 13:43, Ivan Daschinsky
> написал(а):
> > >
> > > TC build of release branch --
> > >
>
Regards,
Igor
On Thu, Sep 9, 2021 at 2:29 PM Ivan Daschinsky wrote:
> Igor, and what about C++20 and coroutines [1]
>
> [1] -- https://en.cppreference.com/w/cpp/language/coroutines
>
> чт, 9 сент. 2021 г. в 14:12, Igor Sapego :
>
> > Well, fortunately we do not provide
Well, fortunately we do not provide a C client if you don't consider ODBC
as one so we should not think about it. For C++ I believe we should use
standard std::future+std::promise for async, but still can provide sync
methods,
built on top of async methods. There is no continuation problem in C++
in 2.12 in full form if Igor agrees and RE thinks
> this is
> > > the best course of action.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego :
> > >
> > >
incomplete change from 2.11 in order
> to reintroduce it in 2.12 in full form if Igor agrees and RE thinks this is
> the best course of action.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 29 июл. 2021 г. в 18:07, Igor Sapego :
>
> > Alexey,
> >
> &g
ockers. I may be
> wrong, but this ticket doesn't seem to be of that kind.
>
> On 2021/07/28 21:00:15, Igor Sapego wrote:
> > Igniters,
> >
> > I suggest adding [1] to the scope of release, because it contains
> > changes to code introduced by [2], which is alread
Igniters,
I suggest adding [1] to the scope of release, because it contains
changes to code introduced by [2], which is already included in release.
[1] - https://issues.apache.org/jira/browse/IGNITE-14815
[2] - https://issues.apache.org/jira/browse/IGNITE-14658
Best Regards,
Igor
On Mon, Jul
ums and gpg signatures (signed by Igor Sapego (CODE
> SIGNING KEY) 5C10 A072 2D94 7727 923C 98B5 AF35 DBD9
> 58FE 8DC5)
> key is inside https://downloads.apache.org/ignite/KEYS)
>
> пт, 23 июл. 2021 г. в 13:52, Ivan Daschinsky :
>
> > The voting finishes at 07/27/2021 12:00 UT
Ivan, what are extra serde steps you are talking about?
Best Regards,
Igor
On Thu, Jul 1, 2021 at 5:52 PM Ivan Daschinsky wrote:
> > I agree. But this was decided before in IEP-54, and is out of scope for
> current IEP.
> Would you like to start a separate thread to discuss this? Or I can do
+1
Best Regards,
Igor
On Sat, Jun 26, 2021 at 1:41 AM Nikita Ivanov wrote:
> +1
>
> --
> Nikita Ivanov
>
>
>
> On Fri, Jun 25, 2021 at 3:31 PM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Dear Community,
> >
> > In the last several months, the development of Ignite 3
so not sure if it’s a regression, but it’s
> >>>>> not great.
> >>>>>
> >>>>> > On 18 Jun 2021, at 09:36, Stephen Darlington <
> >>>>> stephen.darling...@gridgain.com> wrote:
> >>>>> >
> >>
+1 from me
Best Regards,
Igor
On Thu, Jun 17, 2021 at 12:10 PM Ivan Daschinsky
wrote:
> +1 From me
> Checked on Ubuntu 20.04 and windows 10
> 1. Installation from wheels for pythons 3.6 3.7 3.8 3.9
> 2. Native module work
> 3. Examples
>
> Checked on Ubuntu 20.04 building from source package
I propose to cancel this release and fix the issue which was highlighted in
the
"Seconds and milliseconds confusion in python thin client" thread.
WDYT?
Best Regards,
Igor
On Wed, Jun 16, 2021 at 12:10 AM Igor Sapego wrote:
> +1 from me
>
> Uploaded to test.pipy.org: ht
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 place
+1 from me
Uploaded to test.pipy.org: https://test.pypi.org/project/pyignite/0.5.0/
Everything looks good.
Best Regards,
Igor
On Tue, Jun 15, 2021 at 10:09 PM Ivan Daschinsky
wrote:
> Also checked hash sums and signature. Packages are verified and
> signature is OK, signed by Igor
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 (number of
t; > > > >
> >> > > > > > > > >
> >> > > > > > > > > пт, 5 мар. 2021 г. в 15:23, Pavel Tupitsyn <
> >> > > ptupit...@apache.org
> >> > > > >:
> >> > > > > > > > >
> >> >
+1 from me. There were no major issues with this feature and it gives
good performance boost for many cases.
Best Regards,
Igor
On Wed, May 12, 2021 at 5:18 PM Ivan Daschinsky wrote:
> Huge +1 from me. PA should be enabled by default.
>
> ср, 12 мая 2021 г. в 13:33, Pavel Tupitsyn :
> >
> >
Thanks for issuing a ticket. I'll take a look at it.
Best Regards,
Igor
On Fri, Apr 23, 2021 at 1:40 PM teligenz.dheeraj
wrote:
> Team,
>
> I have used nodejs thin client to connect ignite. With single query at time
> on socket works fine. But when hit multiple request simultaneously, getting
Hi,
Ivan, I like your suggestion. To me it looks better than the current
approach.
Best Regards,
Igor
On Mon, Apr 26, 2021 at 11:47 AM Nikita Safonov
wrote:
> Hi Ivan,
>
> Thanks for sharing the information.
> I'll look through the docs and share my thoughts and suggestions soon.
>
>
+1 from me.
Best Regards,
Igor
On Fri, Apr 16, 2021 at 5:05 PM Ivan Daschinsky
wrote:
> Ivan Daschinsky
> чт, 15 апр., 21:37 (19 часов назад)
> кому: dev
> Dear Igniters!
>
> Release candidate binaries are at least uploaded and ready for vote
> You can find them here:
>
Igor Sapego created IGNITE-14534:
Summary: Python thin: Add script for building wheels on Windows
Key: IGNITE-14534
URL: https://issues.apache.org/jira/browse/IGNITE-14534
Project: Ignite
The Project Management Committee (PMC) for Apache Ignite has invited
Ivan Daschinsky to become a committer and we are pleased to announce that
he has accepted.
Ivan made a lot of contributions to Apache Ignite.
He helped a lot to improve our Python Thin Client fixing a lot of different
bugs and
Igor Sapego created IGNITE-14475:
Summary: C++/dotnet query-example select result is various with
additional node
Key: IGNITE-14475
URL: https://issues.apache.org/jira/browse/IGNITE-14475
Project
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
Igor Sapego created IGNITE-14432:
Summary: Python thin: Support "with" statement for connection
method
Key: IGNITE-14432
URL: https://issues.apache.org/jira/browse/IGNITE-14432
Proje
Pavel, I like the proposal,
+1 from me
Best Regards,
Igor
On Tue, Mar 16, 2021 at 6:49 PM Pavel Tupitsyn wrote:
> Alexey,
>
> .NET thick API delegates to Java directly.
>
> When you do ICache.PutAsync():
> * Future is created on Java side, .listen() is called
> * TaskCompletionSource is
Nikolay,
That's because we now have separate repos for them: [1], [2] and [3].
Actually, active development is moved to those repos some time ago and
those directories in main repo are not actual anymore anyway.
Decision of moving those clients to separate repos was discussed in [4]
[1] -
+1 (binding)
Checked C++ compilation, C++ examples
Best Regards,
Igor
On Fri, Mar 5, 2021 at 12:32 AM Denis Magda wrote:
> +1 (binding)
>
> Downloaded the binary package and started a 2-node cluster on MacOS with
> ignite.sh.
>
> -
> Denis
>
>
> On Wed, Mar 3, 2021 at 1:03 PM Maxim Muzafarov
Pavel,
I've checked the IEP and I like it. The only thing that seems a bit
confusing to me
is that there are 4 different variants for clients but there are cons and
pros for
different variants. Maybe at least few sentences should be written here to
give developers who are not familiar with
Igor Sapego created IGNITE-14265:
Summary: Python thin: Support passwords for certificates
Key: IGNITE-14265
URL: https://issues.apache.org/jira/browse/IGNITE-14265
Project: Ignite
Issue
The following commit should be
cherry-picked: 0675e2a7e800730c9c8230332b82809754ddae5a
Sorry for a delay.
Best Regards,
Igor
On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego wrote:
> Maxim,
>
> The issue is fixed and is merged to master now.
>
> Best Regards,
> Igor
>
>
>
gt; > Fixed an issue that caused a deadlock when user cache was created
> in
> > > > > parallel with TTL worker was in progress.
> > > > > https://issues.apache.org/jira/browse/IGNITE-14078
> > > > >
> > > > > On Thu, 18 Feb 2021 at 20:26, Max
Igor Sapego created IGNITE-14211:
Summary: Python thin: SQL API is broken
Key: IGNITE-14211
URL: https://issues.apache.org/jira/browse/IGNITE-14211
Project: Ignite
Issue Type: Bug
Maxim,
I believe I could fix the ticket [1] by the end of the next week.
[1] https://issues.apache.org/jira/browse/IGNITE-14204
Best Regards,
Igor
On Thu, Feb 18, 2021 at 6:30 PM Max Timonin wrote:
> Hi! I've today found an issue [1], there is wrong handling of inlined POJO.
> This bug
Igor Sapego created IGNITE-14174:
Summary: Python thin: returns the time value + the client's time
zone, instead of the time value from the database.
Key: IGNITE-14174
URL: https://issues.apache.org/jira/browse
Igor Sapego created IGNITE-14162:
Summary: Python thin gives ambiguous message when using a wrong
username/password to connect
Key: IGNITE-14162
URL: https://issues.apache.org/jira/browse/IGNITE-14162
Igor Sapego created IGNITE-14127:
Summary: Python Thin: increase default query page size
Key: IGNITE-14127
URL: https://issues.apache.org/jira/browse/IGNITE-14127
Project: Ignite
Issue Type
Guys,
I agree with your concerns about backward compatibility, but
I think this can be a good feature that will help us to add support
for compact footer to thin clients that do not support it currently.
Best Regards,
Igor
On Tue, Feb 2, 2021 at 11:49 AM Pavel Tupitsyn wrote:
> Alex,
>
>
Igor Sapego created IGNITE-14099:
Summary: CPP: Remove 32-bit configs
Key: IGNITE-14099
URL: https://issues.apache.org/jira/browse/IGNITE-14099
Project: Ignite
Issue Type: Bug
Igor Sapego created IGNITE-14075:
Summary: Python client incorrect hash code calculation for classes
as composite keys
Key: IGNITE-14075
URL: https://issues.apache.org/jira/browse/IGNITE-14075
Igor Sapego created IGNITE-14059:
Summary: Thin Python client doesn't work with nested complex
objects
Key: IGNITE-14059
URL: https://issues.apache.org/jira/browse/IGNITE-14059
Project: Ignite
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
Igor Sapego created IGNITE-14057:
Summary: Python thin: implement support for big-endianness
Key: IGNITE-14057
URL: https://issues.apache.org/jira/browse/IGNITE-14057
Project: Ignite
Issue
Igor Sapego created IGNITE-14056:
Summary: Python thin: Readme and other docs are outdated
Key: IGNITE-14056
URL: https://issues.apache.org/jira/browse/IGNITE-14056
Project: Ignite
Issue
Ivan,
Though I generally agree with the approach you've suggested, I can see
a problem here. Since we now have a separate repos for thin clients, for
some features we may need to introduce changes to Ignite and python-thin
repos in a single ticket and we should have an ability to run tests on
Igor Sapego created IGNITE-13997:
Summary: CPP Thin: Transactions can cause deadlock when client
shared in multiple threads
Key: IGNITE-13997
URL: https://issues.apache.org/jira/browse/IGNITE-13997
Agree with Pavel, this should be disabled by default.
To me it looks pretty dangerous as users do not explicitly control what's
going to be
registered and it could lead to hard-to-debug mistakes when wrong classes
get
registered or with wrong names. Also it can be hard to use with classes
that
Looks like a great improvement, +1 from me
Best Regards,
Igor
On Tue, Jan 12, 2021 at 4:43 PM Pavel Tupitsyn wrote:
> Igniters,
>
> Our .NET examples are in need of a refreshment.
> I've prepared an IEP [1], please let me know what you think.
>
> Thanks,
> Pavel
>
>
> [1]
>
>
Igor Sapego created IGNITE-13909:
Summary: Node.js client glob dependency is missing
Key: IGNITE-13909
URL: https://issues.apache.org/jira/browse/IGNITE-13909
Project: Ignite
Issue Type: Bug
Igor Sapego created IGNITE-13908:
Summary: ODBC driver should show real nullability info
Key: IGNITE-13908
URL: https://issues.apache.org/jira/browse/IGNITE-13908
Project: Ignite
Issue Type
Igor Sapego created IGNITE-13907:
Summary: CPP thin: allow user to limit number of max active
connections per client
Key: IGNITE-13907
URL: https://issues.apache.org/jira/browse/IGNITE-13907
Project
Hi Igniters,
As you may know thin clients now can establish connections with
multiple servers simultaneously. It is implemented this way to make
partition awareness [1] work or for fast failover if partition awareness
is not used. However, sometimes it can create excessive load for
cluster in use
Igor Sapego created IGNITE-13900:
Summary: CPP: Fix test flaky Affinity tests
Key: IGNITE-13900
URL: https://issues.apache.org/jira/browse/IGNITE-13900
Project: Ignite
Issue Type: Bug
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
Cool, I like the idea.
You've got a +1 from me
Best Regards,
Igor
On Tue, Dec 1, 2020 at 12:20 PM Данилов Семён wrote:
> Yes, TS compiler produces JS files and TS-typings. Users that are already
> using JS version will have a seamless migration. Note: we'll have to
> publish compiled JS files
Igor Sapego created IGNITE-13825:
Summary: Decimal columns in SQL result set have invalid precision
and scale
Key: IGNITE-13825
URL: https://issues.apache.org/jira/browse/IGNITE-13825
Project: Ignite
; > [2] https://github.com/apache/ignite/pull/8483
> > >
> > > On Mon, Nov 9, 2020 at 4:07 PM Ivan Daschinsky
> > > wrote:
> > >
> > >> I suppose that the best variant -- ability to switch to netty if this
> > lib
> > >> is in classpath
Igor Sapego created IGNITE-13801:
Summary: ODBC: Check ODBC driver with Ab Initio and fix all issues
Key: IGNITE-13801
URL: https://issues.apache.org/jira/browse/IGNITE-13801
Project: Ignite
Igor Sapego created IGNITE-13793:
Summary: ODBC: Implement SQLRowCount for select queries
Key: IGNITE-13793
URL: https://issues.apache.org/jira/browse/IGNITE-13793
Project: Ignite
Issue Type
Igor Sapego created IGNITE-13774:
Summary: Create TC suites for release Python Node.js and PHP
clients
Key: IGNITE-13774
URL: https://issues.apache.org/jira/browse/IGNITE-13774
Project: Ignite
Igor Sapego created IGNITE-13771:
Summary: ODBC crashes on Linux if SQLConnect is called
Key: IGNITE-13771
URL: https://issues.apache.org/jira/browse/IGNITE-13771
Project: Ignite
Issue Type
Igor Sapego created IGNITE-13767:
Summary: Remove Python PHP and Node.js thin clients from main
repository
Key: IGNITE-13767
URL: https://issues.apache.org/jira/browse/IGNITE-13767
Project: Ignite
gt; > On Tue, Nov 24, 2020 at 2:04 PM Pavel Tupitsyn
> > wrote:
> >
> > > Agree, let's get rid of "long, short, byte" in the protocol definition.
> > >
> > > We can use Rust style, which is concise and unambiguous:
> > > i8, u8, i16, u16,
Pavel,
I totally support that. Also, if we are aiming for
stronger platform-independance,
in our schemas we may want to support bit-notation (int32, uint64)? For
example
"long" can mean a different type on different platforms and it's easy to
confuse
them (happens often when using ODBC for
Igor Sapego created IGNITE-13737:
Summary: Move PHP thin client to a separate git repo
Key: IGNITE-13737
URL: https://issues.apache.org/jira/browse/IGNITE-13737
Project: Ignite
Issue Type
Igor Sapego created IGNITE-13736:
Summary: Move Node.js thin client to a separate git repo
Key: IGNITE-13736
URL: https://issues.apache.org/jira/browse/IGNITE-13736
Project: Ignite
Issue
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
Sounds like a good idea to me.
Best Regards,
Igor
On Mon, Nov 9, 2020 at 3:32 PM Alex Plehanov
wrote:
> +1 for using GridNioServer as java thin client communication layer.
>
> вс, 8 нояб. 2020 г. в 19:12, Pavel Tupitsyn :
>
> > Igniters,
> >
> > This is a continuation of "Use Netty for Java
Igor Sapego created IGNITE-13637:
Summary: ODBC: Add support of SQL_ATTR_ROW_ARRAY_SIZE with value
more than one
Key: IGNITE-13637
URL: https://issues.apache.org/jira/browse/IGNITE-13637
Project
Igor Sapego created IGNITE-13636:
Summary: ODBC driver assigns SQL_BINARY type to DATE fields
Key: IGNITE-13636
URL: https://issues.apache.org/jira/browse/IGNITE-13636
Project: Ignite
Issue
my own fault. Thanks for
> making me have a look at that again.
>
> Thanks,
> Brett
>
> -Original Message-
> From: Igor Sapego [mailto:isap...@apache.org]
> Sent: Tuesday, September 29, 2020 2:22 AM
> To: dev
> Subject: [EXTERNAL] Re: cpp thin client vector resi
,
Igor
On Tue, Sep 29, 2020 at 11:22 AM Igor Sapego wrote:
> Hi,
>
> Can you share your ignite::binary::BinaryType::Read method where reading of
> the std::vector is going on?
>
> Also, are your strings large too or only vectors?
>
> Best Regards,
> Igor
>
>
> O
Hi,
Can you share your ignite::binary::BinaryType::Read method where reading of
the std::vector is going on?
Also, are your strings large too or only vectors?
Best Regards,
Igor
On Mon, Sep 28, 2020 at 8:29 PM Brett Elliott wrote:
> Hello,
>
> Tl;dr: I'm doing some profiling, and the cpp
1 - 100 of 611 matches
Mail list logo
