Alexander Paschenko created IGNITE-5482:
---
Summary: Implement basic caching of query results
Key: IGNITE-5482
URL: https://issues.apache.org/jira/browse/IGNITE-5482
Project: Ignite
Issue
On Tue, Jun 13, 2017 at 5:06 PM, Denis Magda wrote:
> e.getCause() might return ‘null’ and you’ll get NullPointerException
> trying to execute e.getCause().getCause().
>
> Ideally, we need to throw TransactionDeadlockException like it’s done in
> .NET.
>
Agree, looks odd, but because of JSR107 w
Alexey Kuznetsov created IGNITE-5481:
Summary: Refactor VisorCache to detect rebalance in progress
Key: IGNITE-5481
URL: https://issues.apache.org/jira/browse/IGNITE-5481
Project: Ignite
e.getCause() might return ‘null’ and you’ll get NullPointerException trying to
execute e.getCause().getCause().
Ideally, we need to throw TransactionDeadlockException like it’s done in .NET.
—
Denis
> On Jun 13, 2017, at 4:43 PM, Dmitriy Setrakyan wrote:
>
> This looks a bit confusing. Why is
This looks a bit confusing. Why is it not enough to have this check:
e.getCause().getCause() instanceof TransactionDeadlockException
?
On Tue, Jun 13, 2017 at 4:40 PM, Denis Magda wrote:
> Pardon me, copy pasted the catch block twice. This how the block looked
> like in Ignite 1.x
>
> catch (C
Pardon me, copy pasted the catch block twice. This how the block looked like in
Ignite 1.x
catch (CacheException e) {
if (e.getCause() instanceof TransactionTimeoutException &&
e.getCause().getCause() instanceof TransactionDeadlockException)
System.out.println(e.g
Andrey Gura, Igniters,
If to refer to our documentation [1], this is how we need to catch the deadlock
detection exception:
catch (CacheException e) {
if (e.getCause() instanceof IgniteCheckedException &&
e.getCause().getCause() instanceof TransactionDeadlockException)
And just to be completely clear: are you referring to OpenStack Swift?
Please pardon my ignorance, but I though Swift is a storage "solution"
rather than a distributed file system. Are you referring to Ceph by
any chance?
I guess I am just confused a little bit and would appreciate if you
can clar
On Tue, Jun 13, 2017 at 11:53 AM, Denis Magda wrote:
> It’s not intended to be a public event but rather a meeting of Ignite’s
> committers and contributors to discuss the store. This is why I personally
> prefer not going out of the dev list boundaries.
>
If you post on the website, with instru
It’s not intended to be a public event but rather a meeting of Ignite’s
committers and contributors to discuss the store. This is why I personally
prefer not going out of the dev list boundaries.
—
Denis
> On Jun 13, 2017, at 11:36 AM, Dmitriy Setrakyan wrote:
>
> Denis, any chance you can po
Denis, any chance you can post info for this webinar on the website?
On Tue, Jun 13, 2017 at 10:05 AM, Denis Magda wrote:
> Roman,
>
> Sure, will do.
>
> —
> Denis
>
> > On Jun 12, 2017, at 8:35 PM, Roman Shtykh
> wrote:
> >
> > Denis,
> > Can you please share slides (or video) after the webina
Roman,
Sure, will do.
—
Denis
> On Jun 12, 2017, at 8:35 PM, Roman Shtykh wrote:
>
> Denis,
> Can you please share slides (or video) after the webinar? I would like to
> attend it but it's midnight in Japan.
> -- Roman
>
>
>
>On Tuesday, June 13, 2017 7:56 AM, Denis Magda wrote:
>
>
Folks,
The webinar is scheduled for Friday, June 16th, 8.00-9.00 AM Pacific Time. I’m
going to use Go To Meeting tool for the call. Please install it prior joining.
All of those who replied with +1 in the discussion received an invitation. Just
in case, below are the details for the rest.
Dmitriy Govorukhin created IGNITE-5480:
--
Summary: Need to correctly handle deactivation process if an
exception occured during deactivation
Key: IGNITE-5480
URL: https://issues.apache.org/jira/browse/IGNITE-5
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/2124
---
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 en
Hi Vyacheslav,
"Broken tests" suite was an experimental place for grouping all failing and
flaky tests in one suite.
Related code changes were not merged into master.
Best Regards,
Dmitriy Pavlov
чт, 8 июн. 2017 г. в 16:56, Vyacheslav Daradur :
> Vladimir, thank you for answers. 1-2 questions w
Hi Vladimir
Yes. That's what I meant.
Thanks.
Antonio.
Sent from my iPhone
> On Jun 12, 2017, at 11:51 PM, Vladimir Ozerov wrote:
>
> Hi Antonio,
>
> Please clarify what file system do you mean? Is it secondary file system
> for IGFS?
>
> Vladimir.
>
>> On Tue, Jun 13, 2017 at 8:14 AM, An
Pavel Tupitsyn created IGNITE-5479:
--
Summary: PersistentStoreConfiguration improvements
Key: IGNITE-5479
URL: https://issues.apache.org/jira/browse/IGNITE-5479
Project: Ignite
Issue Type: Im
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2124
IGNITE-5478: ODBC: SQLNumParams now returns number of reqiured parameters.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-igni
+1
2017-06-13 15:31 GMT+03:00 vadopolski :
> + 1
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/DISCUSS-Webinar-for-
> Ignite-Persistent-Store-walk-through-tp18677p18767.html
> Sent from the Apache Ignite Developers mailing list archive at Nabb
GitHub user artemmalykh opened a pull request:
https://github.com/apache/ignite/pull/2123
IGNITE-5278: First stage of BLAS (Local onheap structures) implemented.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ign
Github user DmitriyGovorukhin closed the pull request at:
https://github.com/apache/ignite/pull/2119
---
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 fea
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2104
---
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 tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/2122
IGNITE-5462 JDBC thin driver: add complex DDL+DML test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-
Igor Sapego created IGNITE-5478:
---
Summary: ODBC: SQLNumParams works incorrectly
Key: IGNITE-5478
URL: https://issues.apache.org/jira/browse/IGNITE-5478
Project: Ignite
Issue Type: Bug
+ 1
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Webinar-for-Ignite-Persistent-Store-walk-through-tp18677p18767.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Vyacheslav Daradur created IGNITE-5477:
--
Summary: Java: BinaryMarshaller should write ints in "varint"
encoding where it makes sense
Key: IGNITE-5477
URL: https://issues.apache.org/jira/browse/IGNITE-5477
plus one
вт, 13 июн. 2017 г. в 14:26, Anton Vinogradov :
> +1
>
> On Tue, Jun 13, 2017 at 2:21 PM, Kozlov Maxim
> wrote:
>
> > +1
> >
> > > 13 июня 2017 г., в 14:14, Vyacheslav Daradur
> > написал(а):
> > >
> > > +1 (I will attend)
> > >
> > > 2017-06-13 6:35 GMT+03:00 Roman Shtykh :
> > >
> >
+1
On Tue, Jun 13, 2017 at 2:21 PM, Kozlov Maxim wrote:
> +1
>
> > 13 июня 2017 г., в 14:14, Vyacheslav Daradur
> написал(а):
> >
> > +1 (I will attend)
> >
> > 2017-06-13 6:35 GMT+03:00 Roman Shtykh :
> >
> >> Denis,
> >> Can you please share slides (or video) after the webinar? I would like
>
+1
> 13 июня 2017 г., в 14:14, Vyacheslav Daradur написал(а):
>
> +1 (I will attend)
>
> 2017-06-13 6:35 GMT+03:00 Roman Shtykh :
>
>> Denis,
>> Can you please share slides (or video) after the webinar? I would like to
>> attend it but it's midnight in Japan.
>> -- Roman
>>
>>
>>
>>On T
+1 (I will attend)
2017-06-13 6:35 GMT+03:00 Roman Shtykh :
> Denis,
> Can you please share slides (or video) after the webinar? I would like to
> attend it but it's midnight in Japan.
> -- Roman
>
>
>
> On Tuesday, June 13, 2017 7:56 AM, Denis Magda
> wrote:
>
>
> Good, we have a quorum th
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/2121
IGNITE-1583: fix test, removeNode partition id update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1583
Alterna
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/2120
Ignite 2.1.1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.1
Alternatively you can review and ap
Hi, I'll have a look and reply in JIRA.
On Tue, Jun 13, 2017 at 10:34 AM, Guru Stron
wrote:
> Hi guys,
>
> Can anyone please review?
>
> Pull request:
> https://github.com/apache/ignite/pull/2118
>
> Also i've scheduled some build jobs:
>
> http://ci.ignite.apache.org/viewQueued.html?itemId=6592
Ilya Borisov created IGNITE-5476:
Summary: Web Console: backend API updates for basic configuration
Key: IGNITE-5476
URL: https://issues.apache.org/jira/browse/IGNITE-5476
Project: Ignite
Iss
Github user mcherkasov closed the pull request at:
https://github.com/apache/ignite/pull/2117
---
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
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/2119
Ignite 5267 merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5267-merge
Alternatively you can rev
+1
On Tue, Jun 13, 2017 at 1:13 AM, Yakov Zhdanov wrote:
> Sam,
>
> Absolutely agree. Good catch!
>
> --Yakov
>
Andrew Mashenkov created IGNITE-5475:
Summary: SQL: add "WITH AS" support
Key: IGNITE-5475
URL: https://issues.apache.org/jira/browse/IGNITE-5475
Project: Ignite
Issue Type: Bug
Andrey Novikov created IGNITE-5474:
--
Summary: Simplify usage of VisorComputeCancelSessionsTask
Key: IGNITE-5474
URL: https://issues.apache.org/jira/browse/IGNITE-5474
Project: Ignite
Issue T
Sam,
Absolutely agree. Good catch!
--Yakov
Makes absolute sense to me. It should be possible to have both persistent
and non-persistent caches.
On Tue, Jun 13, 2017 at 11:06 AM, Semyon Boikov
wrote:
> Hi guys,
>
> As I understand, currently by design, if I set
> IgniteConfiguration.persistentStoreConfiguration then persistence is
> autom
Hi guys,
As I understand, currently by design, if I set
IgniteConfiguration.persistentStoreConfiguration then persistence is
automatically enabled for ALL caches. Don't you think it can be useful to
have possibility to configure persistence per cache?
Thanks!
Alexey Goncharuk created IGNITE-5473:
Summary: Create ignite troubleshooting logger
Key: IGNITE-5473
URL: https://issues.apache.org/jira/browse/IGNITE-5473
Project: Ignite
Issue Type: Imp
Hi guys,
Can anyone please review?
Pull request:
https://github.com/apache/ignite/pull/2118
Also i've scheduled some build jobs:
http://ci.ignite.apache.org/viewQueued.html?itemId=659286&tab=queuedBuildOverviewTab
http://ci.ignite.apache.org/viewQueued.html?itemId=659287&tab=queuedBuildOverview
GitHub user gurustron opened a pull request:
https://github.com/apache/ignite/pull/2118
IGNITE-4636 .NET Support local collection joins in LINQ
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gurustron/ignite IGNITE-4636
Alterna
46 matches
Mail list logo
