://github.com/apache/ignite/pull/7853/files
вт, 26 мая 2020 г. в 20:28, Sergey Antonov :
> Maxim, I've created a ticket [1] for this change.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13079
>
> вт, 26 мая 2020 г. в 20:09, Sergey Antonov :
>
>> Maxim, I'd prefer to do thi
e: July 10, 2020
> > Voting Date: July 31, 2020
> > Release Date: August 7, 2019
> >
> > WDYT?
> >
> > [1] :
> >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
> >
>
--
BR, Sergey Antonov
Guys,
I've taken the liberty of creating the ticket
(https://issues.apache.org/jira/browse/IGNITE-13110) for the proposed
changes.
I did some prototyping as well. You may find the draft code/test
changes in PR https://github.com/apache/ignite/pull/7893
Would appreciate if you can look at it and
Sergey Kalashnikov created IGNITE-13110:
---
Summary: An option to validate field types against SQL schema on
key-value insert
Key: IGNITE-13110
URL: https://issues.apache.org/jira/browse/IGNITE-13110
n
> hook. We don't know what shut down will try to do and we can't sure
> that node will actually terminated. halt() gives such guarantee.
>
> On Tue, Jun 2, 2020 at 5:35 PM Sergey Antonov
> wrote:
> >
> > Andrey, Alexey, I can't agree with your position.
>
Andrey, Alexey, I can't agree with your position.
Current implementation StopNodeOrHaltFH uses Runtime#halt(). This method
doesn't cause shutdown hooks. Why we don't try to stop the node by
System#exit() before Runtime#halt()?
вт, 2 июн. 2020 г. в 17:18, Andrey Gura :
> Sergey, Anton, Kir
I suggest using framework [1] and to do this, take out
> control.sh together with its associated classes in a separate module such
> as "modules/control-utility".
> >
> >Comments, suggestions?
> >
> >[1] - https://picocli.info/
>
>
>
>
--
BR, Sergey Antonov
Alexey,
> How exactly do you want to change the StopNodeFH?
I want to stop JVM with KILL_EXIT_CODE and add an option (constructor
argument of JVM option) for disabling JVM termination.
вт, 2 июн. 2020 г. в 12:54, Alexey Goncharuk :
> Sergey,
>
> How exactly do you want to change th
/admins/anyone who admins Ignite may want to know it's value
> without
> > going to Java code.
> >
> > чт, 21 мая 2020 г. в 09:39, Zhenya Stanilovsky
> :
> >
> >> Thank you Sergey, as for me — very useful proposal huge +1 here.
> >>
> >> >Чет
Sergey Antonov created IGNITE-13102:
---
Summary: IgniteCache#isClosed() returns false on server node even
if the cache had closed before.
Key: IGNITE-13102
URL: https://issues.apache.org/jira/browse/IGNITE-13102
Hi Ivan,
I have an idea about suggested maintenance mode.
First of all, I agree with your ideas about discovery restrictions: node
should not join topology when performing defragmentation.
At the same time I haven't heard about requests for this mode from users,
so we don't know much about
Sergey Antonov created IGNITE-13091:
---
Summary: Cluster read-only mode allows to create caches
Key: IGNITE-13091
URL: https://issues.apache.org/jira/browse/IGNITE-13091
Project: Ignite
Maxim, I've created a ticket [1] for this change.
[1] https://issues.apache.org/jira/browse/IGNITE-13079
вт, 26 мая 2020 г. в 20:09, Sergey Antonov :
> Maxim, I'd prefer to do this with a separate ticket.
>
> вт, 26 мая 2020 г. в 19:59, Maxim Muzafarov :
>
>> Sergey,
Sergey Antonov created IGNITE-13079:
---
Summary: Replace deprecated cluster activation methods in tests.
Key: IGNITE-13079
URL: https://issues.apache.org/jira/browse/IGNITE-13079
Project: Ignite
Maxim, I'd prefer to do this with a separate ticket.
вт, 26 мая 2020 г. в 19:59, Maxim Muzafarov :
> Sergey,
>
> Sounds good!
> Should we consider removing the deprecated methods `active()`,
> `active(boolean active)` from tests also?
>
> On Tue, 26 May 2020 at 12:18, Se
Sergey Stronchinskiy created IGNITE-13077:
-
Summary: .NET transaction gets overwritten for multiple Ignite
trying to start transactions in one thread
Key: IGNITE-13077
URL: https://issues.apache.org/jira
Sergey Antonov created IGNITE-13076:
---
Summary: Cluster read-only mode doesn't affect LOCAL caches
Key: IGNITE-13076
URL: https://issues.apache.org/jira/browse/IGNITE-13076
Project: Ignite
/browse/IGNITE-13071
--
BR, Sergey Antonov
Sergey Antonov created IGNITE-13071:
---
Summary: Improve test coverage for read-only cluster state
Key: IGNITE-13071
URL: https://issues.apache.org/jira/browse/IGNITE-13071
Project: Ignite
I've created the Ignite ticket for this improvement [1].
[1] https://issues.apache.org/jira/browse/IGNITE-13047
чт, 21 мая 2020 г. в 00:46, Sergey Antonov :
> Hello, Igniters!
>
> I'd like to discuss behaviour of Ignite process exit code if the node was
> stopped by failure h
Sergey Antonov created IGNITE-13047:
---
Summary: Ignite node must return Ignition#KILL_EXIT_CODE exit
code, if node had stopped by StopNodeFailureHandler or
StopNodeOrHaltFailureHandler
Key: IGNITE-13047
URL
/StopNodeOrHaltFailureHandler.html
[2]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/failure/StopNodeFailureHandler.html
[3]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/Ignition.html#KILL_EXIT_CODE
--
BR, Sergey Antonov
; > 2. Almost every system with transactions has timeout enabled by default.
> >
> > WDYT?
> >
> > --
> > Best Regards,
> > Ivan Rakov
> >
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>
--
BR, Sergey Antonov
Sergey Antonov created IGNITE-13004:
---
Summary: Fix wrong comparison in
TcpCommunicationSpi#closeConnections(UUID)
Key: IGNITE-13004
URL: https://issues.apache.org/jira/browse/IGNITE-13004
Project
he following:
> >
> >
> > * store binary meta and marshaller data inside db/ folder
> > * if binary meta of marshaller are found in "legacy" locations --
> > safely move them to new locations during the node startup
> >
> >
> > Kind regards,
> >
> > Semyon Danilov.
> >
>
--
BR, Sergey Antonov
Sergey Antonov created IGNITE-12985:
---
Summary: Fix unguarded log.info/log.debug/log.trace usages
Key: IGNITE-12985
URL: https://issues.apache.org/jira/browse/IGNITE-12985
Project: Ignite
Hi, the ticket is ready for review.
[1] https://github.com/apache/ignite/pull/7728
вт, 28 апр. 2020 г. в 14:39, Sergey Antonov :
> Maxim, I'm talking about cluster upgrade through cluster stop -> binary
> update -> cluster start.
>
> вт, 28 апр. 2020 г. в 14:37, Maxim Muzaf
Maxim, I'm talking about cluster upgrade through cluster stop -> binary
update -> cluster start.
вт, 28 апр. 2020 г. в 14:37, Maxim Muzafarov :
> Sergey,
>
> Are you talking about a cluster rolling upgrade feature? AFAIK, Apache
> Ignite doesn't support this feature, so why we
ted. It can lead to a difference in inline sizes
without IGNITE_MAX_INDEX_PAYLOAD_SIZE option.
вт, 28 апр. 2020 г. в 14:22, Maxim Muzafarov :
> Sergey, Ilya,
>
>
> Since inline size for the `create table` clause not supported yet and
> the IGNITE_MAX_INDEX_PAYLOAD_SIZE is the on
,
> --
> Ilya Kasnacheev
>
>
> вт, 28 апр. 2020 г. в 02:31, Denis Magda :
>
> > Hi Sergey,
> >
> > Your changes look useful from the application developer perspective.
> > However, I'm curious why would the one change some low-level
> > IGNITE_MAX_INDEX_PA
Hi Denis,
The problem could be shown when you invoke CREATE INDEX without the
INLINE_SIZE parameter. You don't face with described problem If index
creates by CREATE_INDEX with explicit INLINE SIZE value.
вт, 28 апр. 2020 г. в 02:31, Denis Magda :
> Hi Sergey,
>
> Your changes look us
Sergey Antonov created IGNITE-12955:
---
Summary: Document a new command control.sh --cache
check_index_inline_sizes
Key: IGNITE-12955
URL: https://issues.apache.org/jira/browse/IGNITE-12955
Project
#IGNITE_MAX_INDEX_PAYLOAD_SIZE
--
BR, Sergey Antonov
Sergey Antonov created IGNITE-12942:
---
Summary: control.sh add command for checking that inline size is
same on all cluster nodes
Key: IGNITE-12942
URL: https://issues.apache.org/jira/browse/IGNITE-12942
DYT?
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Naming
> [2]
> https://web.archive.org/web/20120911192801/developers.sun.com/sunstudio/products/archive/whitepapers/java-style.pdf
> [3] https://github.com/apache/ignite/pull
Sergey Chugunov created IGNITE-12878:
Summary: Improve logging for async writing of Binary Metadata
Key: IGNITE-12878
URL: https://issues.apache.org/jira/browse/IGNITE-12878
Project: Ignite
Sergey Chugunov created IGNITE-12876:
Summary: Test to cover deadlock fix between checkpoint, entry
update and ttl-cleanup threads
Key: IGNITE-12876
URL: https://issues.apache.org/jira/browse/IGNITE-12876
Hi,
I'm proposing to add
https://issues.apache.org/jira/browse/IGNITE-12549 (fix iterators/scan
queries for replicated caches)
to 2.8.1.
Best regards,
Sergey Kosarev.
вс, 5 апр. 2020 г. в 01:22, Saikat Maitra :
> Hi,
>
> I observed that we already have release 2.8.1 branc
Hi,
Here is reproducer for master :
https://github.com/macrergate/ignite/commit/9a7d2d27af30018a5f6faccb39176a35243ccfa2
Best regards,
Sergey Kosarev.
вт, 17 мар. 2020 г. в 12:27, Sergey-A Kosarev :
> Classification: Public
>
> Hi Sergey,
> Ticket is here https://issues.apa
, in my experience there are more
objects that not null by nature than nullable. So if you should mark only all
@NotNull objects, you will need to place much more annotations than if mark
only @Nullable objects.
Kind regards,
Sergey Kosarev
-Original Message-
From: Ivan Pavlukhin
and to add such check to checkstyle
> > plugin too?
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-@Annotations
> >
>
--
BR, Sergey Antonov
=1544803905, grpName=default,
> >> > partId=7]
> >> > Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> >> > consistentId=gridCommandHandlerTest2, updateCntr=3,
> >> partitionState=MOVING,
> >> > state=MOVING]] .. and so on
> >> >
> >> > I found this erroneous and can lead to further cluster index
> corruption,
> >> > for example in case when only command OK result checked.
> >> >
> >> > If no objections would be here, i plan to inform about moving states
> as
> >> > not OK exit code too.
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Vladislav Pyatkov
> >> Architect-Consultant "GridGain Rus" Llc.
> >> +7-929-537-79-60
> >>
>
>
>
>
--
BR, Sergey Antonov
difference on node join.
> > IGNITE-12551 Partition desync if a partition is evicted then owned again
> > and historically rebalanced
> > IGNITE-12536 Inconsistency between cache data and indexes when cache
> > operation is interrupted
> > IGNITE-12403 Throttle page difference output in PageMemoryTracker
> > IGNITE-12523 Continuously generated thread dumps in failure processor
> slow
> > down the whole system
> > IGNITE-12489 Error during purges by expiration: Unknown page type
>
--
BR, Sergey Antonov
Sergey Antonov created IGNITE-12803:
---
Summary: Investigate exception message on too many open files in
different OS.
Key: IGNITE-12803
URL: https://issues.apache.org/jira/browse/IGNITE-12803
Hi igniters!
I ask to review PR for issue
https://issues.apache.org/jira/browse/IGNITE-12799 . My PR is approved by
TeamCity and ready for merge.
--
-
With best regards, Sergey Chernolyas
Sergey Chernolyas created IGNITE-12799:
--
Summary: Set right SpEL at test
Key: IGNITE-12799
URL: https://issues.apache.org/jira/browse/IGNITE-12799
Project: Ignite
Issue Type: Bug
Classification: Public
Hi Sergey,
Ticket is here https://issues.apache.org/jira/browse/IGNITE-12793
I will try to make reproducer in the coming days.
Kind regards,
Sergey Kosarev
-Original Message-
From: Sergey Chugunov [mailto:sergey.chugu...@gmail.com]
Sent: 17 March 2020 09:45
Sergey Kosarev created IGNITE-12793:
---
Summary: Deadlock in the System Pool on Metadata processing
Key: IGNITE-12793
URL: https://issues.apache.org/jira/browse/IGNITE-12793
Project: Ignite
Hello Sergey,
Your analysis looks valid to me, we definitely need to investigate this
deadlock and find out how to fix it.
Could you create a ticket and write a test that reproduces the issue with
sufficient probability?
Thanks!
On Mon, Mar 16, 2020 at 8:22 PM Sergey-A Kosarev
wrote
voked from the same client node, or is
there some golden rule to follow - something like not than (capacity of the
system pool - 1) concurrent jobs from the same node should be invoked?
Kind regards,
Sergey Kosarev
---
This e-mail may contain confidential and/or privileged informati
> >
> > I propose the following dates for 2.8.1 release:
> > Scope Freeze: April 15, 2020
> > Code Freeze: April 22, 2020
> > Voting Date: April 27, 2020
> > Release Date: May 1, 2020
> >
> >
> > Please, share your thoughts.
> >
> >
> > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1
> > [2] https://github.com/apache/ignite/tree/ignite-2.8.1
> >
>
--
-
With best regards, Sergey Chernolyas
Sergey Antonov created IGNITE-12774:
---
Summary: Transaction hungs after too many open files NIO exception
Key: IGNITE-12774
URL: https://issues.apache.org/jira/browse/IGNITE-12774
Project: Ignite
Classification: Public
There are no RC anymore, I believe. It's now just 2.8.0 (as in Maven Central)
Thank you to all involved in the release guys, especially Maxim!
Kind regards,
Sergey Kosarev
-Original Message-
From: Ivan Pavlukhin [mailto:vololo...@gmail.com]
Sent: 05 March 2020 12
0.
Still can't get access to teamcity links.
пн, 2 мар. 2020 г., 17:24 Alexey Zinoviev :
> +1 (binding)
> I've downloaded the binary archive, run it, checked the ML examples and
> JavaDocs.
>
>
>
> вс, 1 мар. 2020 г. в 13:49, Ivan Pavlukhin :
>
> > +1 (binding)
> >
> > Downloaded binary
/viewLog.html?buildId=5085460=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages=buildResultsDiv
[3]
https://ci.ignite.apache.org/viewLog.html?buildId=5085458=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=buildResultsDiv
пт, 28 февр. 2020 г. в 16:41, Maxim Muzafarov :
> Ser
Ivan,
I also don't think this issue is a blocker for 2.8 as it affects only
experimental functionality and only in special cases.
Removing key length limitations in MetaStorage seems more strategic
approach to me but depending on how we decide to approach it (as a local
fix or as part of a
Guys, can somebody check those links from TC account different from @
apache.org domain?
пт, 28 февр. 2020 г. в 11:58, Pavel Tupitsyn :
> Sergey, can't confirm, those links work for me
>
> On Thu, Feb 27, 2020 at 11:17 PM Sergey Antonov >
> wrote:
>
> > Hello, Maxim
=buildResultsDiv
Kind regards,
Sergey Kosarev
-Original Message-
From: Pavel Tupitsyn [mailto:ptupit...@apache.org]
Sent: 28 February 2020 11:58
To: dev
Subject: Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
Sergey, can't confirm, those links work for me
On Thu, Feb 27, 2020 at 11
> >> >> > > > > Igniters,
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > I've prepared the issue [1] and PR [2] with removing
> @deprecate
> > >> >> > > > > annotation on DataRegionMetrics and adding
> @IgniteExperimental
> > >> to the
> > >> >> > > > > new metrics API.
> > >> >> > > > > Can anyone review my changes?
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> > >> >> > > > > [2] https://github.com/apache/ignite/pull/7440
> > >> >> > > > >
> > >> >> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <
> > >> ilya.kasnach...@gmail.com>
> > >> >> > > > wrote:
> > >> >> > > > > >
> > >> >> > > > > > Hello!
> > >> >> > > > > >
> > >> >> > > > > > I have just merged a fix for embarrassing issue where you
> > >> could UPDATE
> > >> >> > > > > > entries with Spring Data, but not "Update" or "update"
> them.
> > >> >> > > > > >
> > >> >> > > > > > I suggest adding this fix to the scope of 2.8, since
> Spring
> > >> Data is
> > >> >> > > > popular
> > >> >> > > > > > and it does not in any way affect code outside of its
> > >> modules.
> > >> >> > > > > >
> > >> >> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
> > >> >> > > > > >
> > >> >> > > > > > WDYT?
> > >> >> > > > > >
> > >> >> > > > > > Regards,
> > >> >> > > > > > --
> > >> >> > > > > > Ilya Kasnacheev
> > >> >> > > > > >
> > >> >> > > > > >
> > >> >> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <
> > >> mmu...@apache.org>:
> > >> >> > > > > >
> > >> >> > > > > > > Alexey,
> > >> >> > > > > > >
> > >> >> > > > > > >
> > >> >> > > > > > > Yes. I will remove @deprecation according to the vote
> > >> results and
> > >> >> > > > will
> > >> >> > > > > > > go further with the release steps [1] since there no
> > >> blockers left.
> > >> >> > > > > > >
> > >> >> > > > > > >
> > >> >> > > > > > > [1]
> > >> >> > > >
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >> >> > > > > > >
> > >> >> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > >> >> > > > > > > wrote:
> > >> >> > > > > > > >
> > >> >> > > > > > > > Folks,
> > >> >> > > > > > > >
> > >> >> > > > > > > > I have merged IGNITE-12650 (mark MVCC as
> experimental)
> > >> to master
> > >> >> > > > and
> > >> >> > > > > > > > ignite-2.8. What's left? Should we remove deprecation
> > >> from the old
> > >> >> > > > > > > metrics
> > >> >> > > > > > > > and start the vote?
> > >> >> > > > > > >
> > >> >> > > >
> > >>
> > >
>
--
BR, Sergey Antonov
Sergey Chugunov created IGNITE-12721:
Summary: Validation of key length written to Distributed
Metastorage
Key: IGNITE-12721
URL: https://issues.apache.org/jira/browse/IGNITE-12721
Project
Sergey Antonov created IGNITE-12710:
---
Summary: Extension log in rebuild indexes to search problems
Key: IGNITE-12710
URL: https://issues.apache.org/jira/browse/IGNITE-12710
Project: Ignite
-1 Prohibit.
To me as a developer the situation when old but stable API is deprecated
with only experimental (thus unstable/unfinished) alternative is very far
from comfortable.
And from outside folks it may look like as a sign of immature processes
inside Ignite community (which is definitely
Classification: Public
Alexey,
then I don't have objections.
-Original Message-
From: Alexei Scherbakov [mailto:alexey.scherbak...@gmail.com]
Sent: 12 February 2020 12:01
To: dev
Subject: Re: [DISCUSSION] Deprecation of obsolete rebalancing functionality
Sergey,
The ticket looks
Classification: Public
Hi, Alexey.
I believe it can't be done until in-memory caches will use baseline topology
[1].
In our case we are using rebalanceDelay for in-memory caches.
[1] https://issues.apache.org/jira/browse/IGNITE-8414
Kind regards,
Sergey Kosarev
-Original Message
ache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/lang/IgniteExperimental.java
> > [2]
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Public-API-deprecation-rules-td45647.html
> >
> > Thanks,
> > --AG
>
>
>
> --
> Best Regards, Vyacheslav D.
>
--
BR, Sergey Antonov
Sergey Chugunov created IGNITE-12646:
Summary: When DEBUG mode is enabled GridToStringBuilder may throw
java.util.ConcurrentModificationException
Key: IGNITE-12646
URL: https://issues.apache.org/jira/browse
Sergey Chernolyas created IGNITE-12643:
--
Summary: It is needed to set used cache for Spring Data dynamically
Key: IGNITE-12643
URL: https://issues.apache.org/jira/browse/IGNITE-12643
Project
of code.
--
-
With best regards, Sergey Chernolyas
Ivan,
Thanks. I have answered.
On Tue, 4 Feb 2020 at 15:03, Ivan Pavlukhin wrote:
> Sergey,
>
> Thank you for your efforts! I left some comments in the ticket [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12582
>
> сб, 1 февр. 2020 г. в 18:35, Sergey Chernoly
cycle to
extension project.
May we do it? When (which release for?) and how?
-
With best regards, Sergey Chernolyas
Hi Ivan!
https://github.com/apache/ignite/pull/7347 . It is link to PR. Criticism
is welcome :-)
On Sat, 1 Feb 2020 at 18:15, Ivan Pavlukhin wrote:
> Sergey,
>
> Could you please share your prototype, I would like to have a look.
>
> сб, 1 февр. 2020 г. в 16:59, schernolyas :
options:
1) field "cacheName" will be able to process expression and constant
string. The code of repository factory will analyse the field.
2) create new field for expressions
What is best way?
--
-----
With best regards, Sergey Chernolyas
. The code will analyse type of content (clear
string or expression)
2) at new field.
I mean annotation
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/springdata20/repository/config/RepositoryConfig.html
--
-
With best regards, Sergey Chernolyas
, property "
*spring.data.mongodb.uri*" from spring data repository for mongodb
On Wed, 29 Jan 2020 at 15:16, Sergey Chernolyas
wrote:
> Hi!
>
> It is seemed what I need.
>
> On Wed, 29 Jan 2020 at 15:14, Nikolay Izhikov wrote:
>
>> Hello, Sergey.
>>
>
Hi!
It is seemed what I need.
On Wed, 29 Jan 2020 at 15:14, Nikolay Izhikov wrote:
> Hello, Sergey.
>
> What is «repository»? How it relates to the Ignite?
>
> ignite-spring-boot-autoconfigure confirms your requirements?
>
>
> https://github.com/apache/ignite-extens
wrote:
> Hello, Sergey.
>
> Your proposal is not clear for me
> Can you, please, describe the issue you are trying to solve?
> And the way you want to do it.
>
>
> > 29 янв. 2020 г., в 14:53, Sergey Chernolyas
> написал(а):
> >
> > Hi!
> > It is
Person (id int, city_id int, name
varchar, age int, company varchar, PRIMARY KEY (id, city_id))
Other ideas ?
--
-
With best regards, Sergey Chernolyas
Do you mean channel at Telegram ?
On Wed, 29 Jan 2020 at 11:20, Maksim Stepachev
wrote:
> Okey, but our channel has 90+ active members.
>
> ср, 29 янв. 2020 г. в 11:15, Sergey Chernolyas <
> sergey.chernol...@gmail.com
> >:
>
> > Hi Maksim!
> >
> >
gt; days ago Nikolay Izhikov finished the new spring boot starter.
> https://github.com/apache/ignite-extensions/tree/master/modules
>
> You may add the spring data module.
>
>
> ср, 29 янв. 2020 г. в 10:46, Sergey Chernolyas <
> sergey.chernol...@gmail.com
> >:
>
>
Hi Maksim!
The link is unavailable :-( I can't open it. I think Slack is more
preferable.
On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev
wrote:
> Hi,
>
> Could we use the telegram channel for it for the Russian community?
>
> https://t.me/RU_Ignite
>
> ср, 29 янв. 20
Hi igniters!
I have created new channel "#ignite-spring-framework" for discussion about
integration with Spring Framework.
--
-
With best regards, Sergey Chernolyas
My jiraId is schernolyas
--
-
With best regards, Sergey Chernolyas
--
-
With best regards, Sergey Chernolyas
Denis, Emmanouil,
Sure, I'll take a look at the code shortly.
--
Thank you,
Sergey.
On Mon, Jan 27, 2020 at 8:59 PM Denis Magda wrote:
> I support the idea of triggering such tests on demand. We can create a wiki
> page with instructions on how to run the tests. Unless there is
Sergey Chernolyas created IGNITE-12582:
--
Summary: It is needed to set used cache for Spring Data by
property
Key: IGNITE-12582
URL: https://issues.apache.org/jira/browse/IGNITE-12582
Project
?
--
Thank you,
Sergey Chugunov.
On Thu, Jan 23, 2020 at 5:32 PM Emmanouil Gkatziouras
wrote:
> Hi all!
>
> Yes It seems possible to get some free quota for integration tests on AWS
> [1] however most probably they are not gonna last forever.
>
> [1]
>
> https://aws.amazon.
Hello community,
Recently I published a new blog post on getting started with Apache Ignite
in AWS [1]. I tried to make my example as simple as possible while keeping
it usable.
Let me know if this post is useful for you.
I plan to write several follow-up posts about AWS-specific things but
Maxim,
Conflicts in pr [1] are resolved. TC Run all is started.
[1] https://github.com/apache/ignite/pull/7238
пт, 17 янв. 2020 г. в 16:04, Sergey Antonov :
> Maxim,
>
> I will do that on monday (20/01).
>
> пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov :
>
>> Sergey,
Maxim,
I will do that on monday (20/01).
пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov :
> Sergey,
>
>
> Can you, please, resolve the PR conflicts [1] [2]?
>
> [1] https://github.com/apache/ignite/pull/7238
> [2] https://issues.apache.org/jira/browse/IGNITE-11256
>
> O
queries on REPLICATED caches during rebalance
Hi Sergey,
Just FYI: a similar problem with replicated caches has been fixed in SQL [1].
If you have a reproducer, you may check whether your issue is still actual.
[1]: https://issues.apache.org/jira/browse/IGNITE-12482
On Thu, Jan 16, 2020 at 1:51 PM
.
And as workaround I think PARTITIONED caches with Integer.MAX_VALUE backups can
be used instead of REPLICATED caches.
Will be glad for any feedback.
Kind regards,
Sergey Kosarev
---
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have
Sergey Kosarev created IGNITE-12549:
---
Summary: Scan query/iterator on a replicated cache may get wrong
results
Key: IGNITE-12549
URL: https://issues.apache.org/jira/browse/IGNITE-12549
Project
=pull%2F7239%2Fhead=Latest
пн, 13 янв. 2020 г., 17:51 Maxim Muzafarov :
> Sergey,
>
> Thank you. I also do not support @IgniteExperemental annotation only
> for solving the current case of compatibility issues.
>
> I like your second suggestion to revert the issue [2] from 2.8 rel
gt;> >
> >> > >Hello, Igniters.
> >> > >
> >> > >I’m -1 to include the read-only patch to 2.8.
> >> > >I think we shouldn’t accept any patches to 2.8 except bug fixes for
> >> > blockers and major issues.
> >&
nd protocol and in the
> > same
> > > > > Ignite version deprecate these methods for servers and thick
> clients.
> > > > >
> > > > > [1]: https://issues.apache.org/jira/browse/IGNITE-11709
> > > > > [2]: https://issues.apache.org/jira/brows
> [3]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolvedissues(notrelatedtodocumentation)
>
> On Thu, 9 Jan 2020 at 19:01, Alexey Zinoviev
> wrote:
> >
> > +1
> >
> > чт, 9 янв. 2020 г. в 18:52, Sergey Antonov :
> &g
+1
I'm preparing patch for 2.8 branch now. TC Bot visa for 2.8 branch will be
at 13 Jan
чт, 9 янв. 2020 г., 21:06 Ivan Pavlukhin :
> +1
>
> чт, 9 янв. 2020 г. в 16:38, Ivan Rakov :
> >
> > Maxim M. and anyone who is interested,
> >
> > I suggest to include this fix to 2.8 release:
> >
Igniters, I prepared PR with fix [1].
Can someone merge it?
[1] https://github.com/apache/ignite/pull/7224/files
сб, 4 янв. 2020 г. в 12:08, Sergey Antonov :
> Hi!
>
> I'll fix failures under ticket [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12520
>
> чт, 2
w+to+Contribute
> - Should you have any questions please contact
> dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 15:01:08 02-01-2020
>
--
BR, Sergey Antonov
Sergey Antonov created IGNITE-12520:
---
Summary: Wrong year in copyright in correct output of control
utility.
Key: IGNITE-12520
URL: https://issues.apache.org/jira/browse/IGNITE-12520
Project
101 - 200 of 1083 matches
Mail list logo
