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, 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
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
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
&
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
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.
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.
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, 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, 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
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.
>>>
>>
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»
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
```
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, 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
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
> 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
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.
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
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.
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 апр.
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
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
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
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
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
-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
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
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 а
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
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
:
> 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 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
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
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
+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
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
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
+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
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
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://
*** 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
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 апр
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
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:/
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
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/
> 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
Officially cancelling the vote due to wrong artifacts naming.
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
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
+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
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
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.
+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
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 :
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
-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
+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
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
ср, 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
ect current vision of release date?
>
> [1]. https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1
>
> чт, 7 мая 2020 г. в 17:23, Nikolay Izhikov :
>
>> Done.
>>
>>
>>> 7 мая 2020 г., в 13:20, Denis Garus написал(а):
>>>
&g
Hello, Igniters.
I prepared a PR with release notes.
Please, take a look [1]
[1] https://github.com/apache/ignite/pull/7821
> 20 мая 2020 г., в 13:06, Nikolay Izhikov написал(а):
>
> Hello, Jury.
>
> It seems we reached code freeze step for 2.8.1 release.
> I will prepare
Hello, Igniters.
I created a PoC [1] for the integration tests of Ignite.
Let me briefly explain the gap I want to cover:
1. For now, we don’t have a solution for automated testing of Ignite on «real
cluster».
By «real cluster» I mean cluster «like a production»:
* client and server nod
it on custom OS (eg. Windows)?
> Is it possible to perform in on bare metal?
>
> I hope you'll answer yes to all, and the question mostly about details.
>
> On Thu, May 21, 2020 at 10:27 AM Nikolay Izhikov
> wrote:
>
>> Hello, Igniters.
>>
>> I creat
f these has times not concording with "fixed".
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 20 мая 2020 г. в 15:47, Nikolay Izhikov :
>
>> Hello, Igniters.
>>
>> I prepared a PR with release notes.
>> Please, take a look [1]
>&g
Done, thanks.
> 21 мая 2020 г., в 16:34, Ilya Kasnacheev
> написал(а):
>
> Hello!
>
> Please apply https://github.com/apache/ignite/pull/7832
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 21 мая 2020 г. в 16:02, Nikolay Izhikov :
>
>> Hello
es of the framework. To my knowledge, Max has
> already been working on that for several days.
>
> -
> Denis
>
>
> On Thu, May 21, 2020 at 12:27 AM Nikolay Izhikov
> wrote:
>
>> Hello, Igniters.
>>
>> I created a PoC [1] for the integration tests of I
> Personally, I treat this as an anti-pattern that should have been influenced
> by some of the old Ignite examples.
+1
I don’t see any reason to support fields with the same name both in key and in
value from SQL.
Moreover, I think if we implement this feature then for some part of the users
Hello, Alexey.
Thanks for your feedback and clarification.
> you have to explicitly specify fields having the same name inside the Key and
> Value.
By all of this we just make Ignite more complex in favor of single, wrong
use-case.
Moreover, you hurt another use-cases with this feature.
I don’
Dear Community,
I have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.8.1-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.8.1-rc1/
The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1481
Hello, Alexei.
I think we want to implement this feature without nodes restart.
In the ideal scenario all nodes will stay alive and respond to the user
requests.
> 24 мая 2020 г., в 15:24, Alexei Scherbakov
> написал(а):
>
> Pavel Pereslegin,
>
> I see another opportunity.
> We can use rebal
Hello,
Branch with duck tape created -
https://github.com/apache/ignite/tree/ignite-ducktape
Any who are willing to contribute to PoC are welcome.
> 21 мая 2020 г., в 22:33, Nikolay Izhikov написал(а):
>
> Hello, Denis.
>
> There is no rush with these improvements.
> We
restriction is necessary ?
>> Most likely having a currently re-encrypting node serving only demand
>> requests will have least preformance impact on a grid.
>>
>> пн, 25 мая 2020 г. в 11:08, Nikolay Izhikov :
>>
>>> Hello, Alexei.
>>>
>>> I
restriction is necessary ?
>>> Most likely having a currently re-encrypting node serving only demand
>>> requests will have least preformance impact on a grid.
>>>
>>> пн, 25 мая 2020 г. в 11:08, Nikolay Izhikov :
>>>
>>>> Hello, Alexei.
&g
he re-encryption using full rebalancing, proposed
> by me earlier.
>
>
>
> пн, 25 мая 2020 г. в 11:27, Nikolay Izhikov :
>
>>> And definitely this approach is much simplier to implement
>>
>> I agree.
>>
>> If we allow to made nodes offline
gt;
> On Fri, May 22, 2020 at 3:57 AM Nikolay Izhikov wrote:
>
>> Dear Community,
>>
>> I have uploaded release candidate to
>> https://dist.apache.org/repos/dist/dev/ignite/2.8.1-rc1/
>> https://dist.apache.org/repos/dist/dev/ignite/packages_2.8.1-r
> Nikolay, btw, what's your thinking on the approach proposed by me?
Makes sense.
> 26 мая 2020 г., в 14:07, Alexey Sasov написал(а):
>
> Hello. Looks good. What whould be returned from the query like this "select
> _key from cache" if we don't know the type of the key? ExpandoObject, Tuple,
>
Hello, Igor.
I’m ++1 for this change.
How build system relates to major version of product?
I think we can change the way we build modules any time we want.
> 26 мая 2020 г., в 16:02, Igor Sapego написал(а):
>
> Great!
>
> Let's start with creating a TC suite for it.
>
> The only concern I
Hello, Igor.
> Nikolay, removing support for a certain build system is a breaking change.
No, it’s not.
Why do you think so?
Development environment and build system is a subject to change in any project.
We can drop or add support of any build system any time we want.
> 26 мая 2020 г., в 16:35
Hello!
Apache Ignite 2.8.1 release RC1 has been accepted.
6 "+1" votes received.
Here are the votes received:
- Alexey Zinoviev (binding)
- Nikolay Izhikov (binding)
- Pavel Tupitsyn (binding)
- Ilya Kasnacheev (binding)
- Denis Magd
know if you encounter any problems:
https://ignite.apache.org/community/resources.html#ask
Regards,
Nikolay Izhikov on behalf of Apache Ignite community.
Snapshots.
> 3 июня 2020 г., в 16:10, Ilya Kasnacheev
> написал(а):
>
> Hello!
>
> Can you please clarify what is the scope of 2.9 release?
>
> I have a feeling that we don't really have any big features in the current
> 2.9 code base. No Calcite, etc.
>
> So I'm asking whether it is worth i
+1 To start release process for 2.9
+1 For Alexey Plekhanov as a release manager.
> 3 июня 2020 г., в 16:34, Alex Plehanov написал(а):
>
> Ilya,
>
> We already have a lot of features implemented in the master branch, but not
> released (perhaps not so big as Calcite, but still useful), some of
gt;> post),but
>>>>>> I
>>>>>>>>>> decided not to file a jira issue before discussion.
>>>>>>>>>> Now I see, that this feature are of great interest to
>>> community.
>>>>> So
>>>>>> I
>>>
e_verify.
>>>> Please, clarify your idea:
>>>> We should use some info from control.sh to the report?
>>>> The report should be generated by some control.sh subcommand?
>>> If I am not mistaken, the oracle database has AWR tool (mentioned on the
>>&
Hello, Andrey.
> I've just found that I should waste my time fixing styles in user code that
> (may be) reproduce some bug, just to validate the bug or fix provided by the
> user.
Why do you ignore code style rules while developing «quick reproducer»?
What specific code style rule is an issue
ut using any hacks to skip
> style checks with no intention to merge such code to master.
>
>
> On Mon, Jun 8, 2020 at 4:50 PM Nikolay Izhikov wrote:
>
>> Hello, Andrey.
>>
>>> I've just found that I should waste my time fixing styles in user code
>> that
I will take a look.
> 8 июня 2020 г., в 15:17, Ivan Daschinsky написал(а):
>
> Hi Igniters.
>
> I've recently submitted patch[1] that implemented subj.
> Any help with review would be appreciated.
>
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-12808
> --
> Sincerely yours, Ivan Das
> Is that OK?
We shouldn’t add any code that is broke some existing, widely used feature.
Let’s fix it before the merge.
> 10 июня 2020 г., в 13:54, Ivan Bessonov написал(а):
>
> Hello,
>
> Sorry for the delay. Sergey Chugunov (sergey.chugu...@gmail.com) just
> replied
> to the main conversa
Fixed.
> 12 июня 2020 г., в 20:10, Mauricio Stekl написал(а):
>
> Hi Nikolay,
> I just noticed that the Scaladoc API doc is missing for release 2.8.1. I am
> getting some 404 alerts for URLs like:
> https://ignite.apache.org/releases/latest/scaladoc/scalar/
>
> Could you please help deploy it b
1].
> Ducktape: basic documentation at readthedocs.io. Codebase is rigid, framework
> core is tightly coupled and hard to change. The only possible extension
> mechanism is fork-and-rewrite.
> Score: Tiden: 2, Ducktape: 1
>
> I can continue more on this, but it should be
Hello, Igniters.
I think that inside Ignite core we should name this feature as «performance
statistics»
We already have «cache statistics».
Data that is collected by performance statistics can be used not only for
profiling but to solve other tasks.
> 22 июня 2020 г., в 14:00, Nikita Amelchev
+1.
> 23 июня 2020 г., в 10:02, Artem Budnikov
> написал(а):
>
> Hello Igniters,
>
> I'd like to return to the discussion about migrating the Ignite documentation
> from readme.io to github. The idea emerged long time ago [1] but hasn't been
> implemented. I think now is the time to make it
cheev <
>>> ilya.kasnach...@gmail.com
>>>>>>> :
>>>>>>>
>>>>>>>> Hello!
>>>>>>>>
>>>>>>>> I have assigned roles on TC, you can now work on these builds.
>&g
+1 to keep docs and sources together.
-1 to keep docs in external repository.
> 23 июня 2020 г., в 16:47, Artem Budnikov
> написал(а):
>
> Pavel,
>
>> I don't think so: we can't add snippets pointing to new APIs from a separate
>> repo,
> Snippets are kept together with the docs, they /don't
Hello, Igniters.
For now, we don’t have checkstyle rule to force import order codestyle [1]
Therefore there is many violations of this rule in current codebase.
Moreover, during review, I saw many not related changes regarding import
reorder.
I’ve prepared a PR to fix this [2]
It contains:
a.
atically?
> I know Rider has this feature for C# code (team-shared settings), surely
> IDEA has it too?
>
>
> On Tue, Jun 30, 2020 at 5:39 PM Nikolay Izhikov wrote:
>
>> Hello, Igniters.
>>
>> For now, we don’t have checkstyle rule to force import order codes
e time of the test.
>
>
>> > As an additional motivation, at least 3 teams
>> - IEP-45 team (to check crash-recovery speed-up (discovery and Zabbix
>> speed-up))
>> - Ignite SE Plugins team (to check plugin's features does not slow-down or
>> br
ignite/pull/7967/files#diff-59adde2a2ab7dc17aea6c65153dfcda7R84
> [2]
> https://github.com/apache/ignite/pull/7967/files#diff-d6a7b19f30f349d426b8894a40389cf5R79
>
> On Thu, Jul 2, 2020 at 1:00 PM Nikolay Izhikov wrote:
> Hello, Maxim.
>
> > 1. tiden can deploy artifact
201 - 300 of 1145 matches
Mail list logo
