Vladimir, my comments are inline...
On Sat, May 5, 2018 at 6:12 AM, Vladimir Ozerov
wrote:
> In general I do not support this initiative. There are two serious reasons
> for that:
> 1) Our indexes are slow on updates due to architectural flaws. First, every
> index entry must be of fixed size. F
Dmitry,
Agree, mixed style when some arguments share the same line and others don't
looks very bad. My proposal was to allow two styles - first when all
arguments are on the same line splitted by 120 char limit, second when all
every arguments is on a separate line.
Mixed style should be disallowe
Hello Dmitry!
was review successfull? Or there are any points to change?
сб, 28 апр. 2018 г. в 19:32, Роман Меерсон :
> Ok! I believe in community and that things would change!
> Looking forward for news
> сб, 28 апр. 2018 г. в 19:29, Dmitry Pavlov :
>
>> I hope so!
>>
>> There was several posts
// Bcc’ed user-list and added dev-list.
2.5 scope is already frozen, and I assume this isn’t a kind of issue that would
be added at this point.
Andrey Gura, could you please comment on that?
Thanks,
Stan
From: Paul Anderson
Sent: 7 мая 2018 г. 10:33
To: u...@ignite.apache.org
Subject: Hi... ca
Igniters,
We try to maintain API compatibility and keep default behavior unchanged
between minor releases. But as product evolves, some APIs become
deprecated, new best practices appear, and some defaults are changed.
We had a talk with Andrey Gura and he suggested to add *"Migration Guide"*
to o
Hi.
I have finished this task. Just replaced
`writer.writeLongArray("arr", arr)`
with
`writer.writeLongArray("arr", arr, idx)`
Please review and merge if okay.
Jira: https://issues.apache.org/jira/browse/IGNITE-8054
PR: https://github.com/apache/ignite/pull/3748
CI:
https://ci.ignite.apache.org/
Aleksey Plekhanov created IGNITE-8443:
-
Summary: Flaky failure of
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode
Key: IGNITE-8443
URL: https://issues.apache.org/jira/browse/IGNITE-8
Dmitry,
I can also suggest to refresh on web-site "Contribute to Apache Ignite" [1]
page by the new main tickets to pickup. e.g. we have a lot of interesting
tasks with IEP-4 implementaion.
I think this will help newcomers to get one's hand in Ignite project.
Thoughts?
[1] https://ignite.apache.
Taras Ledkov created IGNITE-8444:
Summary: Authentication: add documentation about user management
SQL command and authentication feature
Key: IGNITE-8444
URL: https://issues.apache.org/jira/browse/IGNITE-8444
Hi Dima,
Update with indexes would definitely be slower than update without them.
The question is how much slower. For now the slowdown comes mostly from
excessive data page reads ([1] and [2] in my previous email) leading to
page evictions and additional IO. To the contrast, usually only a single
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3949
Ignite-1.8.20
For test purposes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.20
Alternatively you can
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3935
---
Hi Dmitriy
Could you explain what is the difference between:
- disk is a copy of the memory (only for recovery purposes)
- disk is a data storage with memory used as a performant caching layer
I assume it is all about DataRegionConfiguration.setPersistenceEnabled and
there is no other options I c
Hi Maxim,
I had similar idea to provide list of "Needed Contributions" from point of
view of community/PMCs.
Not all issues have equal pripority for product and it is easier to find
reviewer for such wanted issues, than for low priority improvement.
Sincerely,
Dmitriy Pavlov
пн, 7 мая 2018 г.
Roman Kondakov created IGNITE-8445:
--
Summary: SQL TX: Fast finish for transactions.
Key: IGNITE-8445
URL: https://issues.apache.org/jira/browse/IGNITE-8445
Project: Ignite
Issue Type: Task
Hi, just 2 remarks,
1) We should somehow separate issue with disc corruption and incorrect key.
For incorrect key I suggest to adopt Key Check Value (KCV) techique. It is
some heading bytes (e.g. 3 bytes) of encrypted 00...00 block using this
key. KCV allow us to check key decrypted correctly and
Hi Folks,
I've started mass run-all last weekend. In short - 361 tests failed, and
12 suites were unable to complete ( vs tests 309 suites 24 - 3 weeks early).
We have markable positive dynamics in fixing existing tests. Current failed
test count grow came from new ZookeeperDiscovery suites (123
Anton Vinogradov created IGNITE-8446:
Summary: Ability to check and completely fill transactions on
creation
Key: IGNITE-8446
URL: https://issues.apache.org/jira/browse/IGNITE-8446
Project: Ignite
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/3950
IGNITE-8437 Control utility fails to connect to cluster if zookeeper â¦
â¦discovery used.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Looks like a good idea to me.
But I believe, if we decide to adopt this idea, then we
need to think how to enforce adding notes to migration
guide.
The only way I can currently think of is a pretty obvious
one - adding corresponding instructions to a wiki [1].
Is there anything else we can do he
Hi Roman,
Currently I'm checking the changes. Because of applying idea to copy all
changes and upsource problem with this branch it is quite complex to locate
actual changes. It is now required to check all copied files before merge.
Sincerely,
Dmitriy Pavlov
пн, 7 мая 2018 г. в 11:07, Роман Мее
Igor,
WIKI is the way to go. In addition we are discussing ticket review
guidelines in separate thread at the moment. May be we will be able to
include Migration Guide update there as well.
On Mon, May 7, 2018 at 3:46 PM, Igor Sapego wrote:
> Looks like a good idea to me.
>
> But I believe, if
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3951
IGNITE-8422 Zookeeper discovery split-brain resolving improvement
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-
Hi, I've replied to ticket, seems old tests are now failing after applying
patch locally.
I've also added 2 suites to TC
TEST_SUITE =IgniteSpringDataTestSuite,IgniteSpringData2TestSuite
to
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpringData
so this suite will chec
Nikolay Izhikov created IGNITE-8447:
---
Summary: .Net support of DataStreamer.perThreadBufferSize
Key: IGNITE-8447
URL: https://issues.apache.org/jira/browse/IGNITE-8447
Project: Ignite
Issu
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/3952
IGNITE-8447: .Net support of DataStreamer#perThreadBufferSize
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-8447
Alt
Sergey, Dmitry,
I've targeted your issues to 2.5 release.
Thanks!
On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov wrote:
> I did not understand process.
>
> Is it required to receive someone reply that issue is agreed to be included
> into release?
>
> Or because there is no response I can cherry
Andrey,
I'm afraid this ticket should be included into 2.5 as well:
https://issues.apache.org/jira/browse/IGNITE-8429
It's similar to previous WAL compaction issue, but now it affects
decompression.
Best Regards,
Ivan Rakov
On 07.05.2018 17:09, Andrey Gura wrote:
Sergey, Dmitry,
I've targe
Hi Radhu, Monil,
Main place where Ignite docs live is https://apacheignite.readme.io/docs
More deep and specific articles targetted to Ignite developers and
committers can be found in wiki
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Home
But readme.io is best place to start.
On Mon, May 7, 2018 at 2:09 AM, Vladimir Ozerov
wrote:
> Hi Dima,
>
> Update with indexes would definitely be slower than update without them.
> The question is how much slower. For now the slowdown comes mostly from
> excessive data page reads ([1] and [2] in my previous email) leading to
> page
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/3953
Ignite 2.5.1-master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-master
Alternatively you can
Thank you, Andrey,
I saw 1 more proposal in separate topic
http://apache-ignite-developers.2346864.n4.nabble.com/RE-Hi-can-we-squeeze-this-into-2-5-https-issues-apache-org-jira-browse-IGNITE-8439-td30161.html
and 1 proposal here related to ML:
http://apache-ignite-developers.2346864.n4.nabble.com
Igniters,
This is the checklist I have at the moment. Please let me know if you have
any comments on existing items, or want to add or remove anything. It looks
like we may have not only strict rules, but *nice to have* points here as
well with help of *MUST*, *SHOULD* and *MAY* words as per RFC21
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/3954
Ignite gg 13788
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13788
Alternatively you can review and appl
Agree.
On Mon, May 7, 2018 at 5:20 PM, Dmitriy Setrakyan
wrote:
> On Mon, May 7, 2018 at 2:09 AM, Vladimir Ozerov
> wrote:
>
> > Hi Dima,
> >
> > Update with indexes would definitely be slower than update without them.
> > The question is how much slower. For now the slowdown comes mostly from
Great progress and thanks to everyone contributing! I can hardly wait for
the 0-failed-tests day. Hope it is coming some time in future :)
On Mon, May 7, 2018 at 3:38 AM, Dmitry Pavlov wrote:
> Hi Folks,
>
> I've started mass run-all last weekend. In short - 361 tests failed, and
> 12 suites we
Ivan,
ok, targeted to 2.5. Thanks!
On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov wrote:
> Thank you, Andrey,
>
> I saw 1 more proposal in separate topic
> http://apache-ignite-developers.2346864.n4.nabble.com/RE-Hi-can-we-squeeze-this-into-2-5-https-issues-apache-org-jira-browse-IGNITE-8439-td30
Dmitry, I leave comment at issue. As i may see localy problem with tests
was fixed
пн, 7 мая 2018 г. в 17:24, Dmitry Pavlov :
> Hi, I've replied to ticket, seems old tests are now failing after applying
> patch locally.
>
> I've also added 2 suites to TC
> TEST_SUITE =IgniteSpringDataTestSuite,Ig
Turik,
Apache Ignite 2.5 is in scope freeze at this moment. Only critical and
early targeted to 2.5 issue can be included to the release.
But in this case only examples are affected by your changes. So if
Yury doesn't have any objections we can include this change also.
On Mon, May 7, 2018 at 1:
Andrey,
I realized that we missed one very important thing - H2 version upgrade
[1]. This is very important thing because new version contain optimization
to IN clause processing. All we need is to upgrade H2 vesion from 1.4.196
to 1.4.197 and re-run tests. Can we target it to 2.5 release?
[1] ht
Vova,
Looks good to me.
Please add clear explanation how to check 1.4, 1.5 and 2.x.
Also, this should be published as a wiki page with refs to... eg. Coding
Guidelines.
пн, 7 мая 2018 г. в 17:26, Vladimir Ozerov :
> Igniters,
>
> This is the checklist I have at the moment. Please let me know if
All this is in our hands.
To come to 0-failed-tests day, we should have zero tolerance for new fails
today.
пн, 7 мая 2018 г. в 17:46, Dmitriy Setrakyan :
> Great progress and thanks to everyone contributing! I can hardly wait for
> the 0-failed-tests day. Hope it is coming some time in future :
Hi Jonathan,
Does Docker Swarm go with any internal services concept that can be used to
share Ignite nodes' IPs? Any other internal thing that can store and share
the IPs?
For instance, Ignite Kubernetes IP finder relies on K8 services to exchange
the IPs on the nodes startup:
https://apacheigni
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3324
---
Ilya Kasnacheev created IGNITE-8448:
---
Summary: C++: AffinityKey support
Key: IGNITE-8448
URL: https://issues.apache.org/jira/browse/IGNITE-8448
Project: Ignite
Issue Type: Task
Co
Guys,
It's planned to migrate to new documentation engine within 2.6 timeframe,
thus, I would suggest us storing migration guides in Github (together with
doc sources) and publish as a part of the docs on Ignite web site.
What do you think about this approach?
-
Denis
On Mon, May 7, 2018 at 6:2
Truly like the idea of having a separate "indexes in memory only mode"
regardless of the optimizations Vladimir keeps track of.
In my observations, some database vendors support this as the only mode
requiring to rebuild the indexes on a restart which confirms that there is
a demand for this confi
Denis,
Sounds good. Could you please share more info about new engine?
пн, 7 мая 2018 г. в 21:00, Denis Magda :
> Guys,
>
> It's planned to migrate to new documentation engine within 2.6 timeframe,
> thus, I would suggest us storing migration guides in Github (together with
> doc sources) and pu
Hi,
I don't think that this issue is critical. While change fixes the
problem I don't like manipulations in the code with host system
property. It seems that this class should be refactored.
What about do it in 2.6?
On Mon, May 7, 2018 at 11:18 AM, Stanislav Lukyanov
wrote:
> // Bcc’ed user-lis
Igniters,
There is an unpleasant bug in .NET [1]:
Services do not work at all on .NET Core and sometimes on classic .NET.
I'm almost done with the fix and I think we should include it in 2.5. Users
are complaining [2].
[1] https://issues.apache.org/jira/browse/IGNITE-8434
[2]
http://apache-igni
+1 from me to approach (co-locating migration guide and main documentation).
пн, 7 мая 2018 г. в 21:00, Denis Magda :
> Guys,
>
> It's planned to migrate to new documentation engine within 2.6 timeframe,
> thus, I would suggest us storing migration guides in Github (together with
> doc sources) a
Vladimir,
I am afraid that H2 version upgrade can affect system dramatically.
Could you please check TC first and then we'll back to the issue?
On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov wrote:
> Andrey,
>
> I realized that we missed one very important thing - H2 version upgrade [1].
> This
Pavel,
issue is targeted to release 2.5 now. Thanks!
On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn wrote:
> Igniters,
>
> There is an unpleasant bug in .NET [1]:
> Services do not work at all on .NET Core and sometimes on classic .NET.
>
> I'm almost done with the fix and I think we should inc
Is this list on the Wiki?
On Mon, May 7, 2018 at 7:26 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> This is the checklist I have at the moment. Please let me know if you have
> any comments on existing items, or want to add or remove anything. It looks
> like we may have not only strict rules, but
Dima, Denis,
Please stp wanting this! :-)
Guys, there are no in-memory indexes just to be in-memory. Let me briefly
explain what other vendors do and why. There are three approaches:
1) You may create *skip-list* based in-memory index. Goal - speedup
*READS*, not writes. Examples: MS SQL,
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/3955
IGNITE-8429 Unexpected error during incorrect WAL segment decompressiâ¦
â¦on, causes node termination
You can merge this pull request into a Git repository by running:
$ git pull https://gith
Hi Igniters,
Can someone take a look at this PR please?
Thanks,
Amir
On Mon, Apr 30, 2018 at 5:28 AM, Pavel Tupitsyn
wrote:
> Hi Amir,
>
> I have filed [1] for multimap in .NET, it will be done later.
> In order to fix IgniteParityTest failures, please add the following to
> MissingMembers arr
Hi Nikolay, Dmitry Pavlov,
Can you take a look at this PR or maybe you have an idea when it probably
can be reviewed?
Thanks,
Amir
On Wed, Apr 11, 2018 at 10:57 AM, Nikolay Izhikov
wrote:
> Hello, Amir.
>
> Sorry, but no.
>
> I will take a look in a next few days.
>
>
> В Ср, 11/04/2018 в 14:51
Sergey Kosarev created IGNITE-8449:
--
Summary: Avoid empty acquiring/releasing checkpointReadLock for
stale updates
Key: IGNITE-8449
URL: https://issues.apache.org/jira/browse/IGNITE-8449
Project: Ign
59 matches
Mail list logo