Andrey Novikov created IGNITE-5788:
--
Summary: Web Console: Missed c3p0 dependencies in generated maven
project
Key: IGNITE-5788
URL: https://issues.apache.org/jira/browse/IGNITE-5788
Project: Ignite
Evgenii Zhuravlev created IGNITE-5789:
-
Summary: After client reconnects to server if server was
restarted, client doesn't create caches defined in config file
Key: IGNITE-5789
URL: https://issues.apache.org/j
Rerun tests in "Run All" Ignite 2.0 group after merge with the latest
master -
http://ci.ignite.apache.org/viewLog.html?buildId=734705&tab=queuedBuildOverviewTab
- Do you see any issues with them? (Unfortunately I have too little
experience with Ignite tests to judge.)
On 7/19/2017 6:25 PM,
Mikhail Cherkasov created IGNITE-5790:
-
Summary: Xml config can not be used in jdbs and user code
simultaneously
Key: IGNITE-5790
URL: https://issues.apache.org/jira/browse/IGNITE-5790
Project: Ig
-1 (according to found issues).
On Wed, Jul 19, 2017 at 6:06 PM, Vyacheslav Daradur
wrote:
> I've investigated the issue.
> There are different branches with the tag: "2.1.0-rc2"
> *ignite-2.1* - last commit by 'devozerov'
> (355ffda1e8aa88fd904d037995c061380aa1b74d)
> *2.1.0-rc2* - last commit
Semen,
What about attribute *rebalanceMode*? From
*ClusterCachesInfo::validateCacheGroupConfiguration* I see that consistency
of the attribute is treated as critical and node even fails to start if
different caches in the same group have different rebalanceMode setting.
I've already implemented a
Let's treat consistency of rebalanceMode as critical (this really can cause
problems if one node has rebalanceMode NONE and other SYNC or ASYNC).
Thanks
On Thu, Jul 20, 2017 at 12:46 PM, Sergey Chugunov wrote:
> Semen,
>
> What about attribute *rebalanceMode*? From
> *ClusterCachesInfo::validat
Yury Babak created IGNITE-5791:
--
Summary: Block matrix Introduction
Key: IGNITE-5791
URL: https://issues.apache.org/jira/browse/IGNITE-5791
Project: Ignite
Issue Type: Sub-task
Compone
Okay, I'll modify my code and let you know when everything will be ready
for review.
On Thu, Jul 20, 2017 at 12:52 PM, Semyon Boikov
wrote:
> Let's treat consistency of rebalanceMode as critical (this really can cause
> problems if one node has rebalanceMode NONE and other SYNC or ASYNC).
>
> Th
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2319
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2317
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Officially cancelling the vote according to found assembly issues.
This vote is closed.
On Thu, Jul 20, 2017 at 12:35 PM, Anton Vinogradov wrote:
> -1 (according to found issues).
>
>
> On Wed, Jul 19, 2017 at 6:06 PM, Vyacheslav Daradur
> wrote:
>
>> I've investigated the issue.
>> There are different branches with the tag: "2.1.0-rc2"
>> *ignite-2.1* - last
First solution is bad idea because client could be closed by driver while
user code still uses this client.
17 июля 2017 г. 12:49 PM пользователь "Vladimir Ozerov" <
voze...@gridgain.com> написал:
> I would say this is a usability issue, please file a ticket. But why one
> need to use JDBC when
Semen, I examined code and found out that such check already exists: node
cannot join cluster if it has rebalanceMode setting inconsistent with other
nodes in the cluster.
I also found a test for it, it is called
*GridCacheConfigurationValidationSelfTest*.
No changes to my code are needed, so ple
GitHub user avinogradovgg opened a pull request:
https://github.com/apache/ignite/pull/2324
Caches 1.6 hack
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/x-kreator/ignite caches-1.6-hack
Alternatively you can review and apply
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/2325
ignite-4181
IGNITE-4181 challenge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/x-kreator/ignite ignite-4181
Alternatively you can review a
Sergey Chugunov created IGNITE-5792:
---
Summary:
IgnitePdsAtomicCacheRebalancingTest.testRebalancingOnRestartAfterCheckpoint is
failing on TC
Key: IGNITE-5792
URL: https://issues.apache.org/jira/browse/IGNITE-579
GitHub user ybabak opened a pull request:
https://github.com/apache/ignite/pull/2326
Ignite-5791: Block matrix introduction
- Implemented new block matrix with effective matrix multiplication.
- Added some missing package-info.
You can merge this pull request into a Git reposito
Ivan Rakov created IGNITE-5793:
--
Summary: Cache with constant time TTL for entries and enabled
persistence hangs for a long time when TTL expirations start
Key: IGNITE-5793
URL: https://issues.apache.org/jira/browse/
GitHub user asfedotov opened a pull request:
https://github.com/apache/ignite/pull/2327
ignite-1.8.8.b2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.8.b2
Alternatively you can review and appl
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/2328
Ignite 5792
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5792
Alternatively you can review and a
Ilya Lantukh created IGNITE-5794:
Summary: BinaryMetadata is lost if all server nodes have been
restarted
Key: IGNITE-5794
URL: https://issues.apache.org/jira/browse/IGNITE-5794
Project: Ignite
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2329
IGNITE-5741
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5741
Alternatively you can review and apply these c
Hi Evgeniy,
I've checked the results. All of failures are flaky tests, failed with
issue link or were failed somewhere else.
Sincerely,
Dmitriy Pavlov
чт, 20 июл. 2017 г. в 11:48, Evgeniy Ignatiev :
> Rerun tests in "Run All" Ignite 2.0 group after merge with the latest
> master -
>
> http://ci
Hi Nick,
Thank you for your comment. Was onIgniteStart called after onKernalStart in
1.9? Or caches were available, but other of initialization was the same?
Sincerely.
Dmitriy Pavlov
ср, 19 июл. 2017 г. в 17:06, Nick Pordash :
> Hi Dmitriy,
>
> The ticket was a regression from 1.9 to 2.0. I do
Dmitry Karachentsev created IGNITE-5795:
---
Summary: @AffinityKeyMapped ignored if QueryEntity used
Key: IGNITE-5795
URL: https://issues.apache.org/jira/browse/IGNITE-5795
Project: Ignite
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/2330
IGNITE-5795 IgniteIGNITE-5795 @AffinityKeyMapped ignored if
QueryEntity used
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridga
onIgniteStart was called in Ignite 1.X in
GridPluginComponent#onKernalStart as one of the calls to the component
callbacks, probably the order in which components were called, ensured
that contract of PluginProvider#onIgniteStart was not violated. But in
2.0 the GridPluginComponent instances ar
Hi, guys. I have written benchmarks for comparing IgniteCache.lock() and
Ignite.reentrantLock() and they merged to master branch.
If someone new wants to make benchmarks look at the implementation. Don't
forget to write both JMH and Yardstick benchmarks.
In process of writing, I have found out th
Hi Evgeniy,
Thank you for such a careful research of the issue.
If don’t mind, I would like to do additional tests with this PR changes.
I will come back with result in couple of days
Sincerely,
Dmitriy Pavlov
чт, 20 июл. 2017 г. в 19:18, Evgeniy Ignatiev :
> onIgniteStart was called in Ignit
Guys, I've finished my first issue (IGNITE-5452).
It contained 2 issues:
1. GridTimeoutProcessor can't be stopped if TimeoutObject eats
InterruptedException. We should handle this correctly.
2. TX use TimeoutObjects to be rolled back by timeout. However, TXs doesn't
remove their TimeoutObjects
Hi Igniters,
We all know that there are a lot of open tasks in Ignite project. To be
able to handle all these tasks, we need to grow our community. And to
achieve that, we should pay special attention to new community members.
As recent newcomer I’ve faced the following problem: There is no way t
Dmitriy, I can do it. But as far as I know Oleg Ignatenko already wrote blog
about Ignite ML. But it only about AI 2.0 and only on Russian(Habrahabr). So
we could translate this post in English.
And also I can write a blog about new features ML in AI 2.1 and mentioned
features which we plan for 2.
Sounds good.
On Jul 20, 2017, 1:56 PM, at 1:56 PM, Yury Babak wrote:
>Dmitriy, I can do it. But as far as I know Oleg Ignatenko already wrote
>blog
>about Ignite ML. But it only about AI 2.0 and only on
>Russian(Habrahabr). So
>we could translate this post in English.
>
>And also I can write a bl
Hi Igniters,
I am working on the ticket
https://issues.apache.org/jira/browse/IGNITE-5648, which purpose is to
add support for NOT NULL constraint for any fields of key or value
stored in Ignite cache.
I would appreciate your comments on the design approach I have described below.
In my opinion,
Alexander,
Sounds like a useful addition, thanks! Does it make sense to document the usage
and specificities you are mentioning on an Ignite wiki page?
—
Denis
> On Jul 20, 2017, at 9:59 AM, Александр Меньшиков wrote:
>
> Hi, guys. I have written benchmarks for comparing IgniteCache.lock() an
Hi Sergey,
That will be an excellent addition to DDL features set.
The proposed changes look good to from the public API standpoint.
Alexander P., Sergi, Vovan, please share your thoughts.
—
Denis
> On Jul 20, 2017, at 12:27 PM, Sergey Kalashnikov
> wrote:
>
> Hi Igniters,
>
> I am workin
Congrats! Keep the pace ;)
—
Denis
> On Jul 20, 2017, at 10:28 AM, Vitaliy Biryukov
> wrote:
>
> Guys, I've finished my first issue (IGNITE-5452).
>
>
> It contained 2 issues:
>
> 1. GridTimeoutProcessor can't be stopped if TimeoutObject eats
> InterruptedException. We should handle this co
Igniters, there is a new video by technical evangelist Akmal B. Chaudhri
explaining Apache® Ignite™ architecture's ACID-compliant transactional
subsystem. http://bit.ly/2uf485B
After watching his recorded webinar, you'll have a better understanding of
why companies in many industries, including la
I think the right question to ask is why do we have RED tests to begin
with. In my view, TC should be green. If there are tests that do not pass,
we should disable them and file blocker tickets for the next releases.
D.
On Thu, Jul 20, 2017 at 1:20 PM, Dmitry Pavlov
wrote:
> Hi Igniters,
>
> We
+1 to Dmitry Pavlov from me.
Green team city would be very helpful.
> If you are a newcomer, please share your feeling: are you confused by
test
> failures on Teamcity?
I'm working on my very first ignite issue
and it's not easy to understand TC build results.
21.07.2017 00:30, Dmitriy Set
Igniters,
Setting off the vote one more time. Hope I’ll be successful this time, keeping
fingers crossed :)
We have uploaded a 2.1.0 release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/
Git tag name is
2.1.0-rc3
This release includes the following changes:
Ignite:
* P
Valentin Kulichenko created IGNITE-5796:
---
Summary: Improve cache memory metrics
Key: IGNITE-5796
URL: https://issues.apache.org/jira/browse/IGNITE-5796
Project: Ignite
Issue Type: Impro
+1
2017-07-21 5:34 GMT+07:00 Denis Magda :
> Igniters,
>
> Setting off the vote one more time. Hope I’ll be successful this time,
> keeping fingers crossed :)
>
> We have uploaded a 2.1.0 release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/
>
> Git tag name is
> 2.1.0-r
+1 (binding)
On Thu, Jul 20, 2017 at 9:35 PM, Sasha Belyak wrote:
> +1
>
> 2017-07-21 5:34 GMT+07:00 Denis Magda :
>
> > Igniters,
> >
> > Setting off the vote one more time. Hope I’ll be successful this time,
> > keeping fingers crossed :)
> >
> > We have uploaded a 2.1.0 release candidate to
>
Github user Desperus closed the pull request at:
https://github.com/apache/ignite/pull/2321
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
47 matches
Mail list logo
