rsonally prefer the closeable iterator approach, since it is
> what
> > most Java libraries use and most users should be familiar with it. Also
> > most IDEs will warn you, if you don't close an AutoCloseable.
> >
> > On Fri, Jun 24, 2022 at 6:24 PM Pavel Tupitsyn
> &
Igniters,
I'm working on IgniteSet in Java thin client [1], and I'm not sure how to
deal with iterator release.
On the "thick" API side we use WeakReferenceCloseableIterator [2] to
release iterator resources automatically when the iterator instance is
claimed by GC.
a) Reuse this on the client
Hi,
I've added you to the Contributors group in JIRA.
Welcome to the Apache Ignite community!
On Fri, Jun 24, 2022 at 5:21 PM wkhapy...@gmail.com
wrote:
> Hi,
>
> I am interesting in ignite. I want to contribute to Apache ignite .
>
> Would you please give me the contributor permission?
>
>
Aleksey,
I fully support the idea of a common tuple format to avoid conversions when
passing data around (servers, clients).
The IEP looks good to me.
> Integer Field Compression
Agree with this, we can even extend the idea to float/double fields.
> size of table elements might be 1, 2, 4, or
+1 (binding)
On Fri, Jun 10, 2022 at 4:35 PM Igor Sapego wrote:
> +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>
>
question is - can we have the following version
> > committed in the source files 2.14.0.0, but when the 'release' profile
> > get activated (or probably the build happened) revision number will
> > changed to 2.14.0.62943? This will be the final release version ready
> As for the last number in .NET version, AFAIK it is used as the unique
> build id and is required for nightly builds as nuget doesn't have
> functionality a-la maven's 'snapshots'
NuGet supports string suffixes like 2.15.0-nightly1. However,
AssemblyVersionAttribute does not.
In some cases it
Igniters, I'd like to include the following ticket as well:
IGNITE-17057 Thin 3.0: Implement synchronous SQL API for java thin client
[1]
Would be great to have the same API available in server and client modes.
It'll be in main in a couple hours.
[1]
requests with an error and RetryPolicy
will deal with them up the call stack.
On Fri, May 20, 2022 at 12:02 PM Pavel Tupitsyn
wrote:
> Another point:
>
> With the current proposal, there is no way for the server to distinguish
> a broken connection from a normal user-initiated connection c
l change
> the IEP accordingly.
>
> Best Regards,
> Igor
>
>
> On Thu, May 19, 2022 at 11:40 PM Pavel Tupitsyn
> wrote:
>
> > Igor,
> >
> > I've started working on the initial sessions implementation [1],
> > and I'd like to clarify the procedure of
server: restore logical connection,
return the same connectionId
Client checks if returned connectionId equals to the original and
understands whether logical connection was restored or not.
Thoughts?
[1] https://issues.apache.org/jira/browse/IGNITE-16928
On Thu, May 19, 2022 at 10:27 PM Pavel Tu
arify IDs part;
> > 2. Maybe you are right, though in this case we'd need to use
> authentication
> > in ConnectionRestoreReq. Which sounds reasonable to me.
> >
> > Best Regards,
> > Igor
> >
> >
> > On Tue, May 17, 2022 at 10:47 AM Pavel
Igor,
The proposal looks good to me. Very detailed!
A couple comments:
1. There is a bit of a term mixup with "Connection ID", "Node ID", "Token"
- can you please review those?
2. > The Connection ID should be generated using a proper secure algorithm
(additional research is required here) to
Added to Contributors group in JIRA
On Fri, May 6, 2022 at 5:40 PM Mikhail Pochatkin
wrote:
> Hello, Pavel.
> Only, Mikhail Pochatkin
>
> On Fri, May 6, 2022 at 4:29 PM Pavel Tupitsyn
> wrote:
>
> > Hello Mikhail,
> >
> > Welcome to the Apache Igni
Hello Mikhail,
Welcome to the Apache Ignite community!
I've added you to Confluence.
However, I see a few matching accounts in JIRA, with the following
usernames:
krokpop, MikhailPochatkin, PochatkinMikhail, Mikhail Pochatkin.
Which one of those is yours?
On Fri, May 6, 2022 at 1:52 PM Mikhail
+1, this is awesome
On Fri, Apr 29, 2022 at 3:26 PM Nikita Safonov
wrote:
> +1
>
> Cannot but support!
>
> Thanks,
> Nikita
>
> сб, 23 апр. 2022 г. в 17:47, Maxim Muzafarov :
>
> > Hello,
> >
> > +1, great improvement.
> >
> > On Sat, 23 Apr 2022 at 17:26, Nikita Amelchev
> > wrote:
> > >
> >
To summarize, those issues are specific to Alpine Linux
1. dlopen issue was fixed in 2.13:
https://issues.apache.org/jira/browse/IGNITE-13011
2. LD_LIBRARY_PATH env var should be set
to /usr/lib/jvm/default-jvm/jre/lib/amd64/server for openjdk8,
/usr/lib/jvm/default-jvm/jre/lib/server for
Hello, please send any email to dev-subscr...@ignite.apache.org to get
started.
On Mon, Apr 11, 2022 at 4:21 PM Lokesh Bandaru
wrote:
> Hello, writing with regards the developer mailing list membership.
>
> Thanks.
>
Hello Yoann,
I've added you to the Contributors group in JIRA, so you can work with
tickets.
Please have a look at our wiki [1]
Welcome to the Apache Ignite community!
[1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
On Sun, Mar 20, 2022 at 6:36 PM Yoann Ozaneaux
I've reviewed the code again and it does not seem right to override
user-defined heartbeat interval with a *bigger* value,
so now I only set it to 1/3 of idleTimeout when the user-specified value is
not already less than that.
On Wed, Feb 16, 2022 at 7:19 PM Pavel Tupitsyn wrote:
> Ok, le
Ok, let's keep heartbeatInterval then.
I've updated the code to reflect our recent agreement, please review.
On Tue, Feb 15, 2022 at 8:28 PM Ivan Daschinsky wrote:
> I personally prefer heartbeatInterval
>
> вт, 15 февр. 2022 г., 18:25 Pavel Tupitsyn :
>
> > >
any
of them.
Any other opinions?
On Tue, Feb 15, 2022 at 6:11 PM Maksim Timonin
wrote:
> What about "keepAlive", "keepAliveInterval" then? It looks more common and
> matches the IEP title :)
>
> On Tue, Feb 15, 2022 at 5:54 PM Pavel Tupitsyn
> wrote:
>
>
вр. 2022 г., 14:54 Ivan Daschinsky :
>
> > > Idle timeout can't change, why send it back with every heartbeat
> > response?
> > May be I am wrong, but from code I see this behaviour. But if I am wrong,
> > this is ok behaviour for me.
> >
> >
> >
> >
clients
> > on timeout -- this will not work without reconfiguring, he should disable
> > heartbeats.
> > But I cannot even imagine that someone will find this behaviour
> desirable.
> > I strongly believe that this behaviour prevents users from using
> > idleTimeout on se
orth kick these clients out.
>
> пн, 7 февр. 2022 г. в 18:25, Pavel Tupitsyn :
>
> > > If we use new approach, we can reduce this timeout. But this can affect
> > old clients.
> >
> > idleTimeout is disabled by default, we are not going to change this.
&
at sending heartbeats and interval of sending
> heartbeats could be calculated on the server side (i.e. one third of idle
> timeout) and sent to the client
> during handshake.
> Also we can introduce something like a negotiation mechanism as in
> zookeeper.
>
>
> пн, 7 февр.
kind of timers to
> implement
> this feature?
>
> Best Regards,
> Igor
>
>
> On Mon, Feb 7, 2022 at 5:23 PM Pavel Tupitsyn
> wrote:
>
> > Maksim, agree. Let's not be too clever and only log a warning.
> >
> > On Mon, Feb 7, 2022 at 5:23 PM Pavel Tu
Maksim, agree. Let's not be too clever and only log a warning.
On Mon, Feb 7, 2022 at 5:23 PM Pavel Tupitsyn wrote:
> Ivan, idleTimeout already exists, I don't think we should change the way
> it works (or did I misunderstand you?)
>
> Of course, enabling heartbeats means that ot
hange dynamically, for example
> restarting a
> > cluster with different configuration should reconfigure clients too.
> Looks
> > complicated.
> >
> > My vote for WARN + javadocs with mention of this issue.
> >
> > On Mon, Feb 7, 2022 at 3:51 PM P
configure
> keepAliveTimeout greater than idleTimeout on the server side?
>
>
>
> On Mon, Feb 7, 2022 at 1:05 PM Pavel Tupitsyn
> wrote:
>
> > Ivan,
> >
> > I suggest the following:
> >
> > 1. Server sends KEEP_ALIVE feature flag, which means it
no requests from client
> with KEEP_ALIVE feature,
> automatically close connection and free resources.
>
> Similar approach is used in zookeeper clients.
>
> пн, 7 февр. 2022 г. в 12:24, Pavel Tupitsyn :
>
> > Ivan,
> >
> > Ideally, the check should come from both sides.
&
ndles and so on?)
>
> пн, 7 февр. 2022 г. в 11:09, Pavel Tupitsyn :
>
> > Hi Maksim,
> >
> >
> > > half-state is a possible situation when an Ignite node goes down or
> > somehow removes connection to a thin client
> >
> > Half-open stat
ve idle connections? Are there
> any other cases with unexpectedly dropped connections?
>
> I'm wondering is it OK to keep such connections alive for a long time?
> Also in the case of partition awareness features it can lead to wasting TCP
> sockets on Ignite nodes, can't it?
>
&
Igniters,
Please review the proposal to add heartbeat messages to the thin client
protocol (both 2.x and 3.x) and let me know your thoughts:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-83+Thin+Client+Keepalive
Vladimir, I think we should make the same changes to the .NET API.
On Tue, Jan 25, 2022 at 5:17 PM Vladimir Steshin wrote:
> Similar question about .NET. I'm doing the sub-ticket with metrics
> of the platform services. Should we return proxy every tome by
> /IServices.GerServiceProxy()/
+1 to option 2
On Thu, Jan 13, 2022 at 3:52 PM Roman Puchkovskiy <
roman.puchkovs...@gmail.com> wrote:
> +1 to option 2
>
> чт, 13 янв. 2022 г. в 15:58, Sergey :
> >
> > +1 for option2 (only @Nullable)
> >
> > Best regards,
> > Sergey Kosarev.
> >
> >
> > чт, 13 янв. 2022 г. в 13:25, Alexander
Hi Brennan,
I've granted you contributor access in JIRA.
Welcome to the Apache Ignite community!
The ticket looks good to me, I've only set the fix version.
Will review the PR now.
Thanks,
Pavel
On Tue, Jan 11, 2022 at 5:15 PM Brennan Fox wrote:
> Hi Ignite team,
>
> May I please have
For some reason, .NET docs were not built during 2.11.1 release.
They are missing both on the website and in zip files.
Unfortunately, TeamCity logs are no longer available, so the reason is not
clear.
I've double-checked that the upcoming 2.12 release does not have this
problem [1]
[1]
+1
Checked .NET binaries, docs, examples, nuget packages.
On Mon, Jan 10, 2022 at 3:53 PM Nikita Amelchev
wrote:
> Dear Community,
>
> The release candidate (2.12.0-rc2) is ready.
>
> I have uploaded a release candidate to:
> https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc2/
>
> Pavel, thank you.
> >
> > The "[3] Build & Upload Nuget Staging Packages" configuration also
> > pushes packages to the MyGet.
> > Will packages be published to some package registry?
> >
> > чт, 30 дек. 2021 г. в 10:15, Pavel Tupitsyn :
> > &g
2Frelease-2.12.0-rc1.zip!%2Fsvn%2Fvote%2Fapache-ignite-2.12.0-nuget.zip
On Thu, Dec 30, 2021 at 9:29 AM Pavel Tupitsyn wrote:
> Hello Nikita,
>
> I'll have a look.
>
> On Wed, Dec 29, 2021 at 6:12 PM Nikita Amelchev
> wrote:
>
>> Hello. Petr, Pavel,
>>
>&g
> >
> > > >> > > > Thanks,
> > > >> > > > S.
> > > >> > > >
> > > >> > > > ср, 15 дек. 2021 г. в 21:45, Nikita Amelchev <
> namelc...@apache.org
> > > >> >:
> > > >&g
Java thin client changes are ready for review:
https://issues.apache.org/jira/browse/IGNITE-16026
https://github.com/apache/ignite/pull/9701
On Tue, Nov 30, 2021 at 2:09 PM Pavel Tupitsyn wrote:
> Igniters,
>
> Since there are no more comments, I've created the tickets and will work
Hi Igor,
Added you to the Contributors group in JIRA.
Welcome to the Apache Ignite community!
On Tue, Dec 28, 2021 at 11:24 AM Igor Zadubinin
wrote:
> I’d like to join the community and contribute to the Ignite website.
> Please grant me contributors’ permissions in JIRA. My JIRA account is
>
+1
Checked .NET binaries, nugets, and examples.
On Mon, Dec 20, 2021 at 3:42 PM Ilya Kasnacheev
wrote:
> Hello!
>
> +1
>
> There seems to be a correct version of log4j2 now.
>
> Btw, I've noticed that we ship log2j 1.x with ignite-rest-http. This is
> quite bad.
>
> Regards,
> --
> Ilya
lable. In most cases, the
> user even no need to know about this new interface.
>
> I'm voting for option (3).
>
> чт, 16 дек. 2021 г. в 15:59, Pavel Tupitsyn :
>
> > Pavel,
> >
> > My vote is for option (1). Simple and clear.
> >
> > As you noted, with (2
+1
Checked binary packages, .NET examples and NuGets.
On Fri, Dec 17, 2021 at 3:20 PM Maxim Muzafarov wrote:
> The release candidate for the 2.11.1 version is ready.
>
>
> I have uploaded a release candidate to:
> https://dist.apache.org/repos/dist/dev/ignite/2.11.1-rc1/
>
> And it still can be done from separate repository.
>
>
> Choosing one of the project's repo to host settings for every other
> project seems non-logical — why should I edit code in Apache Ignite 2.x
> repo to introduce new changes in Apache Ignite 3.x build settings?
>
> > On 17 De
itory should be separate.
> And when JB will fix the branches issues — we still will be able to use it
> with creating branches with the same name on both project and TC repository.
>
> > On 17 Dec 2021, at 14:06, Pavel Tupitsyn wrote:
> >
> > Witaliy,
> >
> >&
Witaliy,
> repository is created
> only in the master branch
I strongly suggest avoiding a separate repository for project settings.
Let's store them in https://github.com/apache/ignite
*1. We should be able to test code changes together with CI/CD changes.*
*2. We should be able to have
Option 2 seems the most sensible.
It translates to/from other languages and should be already familiar to
some developers.
For example, with nullable checks enabled, C# treats everything as not
null, unless specified otherwise with "?".
Same for other languages where Option/Maybe type is present.
; > > On Tue, Oct 19, 2021 at 11:47 AM Pavel Pereslegin
> wrote:
> > > >
> > > >>> Removing parameters from a public interface method is a breaking
> change,
> > > >>> or do you mean something else?
> > > >>
> > &g
Maxim,
Thanks for taking this, scope looks good to me.
I think we can even start the vote today or tomorrow, given the severity of
log4j issue.
Pavel
On Thu, Dec 16, 2021 at 3:44 PM Maxim Muzafarov wrote:
> Dear Ignite Community!
>
> I suggest preparing the Apache Ignite 2.11.1 release and I
Igniters,
Looks like we need to update to 2.16, there is an additional attack vector
[1]
[1]
https://www.lunasec.io/docs/blog/log4j-zero-day-update-on-cve-2021-45046/
On Mon, Dec 13, 2021 at 4:06 PM Maxim Muzafarov wrote:
> Folks,
>
> Should we describe all the WA available for the issue [1]?
gt;>>>>>> Hello everyone,
> >>>>>>>>
> >>>>>>>> is there a chance to add this issue to the release scope? [1]
> >>>>>>>> Currently, defragmentation of certain types of indexes can
> corrupt them.
> >>>>>&
nly experimental
> since 2.12), and extend it on ScanQuery later after stabilizing with
> IndexQuery. WDYT?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12591
>
> On Thu, Dec 9, 2021 at 10:39 AM Pavel Tupitsyn
> wrote:
>
> > Agree with Ivan regarding compatibilit
Agree with Ivan regarding compatibility.
Partition reservation should be opt-in if we decide to proceed.
> is there a real need/benefit from using
> scan queries over primitive SQL queries today
SQL requires additional configuration (QueryEntity) and involves memory and
CPU overhead to maintain
Hello Andrey,
I've added you to the Contributors group in JIRA.
Welcome to the Apache Ignite community!
Pavel
On Tue, Dec 7, 2021 at 12:55 PM Андрей Беляев
wrote:
> Hello, my name is Andrey Belyaev. I want to contribute to the project.
> Could you please give me permissions for contributing
Hi Erlan,
Added you to the contributors role in JIRA.
Welcome to the Apache Ignite community!
Pavel
On Mon, Dec 6, 2021 at 9:36 AM Erlan Aytpaev wrote:
> Hi, Igniters,
>
> My name is Erlan. I'm a seasoned full-stack developer (PHP/JS) with over 10
> years experience.
>
> I'd like to join the
Maxim,
> I don't think that we should wait for 3-rd party plugins to be updated
> this is an awful practice when the open-source product releases depend
> on some of the proprietary plugins
This makes no sense, sorry.
It is not that we depend on 3rd party plugins.
It is that *our users depend
Hello Sarra,
Ignite considers two objects equal when both are true:
- Type ID is the same (same class).
- Serialized representation (byte[]) is the same.
Ignite does not use standard equals() and hashCode() for comparisons
because the DB engine operates on serialized data.
We are not aware of
Igniters,
Since there are no more comments, I've created the tickets and will work on
them soon.
[1] https://issues.apache.org/jira/browse/IGNITE-16025
[2] https://issues.apache.org/jira/browse/IGNITE-16026
On Thu, Nov 25, 2021 at 1:44 PM Pavel Tupitsyn wrote:
> Igor,
>
> I think
tx parameter,
> because
> > > that will pretty much eliminate the value of this change. One thing we
> > can
> > > do to address this is to have separate "non-tx" views, which can only
> be
> > > used to execute implicit transactions. But I would
y of forgetting
> to enlist a table into a transaction, because it is not enforced.
> Having the explicit argument for this purpose seems less error-prone to me.
>
> пн, 29 нояб. 2021 г. в 15:13, Pavel Tupitsyn :
>
> > Taras, yes, yours is the actual syntax in main branch right n
syntax (see below) to attach the table / operation to the
> started transaction?
> RecordView txPersonView =
> person.recordView().withTransaction(txView.transaction());
>
>
> On Mon, Nov 29, 2021 at 1:34 PM Pavel Tupitsyn
> wrote:
>
> > Alexei,
> >
> >
Alexei,
I agree that runInTransaction is confusing and error-prone.
But we already have view.withTransaction(), which seems to be the most
boilerplate-free approach.
The example above will look like this:
public void testMixedPutGet() throws TransactionException {
RecordView view =
vel,
>
> 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 prepare
Igniters,
I've prepared a proposal about thin client retry behavior.
Please review and let me know your thoughts.
https://cwiki.apache.org/confluence/display/IGNITE/IEP-82+Thin+Client+Retry+Policy
> >>>>>> Folks,
> >>>>>>
> >>>>>> I've fixed almost all the review comments [1]. Hopefully, the
> changes
> >>>>>> will be merged by the end of the week.
> >>>>>>
> >>>>>> [
; >> > Hello, Pavel.
> >> >
> >> > The code freeze is blocked by two issues discussed above [1] [2]. The
> >> > issues are in the final review state and should be merged soon.
> >> >
> >> > The bugfix is useful and can be cherry-picked,
Denis,
The new design looks good.
A few comments:
- Will we have a "news" section? We can list release announcements, links
to new talks and blogs, and so on there.
- Main page section "Resources To Elevate Your Ignite Experience" has 6
panels (technical and learning resources), I would expect
gt; > > > > >
> > > > > > On Thu, Oct 28, 2021 at 11:06 AM Ilya Kasnacheev <
> > > > ilya.kasnach...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello!
> > > > > > >
> > &g
Hi Ivan,
Yes, looks like a non-zero exit code is a problem. I'll have a look next
week.
Thanks!
On Wed, Nov 3, 2021 at 11:22 AM Ivan Daschinsky
wrote:
> Hi folks!
>
> Some people found, that recently it is quite hard to obtain green visa of
> tcbot due to some circumstances.
>
> After some
freeze?
>
> ср, 27 окт. 2021 г. в 14:25, Pavel Tupitsyn :
>
> > Ivan, IGNITE-15806 seems to be a minor refactoring, not sure we should
> > inflate the scope with this.
> >
> > On Wed, Oct 27, 2021 at 2:13 PM Ivan Daschinsky
> > wrote:
> >
> > > Nik
Ivan, IGNITE-15806 seems to be a minor refactoring, not sure we should
inflate the scope with this.
On Wed, Oct 27, 2021 at 2:13 PM Ivan Daschinsky wrote:
> Nikita, can we add https://issues.apache.org/jira/browse/IGNITE-15806 this
> ticket for release?
>
> ср, 27 окт. 2021 г. в 13:40, Maksim
Release build issues (IGNITE-15779) should be resolved now.
On Fri, Oct 22, 2021 at 5:38 PM Сергей Утцель wrote:
> I configured TC bot to 'ignite-2.12' instead of 'ignite-2.11'
>
cumentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
>
> пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn :
> >
> > I'm working on IGNITE-15504 and plan to finish it early next week.
> >
> > On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev
> wrote
t; > >@ServiceRequestContextResource
> > > >private Function ctxFunc;
> > > >
> > > > Because, we use this style of API for injection of other resources -
> > > > logger, ignite instance, etc.
> > > > It may be confusing for the user to
which is very counterintuitive. Even more importantly, how should
> one
> > > > learn
> > > > >> about this requirement in the first place? It is not reflected in
> the
> > > > API
> > > > >> in any way - and tha
to SVN [1] for RC testing. Let's start doing this with
> the next release.
>
> I also assume this will be useful for both 2.x and 3.x, right?
>
> [1] https://dist.apache.org/repos/dist/dev/ignite
>
> -Val
>
> On Thu, Oct 14, 2021 at 12:15 PM Pavel Tupitsyn
> wrote:
>
;> > That's actually by design. The current packaging model assumes that
> we
> > >> use
> > >> > Maven/NuGet to deliver binaries - both for servers side and client
> > >> side. In
> > >> > case you have any obj
To clarify, Java thin client has the following features:
- Table API
- Key-value API
- JDBC driver
.NET thin client:
- Table API
I think all of this should be included in the binary release.
On Wed, Oct 13, 2021 at 10:10 AM Pavel Tupitsyn
wrote:
> -1 (binding)
>
> Java thin client
-1 (binding)
Java thin client and .NET thin client are missing from the binary package.
On Wed, Oct 13, 2021 at 3:03 AM Saikat Maitra
wrote:
> +1 (binding)
>
> Regards
> Saikat
>
> On Tue, Oct 12, 2021 at 5:03 PM Denis Magda wrote:
>
> > +1 (binding)
> >
> > -
> > Denis
> >
> >
> > On Tue,
common approach everywhere and is
> very useful in distributed systems. The use cases are so obvious, aren't
> they?
>
>
>
> сб, 9 окт. 2021 г., 20:14 Pavel Tupitsyn :
>
> > Pavel,
> >
> > Thanks for the explanation, I understand the use cases.
> >
> > &g
all calls
> This feature is optional, if the context is not passed - then there's
> shouldn't be any performance difference.
>
> > Ambient state is not obvious and the API looks confusing even though I
> understand our services stack quite well both in Java and .NET
> Can you
Agree with Igor.
I'm not sure this feature is a good fit for Ignite.
Ignite should not be responsible for such a high-level concept, this should
be on the application side instead.
- As Eduard noted, it is hard to make this type-safe
- Ambient state is not obvious and the API looks confusing
-1
We have already started using the existing JIRA and Confluence.
There are lots of tickets, IEPs, and commits interlinked with each other.
Introducing a new JIRA and Confluence will cause a huge mess.
On Wed, Oct 6, 2021 at 7:57 PM Denis Magda wrote:
> Val,
>
> As we discussed earlier, I
using Visual C++ 2017?
> > >
> > > 2015, 2017 and 2019 share the same redistributable package and it is
> the
> > > default one in Windows 10.
> > >
> > > Also, let's remove vs project files, since the most of you all agree
> that
> > > it is redundant.
&
Hi Raymond,
1. Please register an account on TeamCity (ci.ignite.apache.org), you'll be
able to start builds right away.
2. Login with the same credentials to https://mtcga.gridgain.com/prs.html
and schedule a build for your PR.
See
rations/spring/spring-tx#maven-configuration
>
>
> > On 23 Sep 2021, at 18:49, Dmitry Pavlov wrote:
> >
> > Thanks to Maxim and kudos to Alexey Gidaspov, who was serving role of
> Release manager during all init, rampdown and stabilization phase.
> >
> > Sincerely,
>
Hi Raymond,
I've added you to the Contributors group in JIRA, now you should be able to
assign issues, change their status, etc.
On Mon, Sep 27, 2021 at 12:25 AM Raymond Wilson
wrote:
> Hi,
>
> I have created a Jira ticket I would like to assign to myself:
>
+1
On Fri, Sep 24, 2021 at 8:04 PM Maxim Muzafarov wrote:
> Hello Nikita,
>
> +1 if you will lead this release.
>
>
> I'd suggest including into the release scope this one issue too:
>
> Snapshot restore must support restoring with indexes rebuild
>
af.github.io/blob/main/_post/Release_Newsletter_211.md
> > >
> > >
> > > On Thu, 16 Sept 2021 at 17:21, Maxim Muzafarov
> wrote:
> > > >
> > > > Hello, Igniters!
> > > >
> > > > Apache Ignite 2.11.0 re
ks.
>
> And don't forget about vcpkg [1]. Even microsoft goes towards cmake and
> make even package manager for it.
> And it works great, I've tried with Ignite C++.
>
> [1] -- https://github.com/microsoft/vcpkg
>
> ср, 15 сент. 2021 г. в 12:46, Pavel Tupitsyn :
>
> >
of them are present in VS files
> > First of all, BOOST_TEST is not NUnit :) Secondly, we can do that, but it
> > is not so easy as it is in .NET.
> > Yes, we can use boost libraries in tests, but why we should do it? Why we
> > should invest our time in this activity?
ch stack.
> >
> >
> > > On 15 Sep 2021, at 12:02, Ivan Pavlukhin wrote:
> > >
> > > +1 for removing VS project
> > >
> > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov :
> > >> +1
> > >>
> > >>> 15 сент. 2021 г., в
-1
This may become an obstacle for some of the users and I'm not sure how it
improves anything.
> 3. Sometimes even maintainers forget to add test sources to VS projects
[1]
We can add an automatic check for this (in form of a test).
On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky
wrote:
hy are we shipping
> something which is not for publishing in our binary package? I've also not
> heard of it before.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn :
>
> > Ilya,
> >
> > > When I have also installed 3.1
I agree with Ivan, let's return an error on any attempt to create or use a
LOCAL cache from thin clients.
On Tue, Sep 14, 2021 at 2:25 PM Ivan Daschinsky wrote:
> I am not about creation per se, but creation from a thin client side.
>
> This feature simply doesn't work as expected, broken and
> +1
> Отправлено с iPhone
Nikolay, did you test pyignite from your iPhone? Does it work? :)
On Tue, Sep 14, 2021 at 12:22 PM Николай Ижиков wrote:
> +1
>
> Отправлено с iPhone
>
> > 14 сент. 2021 г., в 11:39, Pavel Tupitsyn
> написал(а):
> >
> > +1
>
101 - 200 of 1759 matches
Mail list logo
