GitHub user raghavebdrayr opened a pull request:
https://github.com/apache/ignite/pull/2031
Ignite 5075
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-5075
Alternatively you can review and apply these chang
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/2030
IGNITE-5030 Support Spring @Cacheable(sync=true) annotation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-50
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/2029
IGNITE-5301 JVM crashes on H2TreeIndex destroy
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5301
Alternativ
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2028
IGNITE-5333 .NET: Include Apache.Ignite.exe in the main NuGet package
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite
Sergey Kalashnikov created IGNITE-5335:
--
Summary: Wrong value read by SQL query for field containing
negative decimal
Key: IGNITE-5335
URL: https://issues.apache.org/jira/browse/IGNITE-5335
Proje
Hello Denis,
I have an idea of how we could clarify proposed above approach to
collecting metrics for PDS.
I suggest to split all metrics into two major groups (disk-related and
memory-related) and group them in the following interfaces:
public interface PersistenceMemoryMetrics extends MemoryMe
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2027
IGNITE-5334
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5334-1
Alternatively you can review and apply thes
Vladimir Ozerov created IGNITE-5334:
---
Summary: Return old schema escape behavior
Key: IGNITE-5334
URL: https://issues.apache.org/jira/browse/IGNITE-5334
Project: Ignite
Issue Type: Task
Pavel Tupitsyn created IGNITE-5333:
--
Summary: .NET: Include Apache.Ignite.exe in the main NuGet package
Key: IGNITE-5333
URL: https://issues.apache.org/jira/browse/IGNITE-5333
Project: Ignite
+1 for public
it make sense when copy-pasting SQL queries from ignite to H2 in order to
check how sql works.
On Mon, May 29, 2017 at 9:21 PM, Pavel Tupitsyn
wrote:
> If "public" is already in H2, then it makes sense to use it.
>
> On Mon, May 29, 2017 at 5:18 PM, Sergey Kozlov
> wrote:
>
> > I
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/1994
---
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 feat
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/2000
---
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
Thanks Yakov.
I moved IGNITE-5321 to resolved state.
Is that right?
2017-05-29 17:24 GMT+03:00 Yakov Zhdanov :
> Merged. Thanks for contribution, Nick. Please also see my edits.
>
> --Yakov
>
> 2017-05-28 19:29 GMT+03:00 Николай Ижиков :
>
> > Hello. Here is pull request for this issue:
> >
> >
Dmitry Karachentsev created IGNITE-5332:
---
Summary: Add toString() to
GridNearAtomicAbstractSingleUpdateRequest and it's inheritors
Key: IGNITE-5332
URL: https://issues.apache.org/jira/browse/IGNITE-5332
Merged. Thanks for contribution, Nick. Please also see my edits.
--Yakov
2017-05-28 19:29 GMT+03:00 Николай Ижиков :
> Hello. Here is pull request for this issue:
>
> https://github.com/apache/ignite/pull/2022
>
> 2017-05-26 13:16 GMT+03:00 Yakov Zhdanov :
>
> > Hi Nick! Good catch. Please go ah
If "public" is already in H2, then it makes sense to use it.
On Mon, May 29, 2017 at 5:18 PM, Sergey Kozlov wrote:
> I vote for "public". I assume we may need "ignite" word for future as
> reserved word for SQL syntax extensions ...
>
> On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov
> wrote:
>
>
I vote for "public". I assume we may need "ignite" word for future as
reserved word for SQL syntax extensions ...
On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov wrote:
> I'm OK with 'public'.
>
> Does the "default schema" mean (for Ignite) that all object are contained
> in the schema is availabl
+1 for public
Kind regards,
Alex.
On Mon, May 29, 2017 at 5:14 PM, Taras Ledkov wrote:
> I'm OK with 'public'.
>
> Does the "default schema" mean (for Ignite) that all object are contained
> in the schema is available without a schema specification?
>
>
>
> On 29.05.2017 16:54, Vladimir Ozerov
I'm OK with 'public'.
Does the "default schema" mean (for Ignite) that all object are
contained in the schema is available without a schema specification?
On 29.05.2017 16:54, Vladimir Ozerov wrote:
Folks,
I am going to introduce predefined SQL schema which is always accessible on
all Ignit
+1 for ignite
пн, 29 мая 2017 г. в 17:03, Igor Sapego :
> I like "ignite" as it has lower chance to interfere with anything
> which is already reserved.
>
> Best Regards,
> Igor
>
> On Mon, May 29, 2017 at 5:01 PM, Sergi Vladykin
> wrote:
>
> > PUBLIC is already default schema in H2. You can not
Done.
Sergi
2017-05-26 21:26 GMT+03:00 Dmitriy Setrakyan :
> On Fri, May 26, 2017 at 8:48 AM, Sergi Vladykin
> wrote:
>
> > Guys,
> >
> > As I see we did not drop AffinityKeyMapper for 2.0.
> >
> > May be lets at least deprecate it?
> >
>
> I think we must. Any objections?
>
I like "ignite" as it has lower chance to interfere with anything
which is already reserved.
Best Regards,
Igor
On Mon, May 29, 2017 at 5:01 PM, Sergi Vladykin
wrote:
> PUBLIC is already default schema in H2. You can not even drop it. Oracle
> does have PUBLIC schema as well.
>
> Sergi
>
> 2017
PUBLIC is already default schema in H2. You can not even drop it. Oracle
does have PUBLIC schema as well.
Sergi
2017-05-29 16:54 GMT+03:00 Vladimir Ozerov :
> Folks,
>
> I am going to introduce predefined SQL schema which is always accessible on
> all Ignite nodes [1]. Now I am thinking on how t
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/2026
IGNITE-5299 Don't set IgniteLock as broken if lock is failoverSafe
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
Vladimir Ozerov created IGNITE-5331:
---
Summary: Investigate performance implications of SQL schema
refactoring
Key: IGNITE-5331
URL: https://issues.apache.org/jira/browse/IGNITE-5331
Project: Ignite
SQL Server uses "dbo", Oracle uses current user name.
I prefer "ignite". It is the only one that makes sense to me of all of the
above.
"public" - as opposed to "private"? What's the point?
Pavel
On Mon, May 29, 2017 at 4:54 PM, Vladimir Ozerov
wrote:
> Folks,
>
> I am going to introduce pred
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/2025
Ignite 5210 When enabled security authentication, server is unable to
restart if client tries to reconnect
You can merge this pull request into a Git repository by running:
$ git pull
Folks,
I am going to introduce predefined SQL schema which is always accessible on
all Ignite nodes [1]. Now I am thinking on how to name. Ideas are welcomed.
My 50 cents:
1) "public" - Postgres use this name
2) "mydb" - MySQL use this name
3) "ignite" - to be aligned with our product name
4) "de
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1937
---
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
Hi, Igntrs! Is it make sense transaction on cluster of only node to
rollback?
--
*Best Regards,*
*Kuznetsov Aleksey*
Pavel Tupitsyn created IGNITE-5330:
--
Summary: .NET: Peer assembly loading documentation
Key: IGNITE-5330
URL: https://issues.apache.org/jira/browse/IGNITE-5330
Project: Ignite
Issue Type: Ta
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2024
IGNITE-5317
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5317
Alternatively you can review and apply these
Pavel Tupitsyn created IGNITE-5329:
--
Summary: .NET: Enable peer assembly loading in all APIs
Key: IGNITE-5329
URL: https://issues.apache.org/jira/browse/IGNITE-5329
Project: Ignite
Issue Typ
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2023
---
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
Vladimir Ozerov created IGNITE-5328:
---
Summary: Support cache atomicity mode for CREATE TABLE
Key: IGNITE-5328
URL: https://issues.apache.org/jira/browse/IGNITE-5328
Project: Ignite
Issue Ty
Vladimir Ozerov created IGNITE-5327:
---
Summary: Create predefined cache templates for CREATE TABLE command
Key: IGNITE-5327
URL: https://issues.apache.org/jira/browse/IGNITE-5327
Project: Ignite
Vladimir Ozerov created IGNITE-5326:
---
Summary: Support "backups" property for CREATE TABLE property
Key: IGNITE-5326
URL: https://issues.apache.org/jira/browse/IGNITE-5326
Project: Ignite
I
Vladimir Ozerov created IGNITE-5325:
---
Summary: CREATE TABLE should support "cacheGroup" property
Key: IGNITE-5325
URL: https://issues.apache.org/jira/browse/IGNITE-5325
Project: Ignite
Issu
Alexey Goncharuk created IGNITE-5324:
Summary: Move volatile data structures into a separate cache
Key: IGNITE-5324
URL: https://issues.apache.org/jira/browse/IGNITE-5324
Project: Ignite
Alexey Goncharuk created IGNITE-5323:
Summary: Move record serializer version from file name to file
header
Key: IGNITE-5323
URL: https://issues.apache.org/jira/browse/IGNITE-5323
Project: Ignite
Alexey Goncharuk created IGNITE-5322:
Summary: Improve WAL record/iterator structure
Key: IGNITE-5322
URL: https://issues.apache.org/jira/browse/IGNITE-5322
Project: Ignite
Issue Type: Im
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2023
IGNITE-5315 .NET: Fix LINQ and cache configuration broken by IGNITE-5287
(sqlEscapeAll)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptup
42 matches
Mail list logo
