GitHub user udaykale opened a pull request:
https://github.com/apache/ignite/pull/4577
IGNITE-8251 Reduce testPageEviction run time
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/udaykale/ignite IGNITE-8251
Alternatively you ca
Alexei Scherbakov created IGNITE-9319:
-
Summary:
CacheAsyncOperationsFailoverTxTest.testPutAllAsyncFailover is flaky in master.
Key: IGNITE-9319
URL: https://issues.apache.org/jira/browse/IGNITE-9319
Hello everyone.
Looks like I found cause of problem. It is
https://issues.apache.org/jira/browse/IGNITE-8926.
Ilya Lantukh could you please recheck your changes. You can easily reproduce
problem locally by IgniteCacheFailedUpdateResponseTest#testInvokeAtomic.
I also rerun all tests on your b
Igniters,
I have found "Known issue, possible deadlock in case of low priority cache
rebalancing delayed" comment in
GridCacheRebalancingSyncSelfTest#getConfiguration.Can you please explain when
using rebalance delay can be an issue and why?
-- Roman
Vladimir Ozerov created IGNITE-9320:
---
Summary: MVCC: finalize configuration
Key: IGNITE-9320
URL: https://issues.apache.org/jira/browse/IGNITE-9320
Project: Ignite
Issue Type: Task
Hi Dmitriy,
I agree with you about lambdas. For me they are quite useful and I believe
that this language feature is a solid and well proven part of modern Java.
I still feel that current statement in our guidelines should be rephrased.
But if others are ok with it then let's keep it as is.
2018
Vladimir Ozerov created IGNITE-9321:
---
Summary: MVCC: support cache events
Key: IGNITE-9321
URL: https://issues.apache.org/jira/browse/IGNITE-9321
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-9322:
---
Summary: MVCC: implement deadlock detector
Key: IGNITE-9322
URL: https://issues.apache.org/jira/browse/IGNITE-9322
Project: Ignite
Issue Type: Task
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4569
---
Igniters,
While reviewing the changes for IGNITE-9228 [1,2], Nikolay and I are
discussing whether to introduce a change which may impact backwards
compatibility; Nikolay suggested we take the discussion to this list.
Ignite implements a custom Spark catalog which provides an API by which
Spark us
Vladimir Ozerov created IGNITE-9323:
---
Summary: MVCC: support cache interceptors
Key: IGNITE-9323
URL: https://issues.apache.org/jira/browse/IGNITE-9323
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-9324:
---
Summary: MVCC: support explicit locks
Key: IGNITE-9324
URL: https://issues.apache.org/jira/browse/IGNITE-9324
Project: Ignite
Issue Type: Task
Denis,
Currently we provide md5 and sha512 [1].
Should we just get rid of md5?
[1] https://www.apache.org/dist/ignite/2.6.0/
сб, 18 авг. 2018 г. в 3:51, Denis Magda :
> Peter, Anton V, Igniters,
>
> The board communicated the following release policy changes:
> -- for new releases :
> --
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/4578
IGNITE-9188 Unexpected eviction leading to data loss
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9188
A
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4573
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4571
---
Hi,
I have checked the benchmark and it shows great performance boost on my
laptop!
+1 for this change.
On Tue, Aug 14, 2018 at 9:01 PM Dmitriy Pavlov
wrote:
> Hi Evgeniy,
>
> Thank you. I see that the ticket is unassigned.
>
> Would you like to contribute PR to be macro-benchmarked with Ignit
ARomantsov created IGNITE-9325:
--
Summary: Add to all command-line utility ability to make sound
after complite execution
Key: IGNITE-9325
URL: https://issues.apache.org/jira/browse/IGNITE-9325
Project: I
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4563
---
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
On Sun, Aug 19, 2018 at 12:30 PM Vyacheslav Daradur
wrote:
> Hi, Igniters!
>
> I found that TC build plan n
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4560
---
Oh, you are talking of Java 8 suite.
There is an issue with configuration of the suite.
Peter currently working on it.
Best Regards,
Igor
On Mon, Aug 20, 2018 at 2:42 PM Igor Sapego wrote:
> Yeah, I know.
>
> There is no 32-bit JDK for Java 9 on Windows.
>
> So, I guess, we have no other choi
Alexey Goncharuk created IGNITE-9326:
Summary: IgniteCacheFailedUpdateResponseTest hangs in master
Key: IGNITE-9326
URL: https://issues.apache.org/jira/browse/IGNITE-9326
Project: Ignite
Thank you!
On Mon, Aug 20, 2018 at 2:53 PM Igor Sapego wrote:
>
> Oh, you are talking of Java 8 suite.
>
> There is an issue with configuration of the suite.
> Peter currently working on it.
>
> Best Regards,
> Igor
>
>
> On Mon, Aug 20, 2018 at 2:42 PM Igor Sapego wrote:
>>
>> Yeah, I know.
>>
>
Hello, Stuart.
Personally, I think we should change current tables naming and return table in
form of `schema.table`.
Valentin, could you share your opinion?
В Пн, 20/08/2018 в 10:04 +0100, Stuart Macdonald пишет:
> Igniters,
>
> While reviewing the changes for IGNITE-9228 [1,2], Nikolay and
Anton Kalashnikov created IGNITE-9327:
-
Summary: Client Nodes hangs because client reconnect not handled
Key: IGNITE-9327
URL: https://issues.apache.org/jira/browse/IGNITE-9327
Project: Ignite
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4579
IGNITE-9327 stop the node if IgniteNeedReconnectException happened
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignit
Ilya Kasnacheev created IGNITE-9328:
---
Summary: IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to
write.
Key: IGNITE-9328
URL: https://issues.apache.org/jira/browse/IGNITE-9328
Project: Ignite
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/4580
Need to change merge metadata behavior during new schema registration.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ign
Ilya Kasnacheev created IGNITE-9329:
---
Summary: Positive and negative tests for SSL ciphers and protocols
Key: IGNITE-9329
URL: https://issues.apache.org/jira/browse/IGNITE-9329
Project: Ignite
Ilya Kasnacheev created IGNITE-9330:
---
Summary: Multiple CacheMetricsManageTest tests are failing
Key: IGNITE-9330
URL: https://issues.apache.org/jira/browse/IGNITE-9330
Project: Ignite
Issu
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4582
Ignite 6167
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6167
Alternatively you can review and apply these cha
Yes, let’s just remove md5. Will you create the ticket and handle this for
2.7?
Denis
On Monday, August 20, 2018, Anton Vinogradov wrote:
> Denis,
>
> Currently we provide md5 and sha512 [1].
> Should we just get rid of md5?
>
> [1] https://www.apache.org/dist/ignite/2.6.0/
>
> сб, 18 авг. 2018
Stanislav Lukyanov created IGNITE-9331:
--
Summary: Add thin client tests for custom TLS protocols
Key: IGNITE-9331
URL: https://issues.apache.org/jira/browse/IGNITE-9331
Project: Ignite
I
As for now, metrics are accumulated for cache only when the query is run
directly over this cache, for example, using ignite.cache("Some
cache").sqlFieldsQuery("select ... from .."). When a query is started using
other APIs, it doesn't detect cache, to which this table belongs and
doesn't save any
Eduard Shangareev created IGNITE-9332:
-
Summary: [TC Helper] Add statistic page
Key: IGNITE-9332
URL: https://issues.apache.org/jira/browse/IGNITE-9332
Project: Ignite
Issue Type: Task
Hello Roman,
Did you faced with real issue of delayed rebalance or it's just only for
your personal interest?
If yes, please, share details and we will try to help you.
As for this comment I don't think he is actual. That change was in 2015.
Much has changed
within rebalance process since that ti
Eduard Shangareev created IGNITE-9333:
-
Summary: Adding page with simple statistic for last 50 runs.
Key: IGNITE-9333
URL: https://issues.apache.org/jira/browse/IGNITE-9333
Project: Ignite
Ilya Kasnacheev created IGNITE-9334:
---
Summary: Web Console should set sqlEscapeAll in generated sources
when needed
Key: IGNITE-9334
URL: https://issues.apache.org/jira/browse/IGNITE-9334
Project: I
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/4583
IGNITE-8829
TcpCommunicationSpi: fix configuration properties
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite-8829
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4568
---
Ilya Kasnacheev created IGNITE-9335:
---
Summary:
IgniteOffheapReadWriteLockSelfTest.testTagIdUpdateContinuous() sometimes hangs
on a barrier
Key: IGNITE-9335
URL: https://issues.apache.org/jira/browse/IGNITE-9335
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4567
---
Hello, Igniters.
I'm release manager of Apache Ignite 2.7.
It's time to start discussion of release. [1]
Current code freeze date is September, 30.
If you have any objections - please, responsd to this thread.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
signature.a
Hi Nikolay,
Thanks for being the release manager!
I am getting a bit lost in all these tickets. Can we specify some
high-level tickets, that are not plain bug fixes, which will be interesting
for the community to notice?
For example, here are some significant tasks that the community is either
w
Hi Evgeny,
Do you propose to move into IgniteMetrics absolutely all Ignite metrics or
just dataRegionMetrics, dataStorageMetrics and queryDetailMetrics? I think
you can't move all metrics into one place. Pluggable components and
different SPI implementations may have their own metric sets, and per
I commented in the ticket: https://issues.apache.org/jira/browse/IGNITE-9272
It if can integrate it correctly, according to my comment, in 2.7 release,
it would be great. Otherwise, let's plan this change for 3.0 release.
D.
On Mon, Aug 20, 2018 at 3:50 AM, Eduard Shangareev <
eduard.shangar...@
Hi Igniters
I suppose that'll break compatibility for LFS (PDS).
Do we plan to provide a migration guide w/o data loss for upgrade AI 2.x to
3.0?
On Mon, Aug 20, 2018 at 11:46 PM, Dmitriy Setrakyan
wrote:
> I commented in the ticket: https://issues.apache.org/
> jira/browse/IGNITE-9272
>
> It
Sergey, that was precisely my comment in the ticket:
Can we add this option without breaking compatibility with previous
page/storage formats? If not, then this should support both implementation.
The default should be the new fastest implementation, but if we encounter
the older, slower one, then
Igniters,
let's come back to the idea from Alex Plehanov.
We can try to provide custom xor mask at the end of CRC calc. We can do a
compatible solution using fast implementation, can't we?
Sincerely,
Dmitriy Pavlov
вт, 21 авг. 2018 г. в 0:04, Dmitriy Setrakyan :
> Sergey, that was precisely my
Dmitriy
Due to significant improvement and to reduce the number supported
modes/options would be good to convert the data at the moment of upgrade.
On Tue, Aug 21, 2018 at 12:03 AM, Dmitriy Setrakyan
wrote:
> Sergey, that was precisely my comment in the ticket:
>
> Can we add this option withou
Stuart, Nikolay,
I see that the 'Table' class (returned by listTables method) has a
'database' field. Can we use this one to report schema name?
In any case, I think we should look into how this is done in data source
implementations for other databases. Any relational database has a notion
of sc
Github user mulugetam closed the pull request at:
https://github.com/apache/ignite/pull/4381
---
GitHub user mulugetam reopened a pull request:
https://github.com/apache/ignite/pull/4381
Adding experimental support for Intel Optane DC Persistent Memory
Ignite, when persistence mode is enabled, stores data and indexes on disk.
To minimize the latency of disks, several tuning opt
Hi Maxim,
I have some issues with a cluster with rebalance delay enabled, but need to
check more -- if I find it's related I'll share.Just wanted to make sure it's
not an issue anymore from someone working on rebalancing. We should remove that
comment then, it looks scary :)
--
Roman Shtykh
Hey, ML experts,
Here is an ML issue reported. Please have a look.
--
Denis
-- Forwarded message -
From: DocDVZ
Date: Mon, Aug 20, 2018 at 10:53 AM
Subject: NPE exception in KMeansTrainer
To:
Hello,
Since I'm new to data science, I'm not really sure if it's a bug or wrong
in
Thank you, I think I've found this bug (or related to this) here
https://issues.apache.org/jira/browse/IGNITE-9239
It will be delivered in 2.7 (Currently it's in master branch).
To be sure 100% that the bug is closed, could @DocDVZ provide an approach
of cache populating?
I mean this cache
Ignit
57 matches
Mail list logo
