+1
ср, 13 мая 2020 г., 07:35 Alexey Zinoviev :
> +1
>
> ср, 13 мая 2020 г., 5:52 Saikat Maitra :
>
> > +1
> >
> > Regards
> > Saikat
> >
> > On Tue, 12 May 2020 at 7:03 PM, Denis Magda wrote:
> >
> > > Igniters,
> > >
> > > As it was discussed earlier [1], it feels like we abandoned the
> > deve
Can you, please, send us
1. Detailed error message(stack trace, etc)
2. Ignite configuration.
Any other details that can be usefull.
> 8 мая 2020 г., в 22:08, C Ravikiran написал(а):
>
> Last 2 years there is no code changes.
> Our application is running in only one node.
>
> Our daily data
+1 to release 2.9 right after 2.8.1
> 8 мая 2020 г., в 12:53, Maxim Muzafarov написал(а):
>
> Folks, Denis,
>
>
> I think no one will argue against that frequent releases is good. The
> last major 2.8 release scope was frozen the last December, so having
> the next 2.9 release in September sou
-autoconfigure-ext/1.0.0/
*
https://repo.maven.apache.org/maven2/org/apache/ignite/ignite-spring-boot-thin-client-autoconfigure-ext/1.0.0/
Please let us know [2] if you encounter any problems.
Regards,
Nikolay Izhikov on behalf of Apache Ignite community
[1] https://ignite.apache.org
[2] https
anchForTc=ignite-2.8.1
>> [2]:
>>
>> https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull%2F7755%2Fhead&action=Latest&baseBranchForTc=ignite-2.8.1
>>
>> вт, 28 апр. 2020 г. в 15:19, Nikolay Izhikov :
>&g
Congrats.
> 7 мая 2020 г., в 14:54, Ivan Pavlukhin написал(а):
>
> Maxim,
>
> My congratulations! Well deserved!
>
> P.S. We should mention snapshots for persistent caches in the
> achievement list. Great job!
>
> Best regards,
> Ivan Pavlukhin
>
> чт, 7 мая 2020 г. в 14:47, Dmitriy Pavlov :
Hello.
+1 to remove any graphical utilities from the Ignite core.
I think we should maintain and support only cmd, JMX, and other «core» tools.
We shouldn't waste our resources on supporting pretty looking UI tools.
> 2 мая 2020 г., в 04:05, Saikat Maitra написал(а):
>
> Hello Denis,
>
> I a
The vote for a new release candidate is closed, now
Vote result: Vote passes with 4 votes +1 (4 binding +1 votes), no 0 and no -1.
+1 votes:
- Nikolay Izhikov (binding)
- Maxim Muzafarov (binding)
- Saikat Maitra (binding)
- Denis Magda (binding)
Vote thread
https://lists.apache.org
Hello, Maxim.
I can confirm this itching issue.
It also happens when some custom Security plugin throws an exception while
processing a communication message.
```
UUID newSecSubjId = secSubjId != null ? secSubjId : nodeId;
try (OperationSecurityContext s = ctx.security().withContext(newSecSubjI
+1 (binding)
Check extension with the example application -
https://github.com/nizhikov/ignite-spring-boot-autoconfigure-example
> 1 мая 2020 г., в 19:06, Nikolay Izhikov написал(а):
>
> The vote will hold for 72 hours and will end on May 4 2020 17:00 UTC
> https://www.tim
The vote will hold for 72 hours and will end on May 4 2020 17:00 UTC
https://www.timeanddate.com/countdown/generic?iso=20200504T20&p0=166&font=cursive&csz=1
> 1 мая 2020 г., в 19:03, Nikolay Izhikov написал(а):
>
> Dear Community,
>
> I have uploaded a release can
Dear Community,
I have uploaded a release candidate of the two extension modules
`ignite-spring-boot-autoconfigure` and
`ignite-spring-boot-client-autoconfigure`.
The following staging can be used for testing:
Tag with name `ignite-spring-boot-1.0.0-rc2` created:
https://gitbox.apache.org/rep
Officially cancelling the vote due to wrong artifacts naming.
> Spring Boot artifacts this way?
>
> - ignite-spring-boot-autoconfigure-ext
> - ignite-spring-boot-thin-client-autoconfigure-ext
>
>
> Overall, I don't see anyone raising other issues related to the release. If
> the naming suggestion sounds reasonable the
ve a server node in your spring boot project via
> ignite-spring-boot? If so, how?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 30 апр. 2020 г. в 11:11, Nikolay Izhikov :
>
>> Hello, Denis.
>>
>> Pages moved to - https://apacheignite-mix.readme.io/
e avoid situations when the pages are created in a rush after
> the vote is completed or a version is announced without documentation in
> place. Also, by reading final documentation we can look at the feature from
> the angle of Ignite application developers and spot usability issues be
Hello, Denis.
https://apacheignite-mix.readme.io/docs/spring-boot
> 30 апр. 2020 г., в 02:04, Denis Magda написал(а):
>
> Nikolay, the problem is solved and I've arranged access for you. Please feel
> free to move the Spring Boot docs to these docs as suggested in the vote
> thread:
> https:/
te:
>
>> +1
>>
>> вт, 28 апр. 2020 г. в 11:27, Nikolay Izhikov :
>>
>>> *** Formal vote description fixed ***
>>>
>>> Dear Community,
>>>
>>> I have uploaded a release candidate of the two extension modules
>>> `ig
lass for cache
> with indexed types
> IGNITE-12855 Fixed node failure with concurrent get operation and entry
> expiration when persistent is enabled
> Both fixes prevent node failure in some circumstances, both fixed already
> merged to master.
>
> WDYT?
>
> пн, 27 апр
*** Formal vote description fixed ***
Dear Community,
I have uploaded a release candidate of the two extension modules
`ignite-spring-boot-autoconfigure` and
`ignite-spring-boot-client-autoconfigure`.
The following staging can be used for testing:
https://repository.apache.org/content/reposito
NITE/Release+Process#ReleaseProcess-4.1EnsureDocumentationReadinessandAccouncementBlogPostActivity
>>>
>> [2]
>>
>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Changes-in-Ignite-release-process-related-to-documentation-td46471.html
>> [3] https://
Hello, Igniters.
Right now I working on POC for some «framework» for integration testing of
Ignite.
Feature I want to see in this framework:
* To manage several Ignite instances inside docker or bare metal
servers.
* To manage Ignite cluster
* Start/stop arbitrary appli
+1 (binding)
I’ve checked uploaded artifacts with the test application [1]
[1] https://github.com/nizhikov/ignite-spring-boot-autoconfigure-example
> 27 апр. 2020 г., в 23:24, Nikolay Izhikov написал(а):
>
> Dear Community,
>
> I have uploaded a release candidate of the two ex
Dear Community,
I have uploaded a release candidate of the two extension modules
`ignite-spring-boot-autoconfigure` and
`ignite-spring-boot-client-autoconfigure`.
The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1478/
Tag with na
Hello, Konstantin.
> I think we cannot just turn this optimization on
Why is that?
If we turn on `OPTIMIZE_REUSE_RESULT` consequences would be the following:
* concurrent updated of the subquery table will not be used(we have no
guarantee on that, for now)
* performance of the select increase
+1 to force upper case for `static final` variables.
> 25 апр. 2020 г., в 07:39, Ivan Pavlukhin написал(а):
>
> Maxim,
>
> Thank you for efforts in a code quality improvement!
>
> Unfortunately I do not agree with the proposal. Usually I like to
> refer a following guide [1]. While a question
tion -Pavel
Tupitsyn
IN PROGRESS:
IGNITE-12637IgniteSparkSession doesn't start the clients on really
distributed cluster - Yaroslav Molochkov
IGNITE-12788Cluster achieved fully rebalanced (PME-free ready) state metric
- Nikolay Izhikov
PATCH AVAILABLE:
IGN
Hello, Slava, Ilya, Denis.
Thanks for joining this discussion!
> - visor (which is deprecated)
Who deprecated visor and when?
Maybe I miss something?
> - web-console (to be honest, I don't quite understand the status of this tool)
+1.
> I am not against the new tool, I just want to understan
s in progress now and I'll reply with news if I have any.
>
> Andrey Gura, Nikolay Izhikov, are you OK with 3 more commits in the scope?
> If you don't,
> then I won't be able to port IGNITE-12756 to 2.8.1 properly by myself, I
> guess it would be
> easier to reimpl
:
> https://github.com/apache/ignite/pull/7708
>
> вт, 21 апр. 2020 г. в 17:17, Nikolay Izhikov :
>
>> OK then, let’s include it in the 2.8.1
>>
>> Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain
>> cherry-pick for all required comm
s without using internal API's, code improvements)
>
> But! It also fixes potential NPE's which can be thrown on node start.
> So it would be great to include this fix to 2.8.1 release.
>
> On Tue, Apr 21, 2020 at 11:12 AM Nikolay Izhikov wrote:
>>
>>> I
What about dotnet and cpp thin clients?
> 21 апр. 2020 г., в 16:19, Dmitriy Pavlov написал(а):
>
> +1 since
> - Simpler release may allow us to release more often
> - Often releases - users will get updates faster, more chances to grow and
> keep our user base
> - Faster updates and easy to get
d visa from TC bot.
>
> [1]. https://github.com/apache/ignite/pull/7703
>
> On 21.04.2020 12:52, Nikolay Izhikov wrote:
>> Igniters.
>>
>> Can someone from Grid Gain help me with setup TC bot to monitor ignite-2.8.1
>> branch?
>>
>>> 21 а
Nikolay Izhikov created IGNITE-12926:
Summary: [ignite-extensions] build failed
Key: IGNITE-12926
URL: https://issues.apache.org/jira/browse/IGNITE-12926
Project: Ignite
Issue Type: Test
Igniters.
Can someone from Grid Gain help me with setup TC bot to monitor ignite-2.8.1
branch?
> 21 апр. 2020 г., в 11:11, Nikolay Izhikov написал(а):
>
>> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
>
>
> Thanks!
>
>> considering commit "683f
Nikolay Izhikov created IGNITE-12924:
Summary: [ignite-extensions] Unused import breaks checkstyle
Key: IGNITE-12924
URL: https://issues.apache.org/jira/browse/IGNITE-12924
Project: Ignite
-12735 and
>> https://issues.apache.org/jira/browse/IGNITE-12568,
>> both were targeted to 2.9, but this has to be changed probably.
>>
>> There might be other issues that I didn't find, we should probably ask
>> Andrey Gura about it, he is the author o
hread dumps generation on
system failure.
+ c97b08e672 IGNITE-12491 Dirty pages count calculation optimized.
> 18 апр. 2020 г., в 18:59, Nikolay Izhikov написал(а):
>
> Hello, Igniters.
>
> After some scripting I got the following lists of commits to transfer from
> master to
the original ticket in patch available then and leave a
> comment.
>
> Let us know if need any help with moving commits to the release branch.
>
> пт, 17 апр. 2020 г. в 18:18, Nikolay Izhikov :
>
>> Please, don’t cherry pick tickets to 2.8.1
>> It seems I hav
https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/metric/SystemViewSelfTest.java#L236
[3] https://issues.apache.org/jira/browse/IGNITE-12745
ср, 8 апр. 2020 г. в 23:10, Denis Magda :
> Igniters,
>
> There was a private discussion bet
you
> prefer this ticket to be cherry-picket to 2.8.1 yourself or should I merge
> it to the release branch?
>
> пт, 17 апр. 2020 г. в 16:55, Ivan Pavlukhin :
>
>> Great!
>>
>> Best regards,
>> Ivan Pavlukhin
>>
>> пт, 17 апр. 2020 г. в 12:48, Ni
e it is
> important to know who is a release manager (the current thread subject
> has a "Manager" keyword). E.g. I do not know who is a manager for
> 2.8.1.
>
> Best regards,
> Ivan Pavlukhin
>
> пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov :
>>
>> Hell
A side note from an external spectator. Should not we reflect on the
>> release page [1] who is a release manager?
>>
>> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1
>>
>> Best regards,
>> Ivan Pavlukhin
>>
>> пт, 17 апр.
ulated bug-fixes `as is` and schedule the next 2.8.2 release.
>> This will allow as to have shorten minor releases.
>>
>> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov wrote:
>>>
>>> Hello, Igniters.
>>>
>>> I’m started to work on this 2.8.
gt;>>>
>>>> I observed that we already have release 2.8.1 branch
>>>> https://github.com/apache/ignite/tree/ignite-2.8.1
>>>>
>>>> In that case we should be ok to merge these 2 open PRs in master to
>> make
>>> it
>>>&g
I’ve added this files to the ignite svn.
> 14 апр. 2020 г., в 01:57, Maxim Muzafarov написал(а):
>
> Folks,
>
>
> As another suggestion, we can place such files (pgp, sha512) here
> https://downloads.apache.org/ignite/gce/ (`gce` directory must be
> created). I don't have access rights there.
> On another hand, it seems weird to have both TeamCity and Travis
And don’t forget MTCGA bot!
> 14 апр. 2020 г., в 10:23, Pavel Tupitsyn написал(а):
>
> We should have PR checks for sure.
>
> On one hand, I agree with Denis:
> - Travis is very easy to set up in GitHub
> - Config file (travis
Hello, Maxim.
Great to see such an important feature in Ignite!
Please, let me know if you need any help with review.
> 7 апр. 2020 г., в 22:10, Maxim Muzafarov написал(а):
>
> Igniters,
>
>
> I'd like to back to the discussion of a snapshot operation for Apache
> Ignite for persistence cache
Nikolay Izhikov created IGNITE-12872:
Summary: Check of correct work of explicit security permissions
Key: IGNITE-12872
URL: https://issues.apache.org/jira/browse/IGNITE-12872
Project: Ignite
Nikolay Izhikov created IGNITE-12859:
Summary: .Net services fails to call method with DateTime or Guid
argument
Key: IGNITE-12859
URL: https://issues.apache.org/jira/browse/IGNITE-12859
Project
Hello, Denis.
Good to hear.
Thanks for your work!
> 2 апр. 2020 г., в 21:15, Denis Magda написал(а):
>
> Hi Community,
>
> As per our earlier conversation, I've initiated the website migration
> procedures:
> https://issues.apache.org/jira/browse/INFRA-20065
>
> We'll keep you posted on the p
s far as my understanding goes, v4.0 is for .Net classic, such as Mono.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 1 апр. 2020 г. в 13:04, Nikolay Izhikov :
>>
>>> Hello. Igniters.
>>>
>>> I working on some issue in .
Hello. Igniters.
I working on some issue in .Net platforms and found that different project
files for .Net contains different platform versions.
Can someone explain why?
1. Apache.Ignite.Core.csproj [1]
```
...
v4.0
...
```
2. Apache.Ignite.Core.DotNetCore.csproj
```
have no contract
> and it's safe to change the semantic.
> But we should recheck search results twice because we're talking about the
> security.
>
> On Wed, Apr 1, 2020 at 11:44 AM Nikolay Izhikov wrote:
>
>> Hello, Anton.
>>
>> What is «contract»
we could
>> just add checks for CACHE_CREATE / CACHE_DESTROY there along
>> with ADMIN_CACHE.
>>
>> вт, 31 мар. 2020 г. в 12:30, Nikolay Izhikov :
>>
>>> Hello, Sergey.
>>>
>>>
>>> I’m +1 to make this change.
>>>
>>
Hello, Ali.
This fix would be available in 2.8.1.
> 30 марта 2020 г., в 21:09, Nikolai Kulagin
> написал(а):
>
> Ali, yes, this problem has been fixed.
>
> пн, 30 мар. 2020 г. в 11:44, Nikolay Izhikov :
>
>> Hello, Ali.
>>
>> Looks like thi
Hello, Sergey.
I’m +1 to make this change.
I think we should make security consistent across all APIs.
> 31 марта 2020 г., в 12:14, Sergei Ryzhov написал(а):
>
> Hello!
> Now the work of permissions for API IgniteClient and REST is different.
> To create/delete a cache:
> IgniteClient authori
Hello.
Sorry, I can’t see any code.
Can you create a gist and sent us link to it?
> 30 марта 2020 г., в 20:19, myset написал(а):
>
> Please see the code bellow:
>
> *Ignite service definition
> ...
>
> ...
> *TestService interface*
>
>
> *Test class*
>
>
> *TestServiceImpl class*
>
>
>
Hello.
Sill lack of information.
Please, send stack trace and piece of code that produce the error.
> 30 марта 2020 г., в 18:33, myset написал(а):
>
> Thank you for answer Nikolay,
> I receive various null pointer exceptions @ runtime on TestServiceImpl for
> all fields extended from Test clas
Hello, Ali.
Looks like this is known issue and it was fixed by [1]
Nikolay, can you confirm it?
[1]
https://github.com/apache/ignite/commit/d0bae90bce33dbed8b9f3cd52663ce5efa545d97
> 28 марта 2020 г., в 12:30, ali hassan написал(а):
>
> Hi,
> I failed to connect ignitevisorcmd.sh to my grid.
Hello.
Can you, please, clarify your issue?
Is there any stack trace of logs that can make issue more clear.
Can you, please, show us the code that is cause error?
> 28 марта 2020 г., в 21:43, myset написал(а):
>
> Hi everybody,
> Some body encountered similar issue ?
> It is a matter of seria
which
>>> requires explicit confirmation from the user.
>>> Please take a look at DeactivateCommand#prepareConfirmation and its
>> usages.
>>> It seems to me, this mode has the same aim as the forceDeactivation flag.
>>> We can change the message returned by
&
a/browse/IGNITE-11894
>
> Best regards,
> Ivan Pavlukhin
>
> чт, 26 мар. 2020 г. в 17:54, Nikolay Izhikov :
> >
> > Hello, Igniters.
> >
> > Right now there is no way for the user to set fetchSize of the JdbcStore
> > This leads to the poor performance of t
Hello, Igniters.
Right now there is no way for the user to set fetchSize of the JdbcStore
This leads to the poor performance of the cache load with the 3-d party
persistence [1]
I propose to add JdbcDialect#setFetchSize method [2]
Thoughts?
[1] https://issues.apache.org/jira/browse/IGNITE-1282
Nikolay Izhikov created IGNITE-12841:
Summary: @Override must be on the same line as a method
Key: IGNITE-12841
URL: https://issues.apache.org/jira/browse/IGNITE-12841
Project: Ignite
Nikolay Izhikov created IGNITE-12834:
Summary: [TeamCity] Suites fails with the execution timeout
Key: IGNITE-12834
URL: https://issues.apache.org/jira/browse/IGNITE-12834
Project: Ignite
the deactivation command
> (control-utility.sh) already has a confirmation option.
> Perhaps, we need to clearly state the consequences of using this command
> with in-memory caches.
>
> Thanks,
> S.
>
> вт, 24 мар. 2020 г. в 12:51, Nikolay Izhikov :
>
>> Hello, Alexey.
Hello, Alexey.
I just repeat our agreement to be on the same page
> The confirmation should only present in the user-facing interfaces.
1. We should add —force flag to the command.sh deactivation command.
2. We should throw the exception if cluster has in-memory caches and
—force=false.
3. We s
gt; the
>>> javadoc.
>>> I'm also against some "temporary" API.
>>>
>>> We should:
>>>
>>> 1. Partially remove IGNITE-12701 except javadoc part. Note control.sh
>> for a
>>> long time has support for a confirmation on dea
memory state
> after subsequent reactivation.
> 3. Describe current behavior for in-memory cache on deactivation in Ignite
> documentation.
>
>
> пн, 23 мар. 2020 г. в 21:22, Nikolay Izhikov :
>
>> Hello, Ivan.
>>
>>> Seems like we don't have a final a
> Thoughts?
>
> [1]: https://issues.apache.org/jira/browse/IGNITE-12614
> [2]: https://issues.apache.org/jira/browse/IGNITE-12701
>
> --
> Ivan
>
>
> On Tue, Mar 17, 2020 at 2:26 PM Vladimir Steshin wrote:
>
>> Nikolay, I think we should reconsider cleari
Nikolay Izhikov created IGNITE-12815:
Summary: [IEP-39] Management API to cancel SQL queries.
Key: IGNITE-12815
URL: https://issues.apache.org/jira/browse/IGNITE-12815
Project: Ignite
Nikolay Izhikov created IGNITE-12814:
Summary: [IEP-39] Management API to cancel continuous queries.
Key: IGNITE-12814
URL: https://issues.apache.org/jira/browse/IGNITE-12814
Project: Ignite
Nikolay Izhikov created IGNITE-12813:
Summary: [IEP-39] Management API to cancel scan queries.
Key: IGNITE-12813
URL: https://issues.apache.org/jira/browse/IGNITE-12813
Project: Ignite
Nikolay Izhikov created IGNITE-12812:
Summary: [IEP-39] Management API to cancel transaction.
Key: IGNITE-12812
URL: https://issues.apache.org/jira/browse/IGNITE-12812
Project: Ignite
Nikolay Izhikov created IGNITE-12811:
Summary: [IEP-39] Management API to cancel services.
Key: IGNITE-12811
URL: https://issues.apache.org/jira/browse/IGNITE-12811
Project: Ignite
Issue
Nikolay Izhikov created IGNITE-12810:
Summary: [IEP-39] Management API to cancel compute tasks.
Key: IGNITE-12810
URL: https://issues.apache.org/jira/browse/IGNITE-12810
Project: Ignite
I want to be a release manager.
> 19 марта 2020 г., в 17:52, Denis Magda написал(а):
>
> Igniters,
>
> As long as 2.8.1 is inevitable and we already keep adding critical issues
> to the working queue, let's settle on the release time frames and decide
> who will be a release manager. This is t
o emphasize overall ability to lose
> various objects, not only data. Probably might be reconsidered in future.
>
>
> 17.03.2020 13:49, Nikolay Izhikov пишет:
>> Hello, Vladimir.
>>
>> If there is at lease one persistent data region then system data region also
&g
Hello, Vladimir.
If there is at lease one persistent data region then system data region also
becomes persistent.
Your example applies only to pure in-memory clusters.
And should be covered with the —force parameter we added.
What do you think?
> 17 марта 2020 г., в 13:45, Vladimir Steshin на
Nikolay Izhikov created IGNITE-12791:
Summary: [IEP-39] Management API to cancel user provided tasks and
queries - documentation
Key: IGNITE-12791
URL: https://issues.apache.org/jira/browse/IGNITE-12791
bd1712ad01c9'
KILL COMPUTE_TASK '58b48c3e071-b2d221ca-ab08-4544-b8dc-8475538ed42f'
KILL SERVICE 'my-svc'
```
[1] https://github.com/apache/ignite/pull/7520
[2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145724615
[3] https://issues.apache.org/ji
Hello, guys.
I propose myself as a release manager for 2.8.1.
> 16 марта 2020 г., в 14:19, kpushenko написал(а):
>
> Hi, igniters!
>
> I would like to propose a discussion of version 2.9 and scope releases for
> 2020 to another discussion thread.
>
> I understand that there is no objection to
Hello, Mikhail.
Can you, please, double-check link to the ticket?
For now it’s a IGNITE-12049 Add user attributes to thin clients which is
resolved.
> 16 марта 2020 г., в 12:04, Mikhail Petrov написал(а):
>
> Hello, Igniters.
>
> I'd like to propose a small improvement in control.sh configur
Nikolay Izhikov created IGNITE-12785:
Summary: KILL QUERY command doesn't support parameters
Key: IGNITE-12785
URL: https://issues.apache.org/jira/browse/IGNITE-12785
Project: I
Nikolay Izhikov created IGNITE-12782:
Summary: [IEP-39] Interrupt service method executions on service
cancel.
Key: IGNITE-12782
URL: https://issues.apache.org/jira/browse/IGNITE-12782
Project
ing. I will be happy to help with the announcement and
>> scheduling.
>> Dmitry, what do you think? ASF slack looks less comfortable for this
>> purpose.
>>
>> чт, 12 мар. 2020 г. в 11:22, Nikolay Izhikov :
>>
>>> Yes.
>>>
>>>> 12 марта
Hello, Petr.
> I thought the release cycle should be community driven, not single donator.
We are the part of the global Ignite community, itn’t it?
If you know some reason to postpone bug fix releases, please, write it down.
> what's the haste with next minor version?
Users of the Ignite acti
Hello, Igniters.
I propose to add these tickets to the 2.8.1 scope
[1] Disallow silent deactivation in CLI and REST -
https://issues.apache.org/jira/browse/IGNITE-12701
[2] Compute job system view - https://issues.apache.org/jira/browse/IGNITE-12745
[3] Transaction operations metrics -
https://
Nikolay Izhikov created IGNITE-12778:
Summary: KILL QUERY command doesn't close already fetched cursor
Key: IGNITE-12778
URL: https://issues.apache.org/jira/browse/IGNITE-12778
Project: I
Yes.
> 12 марта 2020 г., в 10:59, Maksim Stepachev
> написал(а):
>
> It's the perfect idea. Will it in English?
>
> чт, 12 мар. 2020 г. в 10:15, Nikolay Izhikov :
>
>> Hello, Igniters.
>>
>> I want to organize the webinar for the Apache Ignite com
Hello, Igniters.
I want to organize the webinar for the Apache Ignite community.
The subject of the webinar - «New monitoring and system view in 2.8»
Is there any Apache guides on how to do it?
What software should be used? How I should announce it? etc...
or issues left with
>> documentation.
>> Are we ready to announce 2.8 release widely?
>>
>>
>> On Tue, 10 Mar 2020 at 12:10, Nikolay Izhikov
>>
>> wrote:
>>
>>> Hello, Igniters.
>>>
>>> I rewrote pages about new metrics
Hello, Igniters.
I prepared a PR for the new system view - JOBS. [1]. Ticket [2]
For now, as you may know, internally we have two processors that implement
compute feature:
* `GridTaskProcessor` - manage locally started compute tasks.
* `GridJobProcessor` - manage compute jobs that should be e
Nikolay Izhikov created IGNITE-12763:
Summary: OpenCensus integration example.
Key: IGNITE-12763
URL: https://issues.apache.org/jira/browse/IGNITE-12763
Project: Ignite
Issue Type: Sub
gt;>>>>>> Are your sure? Was not the feature implemented for java thin client
>>>>>>>> in [1]?
>>>>>>>>
>>>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-11898
>>>>>>>>
>>&g
;> https://mvnrepository.com/artifact/org.apache.ignite/ignite-co
>>>>>>> re/2.8.0
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Ivan Pavlukhin
>>>>>>>
>>>>>>> ср, 4 мар. 2020 г. в 17:
>> Ivan Pavlukhin
>>>>>>>
>>>>>>> ср, 4 мар. 2020 г. в 17:08, Denis Magda :
>>>>>>>>
>>>>>>>> Dmitriy,
>>>>>>>>
>>>>>>>> Ignite 2.8 will be announced as soon
Nikolay Izhikov created IGNITE-12749:
Summary: Unsupported operation exception on node stop if
collisionspi not null
Key: IGNITE-12749
URL: https://issues.apache.org/jira/browse/IGNITE-12749
cancellation
>>>>
>>>>
>>>>- JDBC: Support for query timeout
>>>>
>>>>
>>>>- suspend/resume for pessimistic transactions
>>>>
>>>>
>>>>- WAL page compression
>>>>
>
301 - 400 of 1139 matches
Mail list logo
