;
> Why don't you use Ignite persistence [1]?
>
> [1] https://apacheignite.readme.io/docs/distributed-persistent-store
>
> -Val
>
> On Fri, Nov 17, 2017 at 4:24 AM, Vyacheslav Daradur
> wrote:
>
>> Hi Andrey! Thank you for answering.
>>
>> >> Key
e one instance of RocksDB (or any other DB
> for that matter) that is accessed via network by all nodes, then it's also
> an option. But in this case storage is not distributed.
>
> -Val
>
> On Tue, Nov 21, 2017 at 4:37 AM, Vyacheslav Daradur
> wrote:
>
>> Vale
Hello everyone.
I want to help community with development of Apache Ignite.
I was wondering if you could give me some advice.
With best regards,
Vyacheslav Daradur
- etc.
Maybe it'll be better to use some metrics from ClusterMetrics interface.
The algorithm of ordering can be implemented in a class such as Comparator
and use it when we build a cluster or we select a place for a new node.
--
With best regards,
Vyacheslav Daradur
2016-12-22 13:59 GMT+
ome user-defined ordering can be beneficial. However, we
> are only talking about node discovery protocol here to maintain the
> cluster. All other communication between nodes happens directly (does not
> go through the ring).
>
> D.
>
> On Thu, Dec 22, 2016 at 6:32 AM, Vya
>>
Vyacheslav, please elaborate on how we can determine whether we are on the
same rack. I am not sure this is possible in general case. Please see my
suggestions below.
>>
I thought of latency values.
Latency between host nodes < Latency between same rack nodes < Latency
between subnet nodes < e
Hello everyone.
I want to pick up https://issues.apache.org/jira/browse/IGNITE-4464 as my
first issue.
Please add me as contributor.
ontributor's list.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4248
>
> Vladimir.
>
> On Mon, Dec 26, 2016 at 12:45 PM, Vyacheslav Daradur
> wrote:
>
> > Hello everyone.
> >
> > I want to pick up https://issues.apache.org/jira/browse/IGNITE-4464 as
> my
> > first issue.
> >
> > Please add me as contributor.
>
>>
Vyacheslav, I agree that latency increase in the way you describe, but I
still don't understand how we use this information in discovery. Latency
may differ from time to time depending on many factors. I still think that
arc approach is more intuitive for user and easier to implement.
>>
Way of
I picked up https://issues.apache.org/jira/browse/IGNITE-4374
I have some questions:
1. It is necessary to check a flag MaxDirectMemorySize, but there is no
recommendation of it:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
2. Whether it is necessary to output message in "Quiet mode
>>
3. I think this should be a new section in performance suggestion output.
And I think the GridPerformanceSuggestions should be used, but it should be
probably renamed to reflect its new role and remove Grid prefix also. How
about ConfigurationSuggestions?
>>
How about:
public class Configuratio
I mean ConfigurationValidator as another class, not
GridPerformanceSuggestion.
And invoke it from IgniteKernal.
2016-12-27 14:46 GMT+03:00 Vyacheslav Daradur :
> >>
> 3. I think this should be a new section in performance suggestion output.
> And I think the GridPerformanceSugges
I have described a task: https://issues.apache.org/jira/browse/IGNITE-4501
and linked a bug https://issues.apache.org/jira/browse/IGNITE-4499
Alex Menshikov, maybe you will take her?
2016-12-27 13:32 GMT+03:00 Alexei Scherbakov :
> 2016-12-27 10:42 GMT+03:00 Yakov Zhdanov :
>
> > >>
> > My mai
Yakov, I have looked at source codes and I agree with you.
Let's rename GridPerformanceSuggestions to ConfigurationSuggestions
and to add new checks to suggestOptimizations method in IgniteKernal or
separate method.
2016-12-27 14:51 GMT+03:00 Vyacheslav Daradur :
> I mean ConfigurationV
Hi, Igniters!
After the completion of publishing abbr-plugin [1][2] we will be able
to automate checking of method arguments code style.
It will be easy to check rules approved by the community during writing code.
[1] https://issues.apache.org/jira/browse/IGNITE-5698
[2]
http://apache-ignite-d
ation
> in the discovery thread.
> Making it asynchronous will be our next step: IGNITE-8362
> <https://issues.apache.org/jira/browse/IGNITE-8362>
>
> Denis
>
> вт, 24 апр. 2018 г. в 15:43, Vyacheslav Daradur :
>
>> Hi, Denis M.,
>>
>> I'd like to
Hi, Igniters!
I’ve made tests coverage report of core module using Jacoco 0.8.1
I’d like to share results with the community. Here is a link:
https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-tests-coverage-report-rev-d83f1ec.zip?dl=0
For viewing the report unpack the archive and
re-module-tests-coverage-report-rev-d83f1ec.zip?dl=0&file_subpath=%2Fcoverage-report%2Findex.html
>
> says error 400 for me.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 14 мая 2018 г. в 17:06, Vyacheslav Daradur :
>
>> Hi, Igniters!
>>
>> I’ve made tests cove
hould download the archive first.
>
> I've found for example that method truncate in FSyncWalManager is not
> covered.
>
> Which test suites were executed?
>
> пн, 14 мая 2018 г. в 17:16, Vyacheslav Daradur :
>
>> Hi, Dmitry,
>>
>> Download and unpack
urce.
>> > > >
>> > > > So please proceed with distributive build.
>> > > >
>> > > > Best Regards,
>> > > > Dmitriy Palvov
>> > > >
>> > > >
>> > > > On Mon, May 1
+1 to Andrey's point.
Do we really have any problems with comment's deletion?
I think: if a contributor will make a decision to remove a comment and
will not be able to do this he just will edit the comment with the
message *deleted*.
On Wed, May 16, 2018 at 2:46 PM, Andrey Kuznetsov wrote:
>
o add method
> code style check.
>
> Actually I'm not sure it is easy to validate code style in plugin, but I
> guess you know it better.
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 8 мая 2018 г. в 21:47, Vyacheslav Daradur :
>
>> Hi, Igniters!
>>
>&g
ay 8, 2018 at 9:50 PM, Vyacheslav Daradur wrote:
> Thanks, Denis! I assigned the task to myself.
>
> I going to start work next week.
>
> On Tue, May 8, 2018 at 7:50 PM, Denis Mekhanikov
> wrote:
>> Hi Vyacheslav!
>>
>> Thanks for the enthusiasm!
>> The
Hi, there is such GitHub profile:
https://github.com/apacheignite
But I don't know who manage that.
On Thu, May 17, 2018 at 9:22 PM, Aleksandr Sokolovskii
wrote:
> Hi Igor,
>
> Of course I am ready to donate code.
>
> You have to know that GitHub is source code repo and package repo for build
>
Hi, Andrey, I have faced this problem too.
I'd suggest introducing new logger for tests instead of extending API
of *GridStringLogger*.
The new logger should be some kind of *listened*, for example with the
folowing API:
void addListener(String pattern, CountDownLatch latch);
void addListener(Ig
Hi, Alex!
Please have a look at maven profile named "jcache-tck".
I believe this is what you are looking for.
On Wed, May 23, 2018 at 11:50 AM, Александр Меньшиков
wrote:
> Igniters,
> I think I can do it. As I see we already have JCache TCK tests in TC.
> Can I take somewhere settings/script w
+1 for GoToMeeting webinar.
On Thu, May 24, 2018 at 2:09 PM, Dmitriy Govorukhin
wrote:
> +1 for a webinar, I would like to see it.
>
> On Wed, May 23, 2018 at 5:34 PM, Dmitry Pavlov
> wrote:
>
>> Hi Ivan,
>>
>> Would you like to run presentation based on this slides for Igniters?
>>
>> We can se
+1
Checked build from sources and run several examples.
On Fri, May 25, 2018 at 10:04 PM, Eduard Shangareev
wrote:
> +1
>
> On Fri, May 25, 2018 at 6:41 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> On Fri, May 25, 2018 at 8:05 AM, Dmitry Pavlov
>> wr
You can test new profile locally with the following command:
>>>>>
>>>>> mvn test -P-release,jcache-tck-1.1 -pl :ignite-core -am
>>>>>
>>>>>
>>>>> After that, I will start to add sub-task for every problem w
profile.
> Why we need to merge it in master now?
>
> В Вт, 05/06/2018 в 13:29 +0300, Vyacheslav Daradur пишет:
>> Nikolay, there isn't anything broken in PR.
>>
>> The PR is needed to add new build-plan on TC.
>>
>> We need tools to check that fixes for 1
Hello, Igniters!
I am not familiar with the Ignite's thin client.
I'd suggest defining tests scenarios first, to understand what we need
for testing.
For example, our Compatibility Framework may be used for the following scenario:
1. Start node of a previously released version in separate JVM an
Hi Igniters, sorry for the delay in replying.
I going to finish the task [1] to the end of this month.
[1] https://issues.apache.org/jira/browse/IGNITE-8361
On Wed, May 16, 2018 at 10:57 PM, Vyacheslav Daradur
wrote:
> Hi, Igniters!
>
> I had a discussion about the scope of work of IE
> the community side (articles, webinars, meetups).
>
> Plus, do you think you'll be able to complete the whole IEP by the end of
> the year? Is someone else going to help you with this initiative? That
> would be a huge New Year gift to Ignite community.
>
> --
> Denis
>
ser wants to update the code? Is
> this planned?
>
> D.
>
> On Tue, Jun 19, 2018 at 12:10 AM, Vyacheslav Daradur
> wrote:
>
> > Hi Denis!
> >
> > >> If to assume that Ignite 2.7 gets released in September, what else
> > would you be able to complete
Hi,
I've commented your PR on the GitHub.
On Mon, Jul 9, 2018 at 5:21 AM kcheng.mvp wrote:
>
> Dear igniters,
>
> does anyone can help do the code review?
>
> As this ticket is created by myself, I need someone else to help me do the
> code review.
>
>
> Thanks,
> kcmvp
>
>
>
> --
> Sent from:
Now changes look good to me.
Dmitry, could you help with a final review and merge, please?
On Mon, Jul 9, 2018 at 9:30 AM Vyacheslav Daradur wrote:
>
> Hi,
>
> I've commented your PR on the GitHub.
>
>
> On Mon, Jul 9, 2018 at 5:21 AM kcheng.mvp wrote:
> >
> &
+1
Checked build from sources and run several examples.
On Wed, Jul 11, 2018 at 7:55 PM Dmitry Pavlov wrote:
>
> +1, checked RC ver. 2.6.0#20180710-sha1:669feacc as new DB for Ignite TC
> helper (MTCGA.Bot). Data was sucessfully restored from 2.5, tool is
> operational.
>
> I suggest to publis
I vote for a separate repo for the TC helper project.
IMO TC Helper - is an application project and a separate repo is a
more convenient way to the project developing.
One more place where we could place the project (if the place
maintained by Ignite's commiters):
https://github.com/apacheignite
I vote for a separate repo for the Ignite Abbrev Plugin project.
The reason is:
Ignite Abbrev Plugin - build on top of IntelliJ Platform SDK [1] and
can't be easily packaged without it, moreover, it doesn't depend on
Ignite internals (unlike .NET/C++ clients).
One more place where we could place
gt; > > > > > > https://issues.apache.org/jira/browse/IGNITE-8714
> > > > > > > > >
> > > > > > > > > 6) Problems with Closeable objects from Factory
> > > > > > > > >
> > > > > > > > > *98* tests fail because of it.
> > > > &
Hi, Igniters!
The end of September for Ignite 2.7 release sounds good to me.
I'm working on Service Grid and going to deliver the following tasks:
- Use discovery messages for service deployment [[1]
- Collect service deployment results asynchronously on coordinator [2]
- Propagate service deploy
d, Jun 20, 2018 at 1:46 AM Dmitriy Setrakyan wrote:
>
> On Tue, Jun 19, 2018 at 1:50 PM, Vyacheslav Daradur
> wrote:
>
> > Hi Dmitriy,
> >
> > Yes, the task [1] is planned to be implemented once the main tasks
> > will be completed.
> >
> > [1] https:
y know, when it may be useful?
>
> Vyacheslav, does it complicate the implementation somehow?
>
> Denis
>
> вт, 24 июл. 2018 г. в 11:57, Vyacheslav Daradur :
>
> > Hi, Igniters!
> >
> > I am close to completing the main tasks and I'm going to request a
>
Welcome to the community, Nikolai!
Dmitry, could you help with contributor permissions in Jira?
On Tue, Jul 24, 2018 at 12:44 PM Nikolai Kulagin
wrote:
>
> I'm new to Ignite and I would like to join apache ignite development.
>
> My JIRA's login is zzzadruga.
>
> Going to start from IGNITE-9044
Hi, one of a possible cause:
https://issues.apache.org/jira/browse/IGNITE-8892 Iterating over large
dataset via ScanQuery can fails with OOME.
Related PR tests:
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures&branch=%3Cdefault%3E&tab=buildTypeStatusDiv&bran
; > But I think, it's worth mentioning as a warning in log, that a service is
> > deployed on a client node.
> >
> > Denis
> >
> > вт, 24 июл. 2018 г. в 12:44, Vyacheslav Daradur :
> >
> > > No, it's doesn't complicate imple
-3392
On Tue, Jul 24, 2018 at 3:01 PM Vyacheslav Daradur wrote:
>
> Got it.
>
> Yes, we will preserve this behavior.
>
> Thanks!
> On Tue, Jul 24, 2018 at 2:20 PM Dmitriy Setrakyan
> wrote:
> >
> > By default the client nodes should be excluded form service dep
en done to a release.
On Wed, Jul 25, 2018 at 12:08 PM Dmitriy Setrakyan
wrote:
>
> On Tue, Jul 24, 2018 at 9:14 PM, Vyacheslav Daradur
> wrote:
>
> > Igniters, please help me to clarify the following questions:
> >
> > 1). According to the issue [1] we should propag
FYI, I've filled the tickets:
https://issues.apache.org/jira/browse/IGNITE-9075
https://issues.apache.org/jira/browse/IGNITE-9076
On Wed, Jul 25, 2018 at 12:54 PM Vyacheslav Daradur wrote:
>
> > I think such timeout should be determined on per-service level. Can we make
> > it
ndatory, and it should be
> disabled by default.
> We should be ready for long service initialization. So, it shouldn't be
> done in any crucial threads like discovery or exchange.
>
> Denis
>
> ср, 25 июл. 2018 г. в 15:59, Vyacheslav Daradur :
>
> > FYI, I've
Hi, Maxim,
There is information about project components maintainers [1], but I'm
not sure if it is actual.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers
On Wed, Aug 1, 2018 at 9:33 AM Maxim Muzafarov wrote:
>
> Folks,
>
> I
uarantee availability in case of blinking
> > > > clients.
> > > >
> > > > Also, taking into account that ignite cluster can have more that one
> > user
> > > > it looks odd that one user able to start service at another user's
> > >
9, 2018 at 4:41 AM, Vyacheslav Daradur
> wrote:
>
> > Hi, Igniters!
> >
> > I found a ticket about a service’s versioning [1].
> >
> > It’s out of scope IEP-17, but if we are going to implement this
> > feature we should build a base in the first
name to it.
>
> What do you think?
>
> Denis
>
> чт, 9 авг. 2018 г. в 16:32, Dmitriy Setrakyan :
>
> > On Thu, Aug 9, 2018 at 4:41 AM, Vyacheslav Daradur
> > wrote:
> >
> > > Hi, Igniters!
> > >
> > > I found a ticket about a service’
nt, which should have
> been a part of the current IEP, no? Can you please clarify?
>
> D.
>
> On Thu, Aug 9, 2018 at 9:26 AM, Denis Mekhanikov
> wrote:
>
> > Vyacheslav,
> >
> > It looks like an overcomplication to me.
> > Could you describe a case, t
Huge +1, for a public benchmarking tool and the Docker based approach.
On Thu, Aug 9, 2018 at 7:16 PM Pavel Kovalenko wrote:
>
> Igniters,
>
> I would like to add that it would be very nice to have prepared scenarios
> in packed docker images with docker-compose, to easily deploy and run it on
> A
Hi,
Try to add "-pds" flag in input arguments for Ignite benchmarks to
enable persistence.
On Sat, Aug 11, 2018 at 12:19 AM Mammo, Mulugeta
wrote:
>
> Hi,
>
> I was testing out the Yardstick benchmark in my local machine and it looks to
> me that there is no direct way to run the benchmarks with
Hi, Nick!
ASAIK java.sql.Array hasn't been implemented in binary infrastructure yet.
You should implement it first, like in
https://issues.apache.org/jira/browse/IGNITE-4158
On Mon, Aug 13, 2018 at 5:22 PM Sergey Kozlov wrote:
>
> Hi Nikolay
>
> I was not able to use array type in sqlline [1] i
Hi, Alex, please have a look, it may be interesting for you.
AFAIK, extending of interface *ICompute* with a new method
*WithNoResultCache* should be enough to fix the *ApiParity* test. It
may require changes in XSD scheme.
But it would be great if you'll find time to fully implement a new method
I think that the replacement of serialized instance makes sense to me
for Java part.
But how it should work for .NET client?
On Tue, Aug 14, 2018 at 4:07 PM Dmitriy Setrakyan wrote:
>
> On Tue, Aug 14, 2018 at 6:10 AM, Nikita Amelchev
> wrote:
>
> > Hello, Igniters.
> >
> > I am working on task
TE-9301 and I'm
> > trying to disable test failure.
> >
> > Help with .Net is really appreciated. I think it should not be a difficult
> > issue.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 16 авг. 2018 г. в 2:17, Vyacheslav Daradur
Hi, Igniters!
I found that TC build plan named "Platform C++ (Windows x86)" failed
with compilation error in master branch, with the following error:
java.obj error LNK2001: unresolved external symbol __imp__JNI_CreateJavaVM@12
C:\BuildAgent\work\ae48a463bd611b52\modules\platforms\cpp\project\vs\
Sapego wrote:
>>
>> Yeah, I know.
>>
>> There is no 32-bit JDK for Java 9 on Windows.
>>
>> So, I guess, we have no other choice but to stop supporting of
>> 32 bit version client for Java 9 and later.
>> Best Regards,
>> Igor
>>
>>
>&
Hi,
I think we should provide an article "Ignite.C++ development" in the
project's wiki.
Such article as "Ignite.NET Development" [1] helped me to prepare the
environment step by step.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Ignite.NET+Development
On Wed, Aug 22, 2018 at 12:06 PM
Hi, Igniters!
I’m working on Service Grid redesign tasks and design seems to be finished.
The main goal of Service Grid redesign is to provide missed guarantees:
- Synchronous services deployment/undeployment;
- Failover on coordinator change;
- Propagation of deployments errors across the cluste
an you describe consequences of not having migration solution?
> > What will happen on the user side?
> >
> >
> > В Чт, 23/08/2018 в 14:44 +0300, Vyacheslav Daradur пишет:
> > > Hi, Igniters!
> > >
> > > I’m working on Service Grid redesign tasks and desig
Hi Igniters!
Ilya, I'm glad to see one more person who is interested in the
compression feature in Ignite.
I looked through the pull request and want to share following thoughts:
It's very dangerous using a custom algorithm in this way - you store
serialized data separate from a dictionary and t
I am also very interested in large standard datasets for
> Apache Ignite (or generators thereof) so that we can run precise benchmarks
> on various compression schemes. If you have any of the following, please
> get back to me.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
&
adata from a serialized object to a separate entity
- this will reduce an object's size.
On Mon, Aug 27, 2018 at 2:53 PM Vyacheslav Daradur wrote:
>
> According to my benchmarks - zstd compression algorithm [1] looks very
> interesting, it has a high compression ratio with quite goo
ld be great to
> > have an option to persist services and redeploy them after cluster restart.
> >
> > -Val
> >
> > On Fri, Aug 24, 2018 at 2:51 PM Dmitriy Pavlov
> > wrote:
> >
> > > Denis M. & Val please share your vision about this topic.
>
Hi Igniters!
I'm working on the following Service Grid tasks:
- IGNITE-8361 Use discovery messages for service deployment
- IGNITE-8362 Collect service deployment results asynchronously on coordinator
- IGNITE-8363 Handle topology changes during service deployment
- IGNITE-8364 Propagate deployed
ploy..."
> API.
>
> D.
>
> On Thu, Aug 30, 2018 at 5:04 AM, Vyacheslav Daradur
> wrote:
>
> > Hi Igniters!
> >
> > I had a private talk about new Service Grid design with: Alexey
> > Goncharuk, Vladimir Ozerov, Denis Mekhanikov, Nikolay Izhikov, An
Hi Igniters!
I've filled an umbrella ticket [1] to track all tickets which will be
implemented in phase 1.
We reworked internals completely that allow us to provide us with
several main features:
* synchronous deployment
* propagation of deployment errors across the cluster
* basic deployment fail
gt;> >>> provided by Ignite being only one possible approach, and users can
>>> >>> create their own Native Persistence variations. At least that what has
>>> >>> been said by Denis Magda at that time.
>>> >>>
>>> >>> May be creatin
Hi, Denis, how will the complexity of tasks be estimated?
On Fri, Dec 22, 2017 at 3:16 AM, Denis Magda wrote:
> Igniters,
>
> We at Ignite PMC put together a page with rules-of-thumb on when it’s a right
> time to promote a contributor to a committer:
> https://cwiki.apache.org/confluence/displ
Hi, Pavel, thanks for this improvement, but as far as I understood it
is compatibility mode with .NET Сore.
Are you going to port Ignite to native .NET Core, maybe in the next
major release?
On Fri, Dec 22, 2017 at 1:55 PM, Yakov Zhdanov wrote:
> Great news, Pavel! As a Linux user I will definit
> Please share your results when you have a chance.
>
> -Val
>
> On Wed, Dec 6, 2017 at 1:45 AM, Vyacheslav Daradur
> wrote:
>
>> Evgeniy, as far as I understand PDS and rebalancing are based on
>> page-memory approach instead of entry-based 3rd Party Persistence, so
Hi, Igniters!
I’m working on an implementation of 3rd party persistence solution.
The solution is annotated by CacheLocalStore annotation.
As far as I know, CacheLocalStore annotation means that server node
persists its own primary and backup partitions (please correct me if
I’m wrong).
How abo
ot; database, but
> each node has its independent db. If CacheStore isn't annotated with
> CacheLocalStore, then you can observe situation when data is persisted by
> node, which is neither primary, nor backup for the key.(i.e. we have
> transactional cache with near disabl
and removed in my view.
>
> -Val
>
> On Fri, Jan 5, 2018 at 10:57 AM, Vyacheslav Daradur
> wrote:
>
>> Hi, Igniters!
>>
>> I still need your advice about the situation in the first post in this
>> thread.
>>
>> >> How to handle CacheLocalSt
Hi, Vladimir, it's good news. I'm looking forward to new Ignite release!
Could you please share a release schedule for 'varint' optimizations?
The task [1] is waiting for review for 5 months.
[1] https://issues.apache.org/jira/browse/IGNITE-5097
On Fri, Jan 26, 2018 at 12:51 PM, Vladimir Ozero
Hi Igniters,
I've worked with Apache Ignite 3rd Party Persistent Storage tools recently.
I found that use of CacheLocalStore annotation has hidden issues, for example:
* rebalancing issues [1]
* possible data consistency issues [1]
* handling of CacheLocalStore on clients nodes [2]
Valentin K. c
t; >
>> > > Vyacheslav,
>> > >
>> > > +1 for dropping @CacheLocalStore.
>> > > Ignite have no support 2-phase commit for store and public API provides
>> > no
>> > > methods to users can easily implement it by themselves.
>&
Hi Valentin,
As far as I know, when persistence is enabled and Ignite can't
allocate new page-memory in the memory segment, then Ignite
automatically evict some data from RAM to PDS using Random-2-LRU
eviction algorithm. And there are no mechanisms to evict entries out
when PDS is enabled.
I'll b
That is good news! Congrats, Nikolay!
On Mon, Feb 5, 2018 at 12:21 PM, Anton Vinogradov wrote:
> The Project Management Committee (PMC) for Apache Ignite
> has invited Nikolay Izhikov to become a committer and we are pleased
> to announce that he has accepted.
>
> Nikolay is an author of the Spar
Hi Pavel,
I've noticed that usually abandoned tickets are tickets without
specified "Fix Version", otherwise tickets should be viewed once at
least by release manager for moving to next release.
Should we do "Fix Version" as required field?
On Mon, Feb 5, 2018 at 3:44 PM, Дмитрий Рябов wrote:
nTest
CacheDeploymentTestStoreFactory
Should we annotate such classes as deprecated too?
On Wed, Jan 31, 2018 at 4:07 PM, Vyacheslav Daradur wrote:
> I filed the ticket [1] and will do it soon.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-7588
>
> On Tue, Jan 30, 2018 at 2:27 PM, Anton Vinogr
are test classes, there is not reason to put deprecation on them. We
> need to deprecate anything that is part of public API (in this case I
> believe it's only this annotation, nothing else).
>
> -Val
>
> On Tue, Feb 13, 2018 at 7:09 AM, Vyacheslav Daradur
> wrote:
Hi Anton,
Apache Ignite is licensed under the Apache License Version 2.0, which
does not allow to use author tag in java code [1].
[1]
http://directory.apache.org/fortress/coding-standards.html#classinterface-headers
On Wed, Feb 14, 2018 at 11:23 AM, Антон Калашников wrote:
> Hello Ignite Comm
; >
>> > [1]
>> > https://cwiki.apache.org/confluence/display/IGNITE/How+
>> > to+Contribute#HowtoContribute-ReviewProcessandMaintainers
>> >
>> > 2018-02-14 11:42 GMT+03:00 Vyacheslav Daradur :
>> >
>> > > Hi Anton,
>>
Dmitry, it's a great idea!
Nikolay, I also have the interest to get familiar with Spark Data
Frames integration.
I'd prefer webinar of the format similar to "Ignite Persistent Store
Walkthrough" by Denis Magda, which has been presented some times ago.
On Wed, Feb 14, 2018 at 5:03 PM, Dmitriy Set
/pull/2382
[3] https://ci.ignite.apache.org/viewLog.html?buildId=1105939
On Fri, Aug 4, 2017 at 11:41 AM, Vyacheslav Daradur wrote:
> Hi Igniters,
>
> Working on my task I found a bug at call the method #stopGrid(name),
> it produced ClassCastException. I created a ticket[1].
>
>
Hi, Nikolay
Please login to TeamCity and choose "My
On Thu, Feb 22, 2018 at 1:20 PM, Nikolay Izhikov wrote:
> Hello, Dmitriy
>
> I'm looked in TeamCity but not sure what should I do.
> Can you explain it to me, please?
>
> В Чт, 22/02/2018 в 10:13 +, Dmitry Pavlov пишет:
>> Hi Nikolay,
>>
>
Hi, Nikolay
Please login to TeamCity and choose "My Investigations" [1] in account menu.
[1] https://ci.ignite.apache.org/investigations.html?init=1
On Thu, Feb 22, 2018 at 1:25 PM, Vyacheslav Daradur wrote:
> Hi, Nikolay
>
> Please login to TeamCity and choose "My
&g
Hi, Dmitry, could you please review it, because you are one of the
most experienced people in the testing framework.
Please see comment in Jira, because it is in pretty-format there.
On Thu, Feb 22, 2018 at 11:56 AM, Vyacheslav Daradur
wrote:
> Hi Igniters!
>
> I have investigated the
ting framework. Hope you also will join to this review .
>
> Sincerely,
> Dmitiry Pavlov
>
>
> чт, 1 мар. 2018 г. в 11:13, Vyacheslav Daradur :
>>
>> Hi, Dmitry, could you please review it, because you are one of the
>> most experienced people in the testing frame
I agree with Anton, especially with the following statement:
>> Ignite should be assemblied using package phase,
>> not install in case you want only to assembly it.
Approach with "install" phase may lead to hidden issues in a
development environment.
On Thu, Mar 1, 2018 at 2:26 PM, Nikolay Izhik
gt;
> чт, 1 мар. 2018 г. в 17:23, Petr Ivanov :
>
>> Anton, Vyacheslav — are you proposing assembly process shift to package
>> phase, yet leaving the special profile for assembly itself?
>>
>>
>>
>> > On 1 Mar 2018, at 14:36, Vyacheslav Daradur wrote:
Dima, great job!
Looking forward to the feature completion!
On Fri, Mar 2, 2018 at 9:23 AM, Denis Magda wrote:
> Dmitriy R., Nilokay,
>
> Thanks for the analysis and handout of the architectural design. No doubts,
> it would be a valuable addition to Ignite.
>
> I would encourage you creating an
Hi, Igniters!
This task [1] is about 'get' requests distribution between primary and
backup nodes in the replicated cache if 'readFromBackup' flag is
enabled.
I've prepared a solution [2] suggested by Alexei Scherbakov in Jira
comments. It passed prereviews by Alexei and Nikolay Izhikov.
TeamCit
301 - 400 of 477 matches
Mail list logo
