Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New Critical Failure in master Queries 1
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Queries1=%3Cdefault%3E=buildTypeStatusDiv
Changes may
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4496
---
Hi Evgeniy,
Thank you. I see that the ticket is unassigned.
Would you like to contribute PR to be macro-benchmarked with Ignite?
Sincerely,
Dmitriy Pavlov
вт, 14 авг. 2018 г. в 20:57, Евгений Станиловский
:
> I fill the ticket, bench code attached there.
>
I fill the ticket, bench code attached there.
https://issues.apache.org/jira/browse/IGNITE-9272
Thanks!
>Has anyone else run the benchmark and reproduced the performance
>difference?
>
>On Tue, Aug 14, 2018 at 8:16 AM, Dmitriy Pavlov < dpavlov@gmail.com >
>wrote:
>
>> It depends.
>>
>> CRC
Stanilovsky Evgeny created IGNITE-9272:
--
Summary: PureJavaCrc32 vs j.u.zip.CRC32 benchmark and probably
replace.
Key: IGNITE-9272
URL: https://issues.apache.org/jira/browse/IGNITE-9272
Project:
Pavel Kovalenko created IGNITE-9271:
---
Summary: Implement transaction commit using thread per partition
model
Key: IGNITE-9271
URL: https://issues.apache.org/jira/browse/IGNITE-9271
Project: Ignite
Pavel Kovalenko created IGNITE-9270:
---
Summary: Design thread per partition model
Key: IGNITE-9270
URL: https://issues.apache.org/jira/browse/IGNITE-9270
Project: Ignite
Issue Type:
Hi Igniters,
I would like to refresh review checklist a little bit. Currently it [1]
contains section against lambda Lambda expressions and Stream API. As
far as I know it is not true anymore. Currently both features have
theirs usage in core module. What is a state of affairs for a subject?
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4545
IGNITE-9093 IgniteDbPutGetWithCacheStoreTest failed occassionally dueâ¦
⦠to cache store cancel.
You can merge this pull request into a Git repository by running:
$ git pull
Alexey Goncharuk created IGNITE-9269:
Summary: Stall optimistic transactions reads if there is a
candidate for PREPARED transaction
Key: IGNITE-9269
URL: https://issues.apache.org/jira/browse/IGNITE-9269
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4544
IGNITE-9266 Cache 2 TC configuration timeouts because of hangs on latch
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4543
IGNITE-9268 Check interrupted flag during locking offheap readWriteLock
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Vitaliy Biryukov created IGNITE-9267:
Summary: Deadlock between unsuccessful client reconnecting and
stopping.
Key: IGNITE-9267
URL: https://issues.apache.org/jira/browse/IGNITE-9267
Project:
Anton Kalashnikov created IGNITE-9268:
-
Summary: Hangs on await offheap read lock
Key: IGNITE-9268
URL: https://issues.apache.org/jira/browse/IGNITE-9268
Project: Ignite
Issue Type: Test
Eduard Shangareev created IGNITE-9266:
-
Summary: Cache 2 TC configuration timeouts because of hangs on
latch
Key: IGNITE-9266
URL: https://issues.apache.org/jira/browse/IGNITE-9266
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4519
---
Igor Seliverstov created IGNITE-9265:
Summary: MVCC TX: Two rows with the same key in one MERGE
statement produce an exception
Key: IGNITE-9265
URL: https://issues.apache.org/jira/browse/IGNITE-9265
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/4542
IGNITE-9263 replace weird commit code.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9263
Alternatively you can
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4541
IGNITE-9250 Save configuration during register cache descriptor.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user SGrimstad opened a pull request:
https://github.com/apache/ignite/pull/4540
IGNITE-9256 Implemented
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-9256
Alternatively you can review and
Dmitry and other Igniters,
Previously you has suggested to commit `Code Inspections` into Ignite
codebase.
It makes sense for me. I think it's the easiest way to share this profile
among community
members and this inspection can be set as for the project level.
So, I suggest:
1) According to
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4104
---
Has anyone else run the benchmark and reproduced the performance difference?
On Tue, Aug 14, 2018 at 8:16 AM, Dmitriy Pavlov
wrote:
> It depends.
>
> CRC is a CPU-intensive operation, while WAL logging and page store write
> are mostly about IO speed.
>
> In the same time, it can make the huge
I tend to agree with Vladimir and Sergey. I would upgrade to the new H2
version and document this incompatibility with spatial indexes.
D.
On Tue, Aug 14, 2018 at 3:11 AM, Sergey Kozlov wrote:
> Vladimir
>
> The spatial module is not delivering in AI binaries (and does not provided
> in AI
Hi Dmitriy Govoruknin,
It seems there is a lack of volunteers to apply code inspections to our CI
& patch submission process. Probably we could come back to your
initial idea about setting up inspection locally.
Could you commit or share your IDEA inspection settings? I could apply it
at least
It depends.
CRC is a CPU-intensive operation, while WAL logging and page store write
are mostly about IO speed.
In the same time, it can make the huge impact on machines with fast IO and
slow CPU. So if we can apply change proposed by Evgeniy and Alexey it could
benefit performance because we
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4515
---
On Tue, Aug 14, 2018 at 6:10 AM, Nikita Amelchev
wrote:
> Hello, Igniters.
>
> I am working on task [1] that would replace serialized service's instance
> by service's class name and properties map in {ServiceConfiguration}.
>
> The task describes that we should use
> {String className} + {Map
GitHub user pvinokurov opened a pull request:
https://github.com/apache/ignite/pull/4539
IGNITE-9264 Lost partitions raised twice if node failed during exchange
You can merge this pull request into a Git repository by running:
$ git pull
Pavel Vinokurov created IGNITE-9264:
---
Summary: Lost partitions raised twice
Key: IGNITE-9264
URL: https://issues.apache.org/jira/browse/IGNITE-9264
Project: Ignite
Issue Type: Bug
Stanilovsky Evgeny created IGNITE-9263:
--
Summary: Extra batch param usage in GridCacheAdapter removeAll.
Key: IGNITE-9263
URL: https://issues.apache.org/jira/browse/IGNITE-9263
Project: Ignite
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4538
IGNITE-9171 Use lazy mode with results pre-fetch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9171
On Tue, Aug 14, 2018 at 3:34 AM, Vladimir Ozerov
wrote:
> Hi,
>
> No, we do not support ARRAY data type at the moment. Let's remove it from
> docs.
>
Vladimir, what is the reason for not supporting it? ARRAY is a basic SQL
type and not supporting it presents a serious limitation.
D.
On Tue, Aug 14, 2018 at 4:30 AM, Vladimir Ozerov
wrote:
> Bypassing WAL will make the whole cache data vulnerable to complete loss in
> case of node failure. I would not do this automatically.
>
Well, in this case I would expect a log message suggesting that there is an
option to turn off WAL
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/4537
IGNITE-8189
Improve batching deleteAll operations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite-8189
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4533
---
GitHub user SGrimstad opened a pull request:
https://github.com/apache/ignite/pull/4536
IGNITE-9141 Implemented
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9141
Alternatively you can review
Hello, Igniters.
I am working on task [1] that would replace serialized service's instance
by service's class name and properties map in {ServiceConfiguration}.
The task describes that we should use
{String className} + {Map properties} instead {Service
srvc}.
I'd like to clarify the following
Guys, what time in % does crc calculation take in WAL logging process?
--Yakov
2018-08-14 13:37 GMT+03:00 Dmitriy Pavlov :
> Hi Alex, thank you for this idea.
>
> Evgeniy, Alex, would you like to submit the patch with bypassing
> implementation differences to keep compatibility?
>
> Sincerely,
Thanks, Petr!
В Вт, 14/08/2018 в 12:10 +0300, Petr Ivanov пишет:
> JDK upgrade is finished.
> All linux agents are running on Oracle JDK 1.8.0_u181
>
>
>
> > On 10 Aug 2018, at 12:11, Petr Ivanov wrote:
> >
> > Nikolay, thanks for helping with tests.
> >
> >
> > I will proceed with Java
Hi Alex, thank you for this idea.
Evgeniy, Alex, would you like to submit the patch with bypassing
implementation differences to keep compatibility?
Sincerely,
Dmitriy Pavlov
вт, 14 авг. 2018 г. в 12:06, Alex Plehanov :
> Hello, Igniters!
>
> In java8 java.lang.zip.CRC32 methods become
Hello, Vladimir.
Thanks for a clarification.
Do we have a ticket to add support for an ARRAY data type?
Also, I think we have a bug here.
For now one can create table with ARRAY column.
Seems, we should dissalow it.
I will create a ticket to fix it.
В Вт, 14/08/2018 в 11:34 +0300, Vladimir
Bypassing WAL will make the whole cache data vulnerable to complete loss in
case of node failure. I would not do this automatically.
On Mon, Jul 16, 2018 at 12:28 PM Ilya Kasnacheev
wrote:
> Hello!
>
> Can we also bypass WAL for such mode automatically?
>
> However, we will definitely need a
Pavel,
Agree. Looks like we should leave our compatibility policy as is and do not
limit it to several adjacent versions.
On Thu, Jun 7, 2018 at 12:35 PM Pavel Tupitsyn wrote:
> Vladimir,
>
> Not sure I see the point of 2 release policy.
> It is not very good both for users and developers.
>
>
JDK upgrade is finished.
All linux agents are running on Oracle JDK 1.8.0_u181
> On 10 Aug 2018, at 12:11, Petr Ivanov wrote:
>
> Nikolay, thanks for helping with tests.
>
>
> I will proceed with Java updates. Will notify when finished.
>
>
>
>
>> On 10 Aug 2018, at 11:37, Nikolay
Hello, Igniters!
In java8 java.lang.zip.CRC32 methods become intrinsic, moreover new
"update" method, which use ByteBuffer was introduced. Since we moved to
java8, perhaps we really can get performance boost by using standard
java.lang.zip.CRC32 instead of PureJavaCrc32.
About compatibility:
GitHub user 1vanan opened a pull request:
https://github.com/apache/ignite/pull/4535
IGNITE-8919 Wrong documentation of exec methods in StartNodeCallableImpl
class
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1vanan/ignite
Hi,
No, we do not support ARRAY data type at the moment. Let's remove it from
docs.
On Mon, Aug 13, 2018 at 10:06 PM Denis Magda wrote:
> Vladimir,
>
> Could you step in? How should we update our docs and what are the steps to
> add Arrays support to the project? I thought this worked all the
Vasiliy Sisko created IGNITE-9262:
-
Summary: Web console: missed generation of query entities for
imported domain modelss
Key: IGNITE-9262
URL: https://issues.apache.org/jira/browse/IGNITE-9262
Vladimir
The spatial module is not delivering in AI binaries (and does not provided
in AI maven repo). This the impact will be less than if it happended for
other modules.
On Tue, Aug 14, 2018 at 10:46 AM, Vladimir Ozerov
wrote:
> Dmitriy,
>
> Spatial indexes is one of our features, packed
Dmitriy,
Spatial indexes is one of our features, packed as separate optional module
[1]. With proposed changes users of this feature will not be able to
migrate to 2.7 until they rewrite and recompile their code, because both
compile-time and run-time compatibility will be broken. Required
51 matches
Mail list logo
