+1 (binding)
(Built Ignite.NET from sources, started from binary package, checked
examples)
On Tue, Dec 15, 2020 at 10:34 AM Yaroslav Molochkov
wrote:
> Dear Community,
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/
> https://dist.apache.org/
Pavel Tupitsyn created IGNITE-13834:
---
Summary: .NET: Set COMPlus_EnableAlternateStackCheck environment
variable in Dockerfile
Key: IGNITE-13834
URL: https://issues.apache.org/jira/browse/IGNITE-13834
+1, Java 11 seems to be the only right choice at the moment.
On Tue, Dec 8, 2020 at 12:08 PM Alexey Zinoviev
wrote:
> I totally support Java 11 for development. It's time to go forward
>
> вт, 8 дек. 2020 г. в 11:40, Andrey Gura :
>
> > Igniters,
> >
> > We already had some discussion about usin
Hi Victor,
Welcome to the Apache Ignite community!
I've added your Jira account to the Cotributors group.
Good luck!
Pavel
On Mon, Dec 7, 2020 at 8:13 PM Chemodanov Viktor
wrote:
> Hi All!
>
>
>
> My name is Victor Chemodanov.
>
>
>
> As a technical writer, I would be glad to contribute to th
Pavel Tupitsyn created IGNITE-13826:
---
Summary: .NET: RendezvousAffinityFunction.BackupFilter
Key: IGNITE-13826
URL: https://issues.apache.org/jira/browse/IGNITE-13826
Project: Ignite
Issue
Ilya,
I had the same thought, but Apache guidelines do not mention anywhere that
source releases should come first.
Binary releases are a much more popular option, so it makes sense to show
them first.
On Mon, Dec 7, 2020 at 5:53 PM Ilya Kasnacheev
wrote:
> Hello!
>
> As far as my understanding
Pavel Tupitsyn created IGNITE-13804:
---
Summary: Java thin: avoid buffer copies in synchronous operations
Key: IGNITE-13804
URL: https://issues.apache.org/jira/browse/IGNITE-13804
Project: Ignite
Semyon,
Fully agree, TypeScript is the way to go.
> full rewrite
I would not call it a "full rewrite", because TypeScript is a superset of
JavaScript.
1. Converting to TypeScript mostly means adding type annotations and
tweaking the code, not rewriting it from scratch
2. The conversion can be gr
re for now about where should the code be stored — in
> separate repository (secure, but disables testing of code with TC settings
> both in single PR), or alongside project's code (can be possible security
> hole).
> That would require additional dev thread I think.
>
>
>
PR is ready for review [1]
I've added a simple put/get benchmark, there is some performance
improvement over existing implementation, see results in the PR description.
[1] https://github.com/apache/ignite/pull/8483
On Fri, Nov 20, 2020 at 10:39 AM Pavel Tupitsyn
wrote:
> Since ther
Pavel Tupitsyn created IGNITE-13759:
---
Summary: .NET: Add support for dotnet-example global tool
Key: IGNITE-13759
URL: https://issues.apache.org/jira/browse/IGNITE-13759
Project: Ignite
Pavel Tupitsyn created IGNITE-13755:
---
Summary: .NET: Inspections fail after TC upgrade - unused classes
detected
Key: IGNITE-13755
URL: https://issues.apache.org/jira/browse/IGNITE-13755
Project
Pavel Tupitsyn created IGNITE-13754:
---
Summary: .NET: LINQ provider emits incorrect table alias for
queries with JOIN and GROUP BY combined
Key: IGNITE-13754
URL: https://issues.apache.org/jira/browse/IGNITE
If we use Java15 for development, can the resulting package be used from a
Java11 app (the latest LTS)?
On Tue, Nov 24, 2020 at 7:51 PM Andrey Mashenkov
wrote:
> Jave15 looks awesome.
>
> * Hidden classes [1] can be used by codegenerators.
> * Records [2] can replace boilerplate code like Ignite
> Thus, the one will not be able to map uint64 to Java long primitive, but
> to
> > BigInteger only.
> > As for indices, we could read uint64 to Java long, but treat negative
> > values in a different way to preserve correct ordering.
> >
> > These limitati
will get a negative value, so it should be cast to short
> at first. (converted to BigInteger for uint64)
> So, index on signed type will require a different comparator.
>
> That way doesn't look simpler.
>
> On Tue, Nov 24, 2020 at 4:23 PM Pavel Tupitsyn
> wrote:
>
stly they are for use from platforms where they have native support and
> > widely
> > used, like in C++ or .NET, where users currently have to make a manual
> type
> > casting
> > or even just stop using unsigned types when they use Ignite.
> >
> > Best Reg
straint for negative values. E.g. uLong to BigInteger.
> So, we can't use primitive Java type for Long here. However, it is still
> possible to store uLong in 8 bytes, but have a special comparator for
> unsigned types to avoid unwanted deserialization.
>
> WDYT?
>
>
>
>
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 example).
>
> B
Igniters,
I think we should support unsigned data types:
uByte, uShort, uInt, uLong
Java does not have them, but many other languages do,
and with the growing number of thin clients this is important.
For example, in current Ignite.NET implementation we store unsigned values
as signed internally
+1
On Tue, Nov 24, 2020 at 3:25 AM Saikat Maitra
wrote:
> +1
>
> On Mon, Nov 23, 2020 at 4:55 PM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > +1
> >
> > On Mon, Nov 23, 2020 at 2:44 PM Denis Magda wrote:
> >
> > > Igniters,
> > >
> > > With this vote, I'd like to formally
Pavel Tupitsyn created IGNITE-13746:
---
Summary: Document partition-aware data loading
Key: IGNITE-13746
URL: https://issues.apache.org/jira/browse/IGNITE-13746
Project: Ignite
Issue Type
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,
> > >
Igniters,
Here is a short note on recently released .NET 5:
https://ptupitsyn.github.io/Ignite-on-NET-5/
Pavel Tupitsyn created IGNITE-13692:
---
Summary: .NET: Default query timeout
Key: IGNITE-13692
URL: https://issues.apache.org/jira/browse/IGNITE-13692
Project: Ignite
Issue Type: Improvement
Igniters,
This is a continuation of "Use Netty for Java thin client" [1],
I'm starting a new thread for better visibility.
The problems with current Java thin client are:
* Socket writes block user threads
* Every connection uses a separate listener thread (with partition
awareness there is a thr
>
> > > > > > Hi Alexey,
> > > > > >
> > > > > > The IEP-54 [1] describes the data layout proposed for Ignite 3.0,
> > it
> > > > > > includes various date/time types. Can you please take a look and
> > > check
> > > > if
>
gt; > Nikolay,
> > >
> > > I am up for the call. I will try to explain my reasoning in greater
> > detail
> > > and will be glad to hear the concerns. Will this Friday, Nov 6th, work?
> > >
> > > вт, 3 нояб. 2020 г. в 10:09, Nikolay
Igniters,
I tried to build the docs today using the instructions from README.adoc [1]
Bare Jekyll:
/usr/lib/ruby/vendor_ruby/rouge.rb:55:in `block in ':
asciidoctor: FAILED:
/home/pavel/w/ignite/docs/_docs/SQL/JDBC/error-codes.adoc: Failed to load
AsciiDoc document - uninitialized constant Rouge
Alexey,
Just to clarify before we start the discussion:
this proposal seems to introduce some breaking changes, so we are talking
about Ignite 3.0, correct?
Pavel
On Tue, Nov 3, 2020 at 12:13 AM Alexey Kukushkin
wrote:
> Igniters,
>
> What do you think about changing .NET API to read/write por
es here.
> >
> > Finally, Anton & Nikolay
> > I do not have an estimate for this simply because the activity is
> > community-driven and it depends on the number of people willing to
> > contribute. With the current pace, I would hope to have an RC of Ignite
> 3.0
&g
1. Rewriting from scratch is never a good idea.
We don't want to follow the path of Netscape and lose all our users
by the time we have a working 3.0 [1]
2. Not sure about new repo - seems like some pain and no gain, what's the
problem with a branch?
3. We should keep existing integration tests w
Pavel Tupitsyn created IGNITE-13635:
---
Summary: .NET: OOM due to integer overflow in PlatformOutputStream
Key: IGNITE-13635
URL: https://issues.apache.org/jira/browse/IGNITE-13635
Project: Ignite
Hello Nathan,
Welcome to Apache Ignite community!
I've added your JIRA account to the contributors group so you can work on
tickets.
Please check our How to Contribute wiki page [1]
> mainly using C and Java during my college and research, but I am with C#
right now since it is the main language
Congratulations, everyone, and big thanks to Alex!
As always, I've prepared an overview for .NET features and improvements:
https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.9/
Pavel
On Fri, Oct 23, 2020 at 10:35 PM Denis Magda wrote:
> We made it! Congrats, community! Thanks, Alex for pus
Igniters,
I think we should plan 2.10 instead of 2.9.1.
ignite-2.9 branch was cut 4 months ago, a bunch of new features are waiting
to be released.
On Tue, Oct 27, 2020 at 4:23 AM 18624049226 <18624049...@163.com> wrote:
> Hello,
>
> I suggest that the remaining document issue in version 2.9.0 c
Pavel Tupitsyn created IGNITE-13622:
---
Summary: .NET: Add Snapshots API
Key: IGNITE-13622
URL: https://issues.apache.org/jira/browse/IGNITE-13622
Project: Ignite
Issue Type: New Feature
Pavel Tupitsyn created IGNITE-13615:
---
Summary: .NET: Fix failover-related documentation
Key: IGNITE-13615
URL: https://issues.apache.org/jira/browse/IGNITE-13615
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-13608:
---
Summary: .NET: Add Partitions and UpdateBatchSize to SqlFieldsQuery
Key: IGNITE-13608
URL: https://issues.apache.org/jira/browse/IGNITE-13608
Project: Ignite
Pavel Tupitsyn created IGNITE-13607:
---
Summary: .NET: Binary meta is not registered from QueryEntity on
cache start when types are not present on server node
Key: IGNITE-13607
URL: https://issues.apache.org/jira
nsaction's API a
> > > > little bit (Actually, in netty socket write is performed in other
> > thread
> > > > (channel.write is async) and
> > > > current tx logic will not work
> > > >
> (org.apache.ignite.internal.client.thin.TcpCl
Pavel Tupitsyn created IGNITE-13600:
---
Summary: .NET: TypeResolver uses legacy ReflectionOnlyLoad
Key: IGNITE-13600
URL: https://issues.apache.org/jira/browse/IGNITE-13600
Project: Ignite
Pavel Tupitsyn created IGNITE-13592:
---
Summary: .NET: Incorrect GetTotalPhysicalMemory result in Docker
Key: IGNITE-13592
URL: https://issues.apache.org/jira/browse/IGNITE-13592
Project: Ignite
Igniters,
I'm working on IEP-51 [1] to make Java thin client truly async
and make sure user threads are never blocked
(right now socket writes are performed from user threads).
I've investigated potential approaches and came to the conclusion
that Netty [2] is our best bet.
- Nice Future-based as
Alex, agree, this is not a release blocker.
On Thu, Oct 15, 2020 at 4:58 PM Alex Plehanov
wrote:
> Zhenya,
>
> It's not ok, but I think it's not a release blocker.
> Sources can be compiled using instructions given in DEVNOTES.txt (there are
> no requirements to enable checkstyle in our document
+1 (binding)
- Checked .NET binaries, examples, documentation
- Started a mixed cluster of .NET and Java nodes from binary, slim, and
source packages
- Compiled Ignite from sources
On Thu, Oct 15, 2020 at 3:04 PM Alex Plehanov
wrote:
> Dear Community,
>
>
> I have uploaded a release candidate t
; except in some specific cases. At least, default multicast group should be
> changed.
>
>
> чт, 15 окт. 2020 г. в 10:14, Pavel Tupitsyn :
>
> > Ivan, yes, it does use MulticastIpFinder, which can be problematic in
> > tests,
> > but it was fine for 5 years, and now go
Ivan, yes, it does use MulticastIpFinder, which can be problematic in tests,
but it was fine for 5 years, and now got broken.
Do you think this can be caused by the recent changes in GridNioServer?
Pavel
On Thu, Oct 15, 2020 at 9:41 AM Ivan Daschinsky wrote:
> It seems, that in this test we us
easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity.
Sergey, congratulations and welcome on board!
Best Regards,
Pavel Tupitsyn
on behalf of Apache Ignite PMC
+1 (binding)
- Checked .NET binaries, examples, documentation
- Started a mixed cluster of .NET and Java nodes
- Compiled Ignite from sources
On Tue, Oct 13, 2020 at 10:48 PM Denis Magda wrote:
> +1 (binding)
>
> Started a two-node Ignite cluster using the binary package and the
> ignite.sh sc
It depends. The only way to tell is to measure and profile your specific
use case.
What I'm trying to say is:
1. Start with one instance - low complexity, low overhead.
2. If performance needs improvement, and Ignite is determined to be a
bottleneck,
consider trying multiple instances, this ma
Java and .NET Thin Clients are thread-safe.
You can use one client instance for all requests.
However, in high-load scenarios, one client can become a bottleneck.
In this case you can try creating multiple client instances (say, one
client per processor)
and using them in a round-robin way.
On Sa
looked through your comments and fixed them. Could you please
> check one more time?
>
> On Fri, Oct 9, 2020 at 10:27 AM Pavel Tupitsyn
> wrote:
>
> > Hello Sergey,
> >
> > I went over the public API changes briefly and left some minor comments
> on
> > GitH
Hello Sergey,
I went over the public API changes briefly and left some minor comments on
GitHub
Thanks,
Pavel
On Fri, Oct 9, 2020 at 9:59 AM Sergey Chugunov
wrote:
> Hello Igniters,
>
> I'm getting closer to finishing main ticket for Maintenance Mode feature
> [1] and now working on test fixes
Pavel Tupitsyn created IGNITE-13555:
---
Summary: Java thin: Add support for IPv6 addresses
Key: IGNITE-13555
URL: https://issues.apache.org/jira/browse/IGNITE-13555
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-13551:
---
Summary: .NET: Enable ClientServerCompatibilityTest on Linux
Key: IGNITE-13551
URL: https://issues.apache.org/jira/browse/IGNITE-13551
Project: Ignite
Pavel Tupitsyn created IGNITE-13536:
---
Summary: .NET: Child processes become zombies when persistence is
used with direct-io on Linux
Key: IGNITE-13536
URL: https://issues.apache.org/jira/browse/IGNITE-13536
Pavel Tupitsyn created IGNITE-13530:
---
Summary: Java thin: exception type is lost on rethrow
Key: IGNITE-13530
URL: https://issues.apache.org/jira/browse/IGNITE-13530
Project: Ignite
Issue
Denis, IGNITE-13331 is ready for your review
https://issues.apache.org/jira/browse/IGNITE-13331
On Thu, Oct 1, 2020 at 9:42 AM Pavel Tupitsyn wrote:
> Denis,
>
> Thanks a lot for porting those changes, great job!
> I'm working on IGNITE-13331, sorry for the delay.
>
> On
Pavel Tupitsyn created IGNITE-13506:
---
Summary: .NET: Release build does not fail when compilation fails
Key: IGNITE-13506
URL: https://issues.apache.org/jira/browse/IGNITE-13506
Project: Ignite
you'll take care of
> >> IGNITE-13331 <https://issues.apache.org/jira/browse/IGNITE-13331>.
> Let's
> >> split the job.
> >>
> >> Nikolay, I'll review your contribution early next week.
> >>
> >> Thanks, folks, for the cooperat
Pavel Tupitsyn created IGNITE-13496:
---
Summary: Java thin: Use non-blocking socket IO
Key: IGNITE-13496
URL: https://issues.apache.org/jira/browse/IGNITE-13496
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-13485:
---
Summary: Java thin: increase test coverage for transactions and
partition awareness
Key: IGNITE-13485
URL: https://issues.apache.org/jira/browse/IGNITE-13485
pages or are you going to do it yourself?
>
> Btw, what's wrong with the 3rd-party integrations? Are you saying the .NET
> community no longer uses those?
>
> -
> Denis
>
>
> On Fri, Sep 18, 2020 at 5:45 AM Pavel Tupitsyn
> wrote:
>
> > Denis,
&
Igniters,
The PR is ready for review
https://github.com/apache/ignite/pull/8174
On Tue, Sep 22, 2020 at 11:51 AM Pavel Tupitsyn
wrote:
> Yes, this makes a lot of sense (and can be applied to Services, too).
>
> I've filed the ticket: https://issues.apache.org/jira/browse/IGNIT
Nikolay, can you try again? Seems to work fine for me.
On Tue, Sep 22, 2020 at 9:57 AM Nikolay Izhikov wrote:
> Hello, Igniters.
>
> Currently, mtcga bot is down - 502 bad gateway error.
> Can someone help with it?
>
> https://mtcga.gridgain.com/prs.html
>
Pavel Tupitsyn created IGNITE-13471:
---
Summary: Execute user-defined compute jobs asynchronously when
CompletionStage is returned
Key: IGNITE-13471
URL: https://issues.apache.org/jira/browse/IGNITE-13471
Yes, this makes a lot of sense (and can be applied to Services, too).
I've filed the ticket: https://issues.apache.org/jira/browse/IGNITE-13471
This requires a separate IEP, of course.
On Mon, Sep 21, 2020 at 6:33 PM mnk wrote:
> Pavel Tupitsyn wrote
> >> result of a remo
Pavel Tupitsyn created IGNITE-13470:
---
Summary: .NET: Add async counterparts to all applicable thin
client APIs
Key: IGNITE-13470
URL: https://issues.apache.org/jira/browse/IGNITE-13470
Project
> result of a remote execution is a CompletionStage
Can you give an example? What is a remote execution? Is this about Compute
and/or Services?
On Mon, Sep 21, 2020 at 5:11 PM mnk wrote:
> So one question I have here (and this maybe out of scope) - but what about
> the cases where the result o
Pavel Tupitsyn created IGNITE-13462:
---
Summary: .NET: Thin client Dispose hangs when continuous query is
active on .NET Core 3.x
Key: IGNITE-13462
URL: https://issues.apache.org/jira/browse/IGNITE-13462
Pavel Tupitsyn created IGNITE-13460:
---
Summary: .NET: Thin client can't be collected by GC when Dispose
was not called
Key: IGNITE-13460
URL: https://issues.apache.org/jira/browse/IGNITE-
Denis,
> @Pavel Tupitsyn ... Are you going to document the
features added in 2.9 <https://issues.apache.org/jira/browse/IGNITE-13331>
Yes, I have this on my plate, but the release was postponed so I postponed
the task as well.
> is there is anything else you planned to move fr
Agree with Val, even experienced developers have a hard time understanding
what "in-memory computing platform" really does.
"distributed memory-first database" is right on point.
On Thu, Sep 17, 2020 at 8:30 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> My vote is for the "dis
anilovsky
>
> wrote:
>
> >
> > I understand now, thanks Pavel, initial discussion didn`t touch kuber
> > theme ...
> >
> >
> > >Вторник, 15 сентября 2020, 18:22 +03:00 от Pavel Tupitsyn <
> > ptupit...@apache.org>:
> > >
> > >
Pavel Tupitsyn created IGNITE-13454:
---
Summary: Thin Client Ping API
Key: IGNITE-13454
URL: https://issues.apache.org/jira/browse/IGNITE-13454
Project: Ignite
Issue Type: Improvement
t at least we can have auto-ping as
> an
> >> >> internal mechanism. This will be helpful if the client doesn't send
> any
> >> new
> >> >> requests but only waits for server-side notifications (for example,
> if
> >> the
> >> &g
lved.
> >>
> >> So, +1 to add ping to the protocol, +0 to expose it to public API.
> >>
> >> [1]
> >>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/IEP-44-Thin-Client-Discovery-tp47129p47318.html
> >>
> >> п
p 13, 2020 at 10:16 PM Николай Ижиков
> wrote:
> >
> >> Hello, Pavel.
> >>
> >> SQL drivers usually use “SELECT 1” query to ensure connection is alive.
> >>
> >> Can we use similar approach?
> >>
> >> Отправлено с iPhone
>
Igniters,
There is a feature request for a thin client Ping operation on the user
list [1].
I think that is a good idea - IgniteClient.ping() will be a valuable
addition.
Any objections?
[1]
http://apache-ignite-users.70518.x6.nabble.com/Feature-request-method-to-test-active-connection-in-Ignite
Pavel Tupitsyn created IGNITE-13410:
---
Summary: .NET: Run Services tests with different service processors
Key: IGNITE-13410
URL: https://issues.apache.org/jira/browse/IGNITE-13410
Project: Ignite
Actually, we already have IgniteIllegalStateException,
it exists exactly for situations like this.
Let's just change GridKernalGatewayImpl to throw IgniteIllegalStateException
instead of IllegalStateException and handle that in .NET
On Sat, Aug 1, 2020 at 10:32 AM Pavel Tupitsyn
Denis,
No objections to the removal of the "final" modifier from my side.
However, the use case sounds a bit weird to me, can you please describe it
in more detail?
Thanks,
Pavel
On Mon, Aug 24, 2020 at 10:47 PM Denis Magda wrote:
> @Pavel Tupitsyn , @Igor Sapego ,
>
&g
at.
>
> I would be glad to hear other opinions though.
>
> -Val
>
> On Fri, Aug 21, 2020 at 1:02 AM Pavel Tupitsyn
> wrote:
>
> > Val,
> >
> > The problems with CompletableFuture in public API are:
> > * It is a class, not an interface
> > * It is c
Pavel Tupitsyn created IGNITE-13378:
---
Summary: .NET: Thin Client: Use non-blocking socket IO
Key: IGNITE-13378
URL: https://issues.apache.org/jira/browse/IGNITE-13378
Project: Ignite
Issue
lient data streamer
Very interesting, is there a ticket or IEP to follow?
On Fri, Aug 21, 2020 at 11:01 AM Pavel Tupitsyn
wrote:
> Val,
>
> The problems with CompletableFuture in public API are:
> * It is a class, not an interface
> * It is completable - anyone can call .complete()
thers, let's stick with the
> > CompletableFuture for any future development, including the thin client.
> >
> > -Val
> >
> > On Thu, Aug 20, 2020 at 9:30 AM Pavel Tupitsyn
> > wrote:
> >
> > > Val, no objections from my side.
> >
e any objections from others, let's stick with the
> CompletableFuture for any future development, including the thin client.
>
> -Val
>
> On Thu, Aug 20, 2020 at 9:30 AM Pavel Tupitsyn
> wrote:
>
> > Val, no objections from my side.
> > As noted above, the
>investigation of issues, but it really confused in production environment.
> >I see all participants tell the same.
> >
> >Pavel, do you mean this behavior should be switching by configuration?
> >
> >On Thu, Aug 20, 2020 at 5:00 PM Pavel Tupitsyn < ptupit..
d prefer using CompletableFuture in the thin client and getting rid of
> IgniteFuture altogether in 3.0.
>
> What do you think?
>
> -Val
>
> On Thu, Aug 20, 2020 at 7:19 AM Pavel Tupitsyn
> wrote:
>
> > Igniters,
> >
> > I've prepared an IEP [1], ple
Igniters,
I've prepared an IEP [1], please review and let me know what you think.
In particular, I'd like to discuss the Future interface to be used:
* IgniteFuture is the first candidate - Thin APIs will be consistent with
Thick APIs, probably better for existing Ignite users.
* CompletableFutur
Link to the original discussion:
http://apache-ignite-developers.2346864.n4.nabble.com/Exception-handling-in-thin-client-should-we-pass-stack-traces-to-the-client-td22392.html
On Thu, Aug 20, 2020 at 4:46 PM Zhenya Stanilovsky
wrote:
>
> I want to resurrect this discussion, i don`t understand w
ket IGNITE-13369 still in progress. When it will be resolved? Is it
> really critical bug? According to the user-list thread attached to the
> ticket, there is a workaround exists for this problem and looks like it's
> not so critical.
>
> вт, 18 авг. 2020 г. в 12:30, Pavel Tupitsyn :
Alex,
What's the status of the release?
Can we include a bug fix there [1]?
[1] https://issues.apache.org/jira/browse/IGNITE-13369
On Fri, Aug 14, 2020 at 11:14 AM Alex Plehanov
wrote:
> Hello,
>
> > What is the release date for 2.9, from the cwiki it still says August 7
> We have a performanc
Pavel Tupitsyn created IGNITE-13369:
---
Summary: .NET: Local node info is not updated on client reconnect
Key: IGNITE-13369
URL: https://issues.apache.org/jira/browse/IGNITE-13369
Project: Ignite
s can be achieved
with a little more work with Compute as well.
Thanks,
Pavel
On Tue, Aug 18, 2020 at 3:16 AM Saikat Maitra
wrote:
> Hi Pavel,
>
> Awesome, thank you.
>
> Yes, I remember having .Net modernization as part of Apache Ignite 3.0
> roadmap.
>
> Regards,
Saikat, yes, most definitely.
This is mentioned in the wishlist under ".NET: Target .NET Standard 2.0,
discontinue .NET 4.0 support".
I'm already working towards this goal by making more code and tests work
properly under .NET Core,
so when the time for breaking changes comes, it will be simpler.
Val,
The list of removals looks good to me, except Messaging.
I remember it had some implementation issues, but the API itself seems to
be rather useful -
what are we going to offer instead?
On Fri, Aug 14, 2020 at 3:16 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Folks,
>
>
Pavel Tupitsyn created IGNITE-13360:
---
Summary: .NET: Add Timeout to Thin Client services
Key: IGNITE-13360
URL: https://issues.apache.org/jira/browse/IGNITE-13360
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-13359:
---
Summary: .NET: Add GetServiceDescriptors to Thin Client Services
Key: IGNITE-13359
URL: https://issues.apache.org/jira/browse/IGNITE-13359
Project: Ignite
401 - 500 of 1891 matches
Mail list logo
