Pavel Tupitsyn created IGNITE-14532:
---
Summary: Thin client: Unordered map used for putAll warning is
unavoidable
Key: IGNITE-14532
URL: https://issues.apache.org/jira/browse/IGNITE-14532
Project
proach you're suggesting if I haven't
> convinced you by now :)
>
> Thanks,
> Stan
>
> > On 29 Mar 2021, at 22:47, Pavel Tupitsyn wrote:
> >
> > Stan,
> >
> > Unfortunately, annotations have a few drawbacks:
> > * Can't configure it globally ("I
t; own
> > CQ
> > > classes and interfaces for thin client, but such API looks weird. On
> the
> > > one hand, we should use CacheEntryEventFilter (JCache interface) since
> > it's
> > > required by the server-side, on the other hand, we can't use
> > >
gt; > > > > > > >
> > > > > > > >> > The methods below shouldn't be accessible for user:
> > > > > > > >> > complete()
> > > > > > > >> > completeExceptionaly()
> > > > > > > >>
> > > > > > > >> Folks, in case of user-facing API,
ould eventually be deprecated.
>
> WDYT?
>
> Thanks,
> Stan
>
> > On 29 Mar 2021, at 14:09, Pavel Tupitsyn wrote:
> >
> > Stan,
> >
> > I'm ok with using public pool by default, but we need a way to restore
> the
> > old behavior,
Hello,
Please pass all known server node addresses to
ClientConfiguration.setAddresses.
E.g. if everything is on one machine, for 3 servers it'll be
setAddresses("127.0.0.1:10800", "127.0.0.1:10801", "127.0.0.1:10802")
On Mon, Mar 29, 2021 at 3:23 PM Максим Плотников
wrote:
> Hello!
>
>
>
>
ated pool looks safer and more manageable to me. Make sure the threads
> in the pool are lazily started and stopped if not used for some time.
>
> Because I have no more real arguments against the change, I suggest to
> proceed with this approach.
>
> чт, 25 мар. 2021 г. в 22:
On the one hand, I agree with Alexey.
CompletableFuture has complete* methods which should not be available to
the user code.
This can be solved with a simple interface like we do in Thin Client:
IgniteClientFuture extends Future, CompletionStage
On the other hand:
- CompletionStage has
ommonPool is heavily used for other purposes
Common pool resizes dynamically to accommodate the load [1]
What do you think about Stan's suggestion to use our public pool instead?
[1]
https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ForkJoinPool.html
On Thu, Mar 25, 2021 at 10:10 PM Pavel
2.X for the reasons above - we already have ways
> to control a listener's behavior - it's a matter of good documentation to
> me.
>
>
>
>
>
>
> чт, 25 мар. 2021 г. в 15:33, Pavel Tupitsyn :
>
> > Alexei,
> >
> > > Sometimes it's more desirable to e
s or any other potentially blocking
> operations inside the listener.
>
> Otherwise listenAsync should be used.
>
>
>
> чт, 25 мар. 2021 г. в 14:04, Pavel Tupitsyn :
>
> > Stan,
> >
> > We have thread pools dedicated for specific purposes, like cache
>
ernatively, we may consider using public pool for that. May I ask if
> there is an example use case which doesn’t work with public pool?
>
> For .NET, agree that we should follow the rules and APIs of the platform,
> so the behavior might slightly differ.
>
> Thanks,
> Sta
Pavel Tupitsyn created IGNITE-14402:
---
Summary: Java Thin: Continuous Query
Key: IGNITE-14402
URL: https://issues.apache.org/jira/browse/IGNITE-14402
Project: Ignite
Issue Type: New Feature
Igniters, since there are no more comments and/or review feedback,
I'm going to merge the changes by the end of the week.
On Mon, Mar 22, 2021 at 10:37 PM Pavel Tupitsyn
wrote:
> Ready for review:
> https://github.com/apache/ignite/pull/8870
>
> On Sun, Mar 21, 2021 at 8:09 PM Pa
Ready for review:
https://github.com/apache/ignite/pull/8870
On Sun, Mar 21, 2021 at 8:09 PM Pavel Tupitsyn wrote:
> Simple benchmark added - see JmhCacheAsyncListenBenchmark in the PR.
> There is a 6-8% drop (1 client, 2 servers, 1 machine, int key/val).
> I expect this difference
Simple benchmark added - see JmhCacheAsyncListenBenchmark in the PR.
There is a 6-8% drop (1 client, 2 servers, 1 machine, int key/val).
I expect this difference to become barely observable on real-world
workloads.
On Thu, Mar 18, 2021 at 12:35 PM Pavel Tupitsyn
wrote:
> De
Pavel Tupitsyn created IGNITE-14343:
---
Summary: .NET: Allow arbitrary MemberInit projections in LINQ
Key: IGNITE-14343
URL: https://issues.apache.org/jira/browse/IGNITE-14343
Project: Ignite
, 17 мар. 2021 г. в 17:36, Вячеслав Коптилин <
> slava.kopti...@gmail.com
> > >:
> > >
> > > > Hi Pavel,
> > > >
> > > > > Not a good excuse really. We have a usability problem, you have to
> > > admit
> > > > it.
> &
putAsync(1, 1);
> fut.listenAync(f -> {
> // Executes on Striped pool and deadlocks.
> cache.replace(1, 2);
> }, ForkJoinPool.commonPool());
>
> Of course, it does not mean that this fact should not be properly
> documented.
> Perhaps, I am missing something.
>
> Thanks,
to me, that we should not change the current behavior.
> > However, thread pool executor can be added as an optional parameter of
> > listen() method as follows:
> >
> > public void listen(IgniteInClosure> lsnr,
> > Executor exec);
> >
> > Thanks,
> > S.
> >
> > пн, 15 мар. 2021 г. в 19:24, Pavel Tupitsyn :
> >
> >> Igniters,
> >>
> >> Please review the IEP [1] and let me know your thoughts.
> >>
> >> [1]
> >>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-70%3A+Async+Continuation+Executor
> >>
> >
>
at should I do with an announcement blog post for blogs.apache.org?
> > > Should it also be prepared prior to an announcement message?
> > >
> > > On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov
> wrote:
> > > >
> > > > Pavel,
> > > >
>
> SynchronizationContext captured before the async operation. I thought we
> > would have to do it in Ignite. Now I know that and have no problems with
> > the IEP.
> >
> > ср, 17 мар. 2021 г. в 11:18, Pavel Tupitsyn :
> >
> > > Denis,
> > >
>
e are 2 PR's for the ticket[1] with two different APIs suggested.
> Please, take a look at PR [2].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14035
> [2] https://github.com/apache/ignite-3/pull/69
>
> On Wed, Mar 17, 2021 at 11:11 AM Pavel Tupitsyn
> wrote:
>
> &
Denis,
> we don't try to solve the problem mentioned in the IEP
The problem: user code executes on striped pool (which causes issues)
The solution: don't execute user code on striped pool
I believe this solves the problem and removes any and all restrictions
for async listeners/continuations.
Andrey, I can't find any async methods,
can you please check if the changes are pushed?
On Tue, Mar 16, 2021 at 10:06 PM Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:
> Pavel, good point.
> Thanks. I've added async methods.
>
> On Fri, Mar 12, 2021 at 2:29 PM Pavel
etAsync(1)
This performs better for local entries, because we avoid
async method overhead, and worse for non-local entries, because we do two
calls.
On Tue, Mar 16, 2021 at 10:58 PM Pavel Tupitsyn
wrote:
> Alexey,
>
> I'm not sure your understanding is entirely correct.
> The proposal
n-UI thread" exception. But if you
> > > capture SynchronizationContext.Current in PutAsync and then route
> > > continuation to the captured context then the code would work.
> > >
> > > I think the users really expect the continuations to be executed on
default and it should have exciting behavior (use
> Ignite striped pool) if ConfigureAwait(false) was specified for the Task
> result.
>
> Is my understanding correct?
>
>
> пн, 15 мар. 2021 г. в 19:24, Pavel Tupitsyn :
>
> > Igniters,
> >
> > Please review t
Igniters,
Please review the IEP [1] and let me know your thoughts.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-70%3A+Async+Continuation+Executor
Ilya,
Thanks for the effort!
I think this guide should be much shorter and simple.
Right now it is intimidating for newcomers.
What they need is basically
* Register in Jira, pick a ticket, assign, put In Progress
* Create a fork, implement
* Create a PR
* Ask for review
Maybe we should have a
led and can be easily extracted
> to
> >> >> > separate
> >> >> > > > module if we decide to do so.
> >> >> > > > * Some columns types (e.g. Date/Time) are missed, they will be
> >> added
> >>
Hello,
Please see [1], [2].
In short:
* Create a JIRA account and ask for Contributor permissions here on the dev
list
* Pick a ticket, implement, ask for review (by mentioning maintainers [3]
in the ticket or here)
[1] https://ignite.apache.org/community/contribute.html
[2]
+1 (binding)
Downloaded binary packages, started nodes, .NET examples, .NET nodes.
Downloaded source package, built Java and .NET parts.
On Thu, Mar 11, 2021 at 4:24 AM Maxim Muzafarov wrote:
> Dear Community,
>
> I have uploaded a release candidate to:
>
>
Ilya,
I hear you about confusing .NET build procedure,
there is a ticket for that [1]
[1] https://issues.apache.org/jira/browse/IGNITE-13859
On Fri, Mar 5, 2021 at 1:37 PM Igor Sapego wrote:
> +1 (binding)
>
> Checked C++ compilation, C++ examples
>
> Best Regards,
> Igor
>
>
> On Fri, Mar 5,
Maxim, thanks!
I've cherry-picked IGNITE-14293.
On Wed, Mar 10, 2021 at 10:05 PM Maxim Muzafarov wrote:
> Pavel,
>
> Sorry, my bad. Entangled in my local branches during trying to
> cherry-pick related commits.
> I've reverted this change.
>
>
> On Wed, 10 Mar 2021
e it a bit of time for
> the self-stabilization process :-)
>
> On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn wrote:
> >
> > Maxim,
> >
> > Sure, I can assist with cherry-picks.
> >
> > 13661 is fixed by 13979, as indicated by the "fixed by" lin
/IGNITE-13661
> [4] https://issues.apache.org/jira/browse/IGNITE-13661
> [5] https://issues.apache.org/jira/browse/IGNITE-13979
>
> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn wrote:
> >
> > Maxim,
> >
> > No objections to those cherry-picks,
> > please also inc
Maxim,
No objections to those cherry-picks,
please also include https://issues.apache.org/jira/browse/IGNITE-14293
Thanks!
On Wed, Mar 10, 2021 at 10:54 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Unless we do extra checks for Windows environment, I suggest merging
> IGNITE-14284
Pavel Tupitsyn created IGNITE-14294:
---
Summary: .NET: ClientServerCompatibilityTest is flaky
Key: IGNITE-14294
URL: https://issues.apache.org/jira/browse/IGNITE-14294
Project: Ignite
Issue
n the same data files or
> > even migrating to the next release without any problems if they don't
> > use deprecated features.
> > - if any next releases (e.g. 4.0) will introduce such issues we should
> > provide migration scripts.
> >
> >
> > [1]
> http
Maxim,
What you propose is
1) Take Ignite 2.x, remove some deprecated features, and release that as
Ignite 3.0
2) Much later, release what is being worked on in ignite-3 as Ignite 4.0 or
5.0
Do I understand this correctly?
On Tue, Mar 9, 2021 at 7:15 PM Ilya Kasnacheev
wrote:
> Hello!
>
> 0.
Can we include the fix for this as well? I'm working on it.
https://issues.apache.org/jira/browse/IGNITE-14293
On Mon, Mar 8, 2021 at 9:18 PM Maxim Muzafarov wrote:
> Folks,
>
> The vote cancelled. The following issues need to be addressed:
> https://issues.apache.org/jira/browse/IGNITE-14284
>
Pavel Tupitsyn created IGNITE-14293:
---
Summary: .NET: AffinityKey does not work
Key: IGNITE-14293
URL: https://issues.apache.org/jira/browse/IGNITE-14293
Project: Ignite
Issue Type: Bug
on" flag is sent with the request. WDYT?
>
> пт, 5 мар. 2021 г. в 17:03, Ivan Daschinsky :
>
> > Agree, this is completely offtopic here.
> >
> > пт, 5 мар. 2021 г. в 17:02, Pavel Tupitsyn :
> >
> > > > custom DSL
> > > This is a topic for
Maxim,
This proposal goes against [1], as I understand.
Ignite 3.0 development is going on in [2]
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-3-0-development-approach-td49922.html
[2] https://github.com/apache/ignite-3
On Sun, Mar 7, 2021 at 11:04 AM Nikolay Izhikov
t users want this
> variant.
>
> пт, 5 мар. 2021 г. в 16:52, Pavel Tupitsyn :
>
> > > I suppose this is of questional usability, same for existing
> > > implementation for ScanQuery and ContinousQuery
> >
> > One way or another, we need to be able to run
create custom Receiver this way.
>
> пт, 5 мар. 2021 г. в 15:54, Pavel Tupitsyn :
>
> > > How do you suggests to serialize this object?
> >
> > Like a normal binary object. This scenario already exists for ScanQuery
> and
> > ContinuousQuery filters.
> >
serialize this object?
> > Implement custom classloader for java? What about other platforms?
> >
> > I suppose that we should not add this field, because it is confusing.
> > Everything will work for local unit tests and only for java.
> > But in real environment this wi
r effort.
> >
> > BTW, are you sure that receiver should be a param of
> > STREAMER_START_REQUEST?
> > Receiver is mostly internal stuff and I can hardly imagine why
> > someone would decide to change defaults.
> >
> > пт, 5 мар. 2021 г. в 13:01, Pavel Tupit
to choose.
>
> Best Regards,
> Igor
>
>
> On Thu, Mar 4, 2021 at 3:14 PM Pavel Tupitsyn
> wrote:
>
> > Igniters,
> >
> > Please review the IEP [1] and let me know what you think.
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-68%3A+Thin+Client+Data+Streamer
> >
>
Igniters,
Please review the IEP [1] and let me know what you think.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-68%3A+Thin+Client+Data+Streamer
+1 (binding)
Checked binary packages, started nodes, .NET examples, .NET nodes
On Wed, Mar 3, 2021 at 11:03 PM Maxim Muzafarov wrote:
> Dear Community,
>
> The release candidate is ready. The rest of the documentation pages
> will be completed prior to the release announcement message. Please,
I think we agreed to make thin client attributes String-only [1]
However, this does not seem to be the case right now.
Anyway, I'd like to avoid complicating the protocol even further with magic
suffixes.
Can we simply use a String instead of an array?
[1]
Hi,
u...@ignite.apache.org address is reachable.
However, it looks like you have an http address instead of the email
address, which probably does not work:
"https://lists.apache.org/list.html?u...@ignite.apache.org;
On Fri, Feb 26, 2021 at 5:28 PM Sean Chen wrote:
> Hi team,
>
> Is
gt;
>
> On Fri, Feb 19, 2021 at 4:55 AM Pavel Tupitsyn (Jira)
> wrote:
>
> > Pavel Tupitsyn created IGNITE-14208:
> > ---
> >
> > Summary: .NET: Examples multi targeting
> > Key: IGNITE-1
Pavel Tupitsyn created IGNITE-14243:
---
Summary: .NET: Upgrade ConfigurationManager dependency
Key: IGNITE-14243
URL: https://issues.apache.org/jira/browse/IGNITE-14243
Project: Ignite
Issue
+1
- Close inactive PRs (1 month or so?)
- Enable main branch protection (no force pushes, require linear history,
require status checks)
On Sat, Feb 20, 2021 at 2:31 PM Petr Ivanov wrote:
> Hi, Igniters!
>
>
> When we started Ignite 3.x in new repository, not only we have received a
> chance
Pavel Tupitsyn created IGNITE-14208:
---
Summary: .NET: Examples multi targeting
Key: IGNITE-14208
URL: https://issues.apache.org/jira/browse/IGNITE-14208
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-14187:
---
Summary: .NET Thin Client: DataStreamer
Key: IGNITE-14187
URL: https://issues.apache.org/jira/browse/IGNITE-14187
Project: Ignite
Issue Type: New
hought we want to avoid this.
>
> Anyway, I’m OK with the built-in extension of BinaryBasicNameMapper.
> Will do those changes.
>
> > 13 февр. 2021 г., в 13:07, Pavel Tupitsyn
> написал(а):
> >
> > Nikolay,
> >
> > 1) What about the org./com. prefix t
Pavel Tupitsyn created IGNITE-14173:
---
Summary: .NET: TestReconnectToOldNodeDisablesPartitionAwareness
fails
Key: IGNITE-14173
URL: https://issues.apache.org/jira/browse/IGNITE-14173
Project: Ignite
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,
> >
> > This is a very good point, thank you for the heads up.
> >
> > The propos
Pavel Tupitsyn created IGNITE-14116:
---
Summary: .NET: Review LongRunning tests
Key: IGNITE-14116
URL: https://issues.apache.org/jira/browse/IGNITE-14116
Project: Ignite
Issue Type
of thin clients)
>
> [1]: https://issues.apache.org/jira/browse/IGNITE-10960
>
> пн, 1 февр. 2021 г. в 19:33, Pavel Tupitsyn :
>
> > Igniters,
> >
> > Please review the IEP [1] and let me know your thoughts.
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-66%3A+Thin+Client+Automatic+Binary+Configuration
> >
>
Igniters,
Please review the IEP [1] and let me know your thoughts.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-66%3A+Thin+Client+Automatic+Binary+Configuration
Pavel Tupitsyn created IGNITE-14103:
---
Summary: .NET Thin Client: Retrieve binary configuration from
server
Key: IGNITE-14103
URL: https://issues.apache.org/jira/browse/IGNITE-14103
Project: Ignite
Pavel Tupitsyn created IGNITE-14101:
---
Summary: .NET Thin Client: Add connection limit configuration
property.
Key: IGNITE-14101
URL: https://issues.apache.org/jira/browse/IGNITE-14101
Project
Pavel Tupitsyn created IGNITE-14076:
---
Summary: Exponential putAll performance degradation in
transactional cache
Key: IGNITE-14076
URL: https://issues.apache.org/jira/browse/IGNITE-14076
Project
Pavel Tupitsyn created IGNITE-14064:
---
Summary: .NET: Incorrect table name when query type is generic
Key: IGNITE-14064
URL: https://issues.apache.org/jira/browse/IGNITE-14064
Project: Ignite
Pavel Tupitsyn created IGNITE-14047:
---
Summary: .NET: Release build fails because of missing nuget
executable
Key: IGNITE-14047
URL: https://issues.apache.org/jira/browse/IGNITE-14047
Project
There are quite a lot of issues with the `newbie` label [1],
we usually recommend them to the new contributors.
This label is also mentioned on wiki [2]
[1]
https://issues.apache.org/jira/issues/?jql=project%3Dignite%20and%20labels%3Dnewbie%20and%20status%3Dopen
[2]
Pavel Tupitsyn created IGNITE-14045:
---
Summary: .NET: Examples tests fail on .NET Core 3 nightly run
Key: IGNITE-14045
URL: https://issues.apache.org/jira/browse/IGNITE-14045
Project: Ignite
> I wonder if the dev email is a good place to ask questions
Yes, dev email is the best place! Don't hesitate to ask anything in this
thread
or create a new one if needed.
On Fri, Jan 22, 2021 at 12:36 AM Nathan Chan
wrote:
> Hi Pavel,
>
> Yes, it seems like I missed it, but the weird thing is
Pavel Tupitsyn created IGNITE-14033:
---
Summary: .NET: MessagingTest is flaky
Key: IGNITE-14033
URL: https://issues.apache.org/jira/browse/IGNITE-14033
Project: Ignite
Issue Type: Bug
Pavel Tupitsyn created IGNITE-14032:
---
Summary: IgniteMessaging.stopRemoteListen does not remove remote
listeners immediately
Key: IGNITE-14032
URL: https://issues.apache.org/jira/browse/IGNITE-14032
Hi Kin,
Did you miss my reply to the previous email? [1]
I've added you to the contributors list, and suggested some tickets.
[1]
https://lists.apache.org/thread.html/r2dcdaed7c65aa655cc5d1d9ed795f55b070a95937bcb9d831a4075ff%40%3Cdev.ignite.apache.org%3E
On Thu, Jan 21, 2021 at 8:37 AM Nathan
1] https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-new
On Tue, Jan 19, 2021 at 8:33 PM Pavel Tupitsyn wrote:
> Igniters,
>
> The PR is ready for your review, everyone is welcome.
>
> https://github.com/apache/ignite/pull/8651
>
>
> On Tue, Jan 12, 2021 at 7:50 PM Pavel T
Igniters,
The PR is ready for your review, everyone is welcome.
https://github.com/apache/ignite/pull/8651
On Tue, Jan 12, 2021 at 7:50 PM Pavel Tupitsyn wrote:
> Hi Sergey,
>
> Good point, but I don't think using a newer SDK is any better for the
> examples:
> * Oldest LT
Maxim,
No objections for .NET-related cherry-picks.
Thank you!
On Mon, Jan 18, 2021 at 4:52 PM Никита Сафонов
wrote:
> Hi Maxim et al,
>
> Thank you very much!
> I do appreciate your help!
>
> Regards,
> Nikita
>
> пн, 18 янв. 2021 г. в 16:16, Maxim Muzafarov :
>
> > Folks,
> >
> > I'd like
t; the Java side.
> So, for all classes that is used only in .Net nothing will change.
>
>
> > 13 янв. 2021 г., в 15:14, Pavel Tupitsyn
> написал(а):
> >
> >> Classes MUST be registered to be used in compute or cache.
> >
> > Yes, but they are regist
we use the same class
> names both in Java and .Net.
>
> > This is not up for discussion, we do not break compatibility like this.
>
> Sorry, I don’t see compatibility issues in the proposal.
> Can you, please, provide an example?
>
> > 13 янв. 2021 г., в 13:46, Pavel
per requires from the user to have exactly same names for
> custom binary types in Java and .Net.
> 3. Improvals for Services in master, already.
>
> [1]
> https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/Services/ServiceTypeAutoResolveTe
s.
> >
> > Also, why register types which are used as method arguments for any
> > service? Wouldn't
> > it be more reasonable to only register those which are used with Java
> > services?
> >
> > Best Regards,
> > Igor
> >
> >
> > On Tue, Jan 12,
; 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
Nikolay,
I think this behavior should be opt-in - let's add a flag to
BinaryConfiguration.
Registering every .NET type as a Java type can lead to typeId collisions
and break existing user code,
so we can't enable this by default.
Ignite stores typeId -> className mappings separately for Java
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]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-65%3A+.NET+Examples+Modernization
Pavel Tupitsyn created IGNITE-13979:
---
Summary: .NET: Modernize examples
Key: IGNITE-13979
URL: https://issues.apache.org/jira/browse/IGNITE-13979
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-13957:
---
Summary: GridQueryProcessor.validateKeyAndValue attempts to
deserialize key and value when QueryEntity.fields is not set
Key: IGNITE-13957
URL: https://issues.apache.org
Igor,
The idea is to keep partition awareness enabled
even when the limit is reached, right?
So it works when the corresponding server is available,
and ignored otherwise.
I think this could be useful, but we should document it thoroughly,
so the negative effect on partition awareness
Ivan, thank you for fixing this!
On Wed, Dec 23, 2020 at 11:13 AM Ivan Pavlukhin wrote:
> Actually a first attempt was not successful. And the reason was "main"
> branch name. I asked INFRA folks assistance and as I understood they
> configured GitBox HEAD to be "main" branch HEAD. I suppose it
Ivan, it is the new GitHub default
"On Oct. 1, 2020, any new repositories you create will use main as the
default branch, instead of master" [1]
[1]
https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/
On Tue, Dec 22, 2020 at 1:12 PM Ivan Pavlukhin wrote:
>
Pavel Tupitsyn created IGNITE-13883:
---
Summary: .NET: Performance: Refactor
BinarySystemHandlers.TryReadSystemType to switch-case
Key: IGNITE-13883
URL: https://issues.apache.org/jira/browse/IGNITE-13883
Pavel Tupitsyn created IGNITE-13859:
---
Summary: .NET: Build scripts and instructions cleanup
Key: IGNITE-13859
URL: https://issues.apache.org/jira/browse/IGNITE-13859
Project: Ignite
Issue
+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/
>
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
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
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
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
301 - 400 of 1759 matches
Mail list logo
