Sascha Hofer created IGNITE-7483:
Summary: Queries: transformers are not executed when paging the
result
Key: IGNITE-7483
URL: https://issues.apache.org/jira/browse/IGNITE-7483
Project: Ignite
Hi Raymond,
Upcoming Ignite 2.4 has a lot of changes to run Ignite.NET under .NET Core
on Linux and macOS (as well as Windows).
However, we are not targeting .NET Standard, since it misses some crucial
things like DynamicMethod.
Please make sure that you don't confuse .NET Standard and .NET Core:
Thanks Denis, makes sense.
On Fri, Jan 19, 2018 at 10:55 PM, Denis Magda wrote:
> Added the proposed callout to the top of the page:
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 9+Thin+Client+Protocol
>
> > On Jan 19, 2018, at 9:36 AM, Denis Magda wrote:
> >
> > Pavel,
> >
> > Do
Yury Babak created IGNITE-7484:
--
Summary: Documentation for new lin reg trainer.
Key: IGNITE-7484
URL: https://issues.apache.org/jira/browse/IGNITE-7484
Project: Ignite
Issue Type: Task
It seems that problem isn't related with deadlock detection and should be
reproducible when deadlock detection disabled.
Anyway it sounds like a bug. Could you please file a ticket and provide
minimal reproducer?
19 янв. 2018 г. 3:55 PM пользователь "ALEKSEY KUZNETSOV" <
alkuznetsov...@gmail.com>
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3414
Ignite 2.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-2.4
Alternatively you can review and apply these changes as
Sergey Kosarev created IGNITE-7485:
--
Summary: control.sh utility does not support authentication
Key: IGNITE-7485
URL: https://issues.apache.org/jira/browse/IGNITE-7485
Project: Ignite
Issue
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/3415
IGNITE-7477 Ignite.NET does not work on Java 9
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-7477
Alternatively yo
Sure
пн, 22 янв. 2018 г. в 12:25, Andrey Gura :
> It seems that problem isn't related with deadlock detection and should be
> reproducible when deadlock detection disabled.
>
> Anyway it sounds like a bug. Could you please file a ticket and provide
> minimal reproducer?
>
> 19 янв. 2018 г. 3:55 P
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/3416
IGNITE-7485 add support for authentication parameters
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-7485
Al
Alexey Kuznetsov created IGNITE-7486:
Summary: Сache operation failed after transaction rolled back due
to deadlock
Key: IGNITE-7486
URL: https://issues.apache.org/jira/browse/IGNITE-7486
Project:
Hello Ignite Community!
My name is Roman. I want to contribute to Apache Ignite. Any help on this
will be appreciated.
Thanks!
Best Regards, Roman
Email: ro...@gromtech.ru
Username at Jira: guseinov
Pavel Tupitsyn created IGNITE-7487:
--
Summary: .NET: Thin client: Documentation
Key: IGNITE-7487
URL: https://issues.apache.org/jira/browse/IGNITE-7487
Project: Ignite
Issue Type: Task
Oleg Ignatenko created IGNITE-7488:
--
Summary: fix javadoc and license check failures introduced per
IGNITE-7284
Key: IGNITE-7488
URL: https://issues.apache.org/jira/browse/IGNITE-7488
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3415
---
Github user oignatenko closed the pull request at:
https://github.com/apache/ignite/pull/2600
---
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/3417
IGNITE-2766 Opportunistically reopen cache after client reconnect.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
Andrew Mashenkov created IGNITE-7489:
Summary: Weird FillFactor metric fluctuation.
Key: IGNITE-7489
URL: https://issues.apache.org/jira/browse/IGNITE-7489
Project: Ignite
Issue Type: Bug
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/3418
Ignite 6899 check
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6899-check
Alternatively you can review and
Igniters,
What’s left and what prevents us from passing 2.4 through the QA phase?
Petr, Anton, Vladimir, Alex G., others please chime in.
—
Denis
> On Jan 17, 2018, at 7:05 PM, Dmitriy Setrakyan wrote:
>
> Great news, indeed! Looking forward to 2.4 release.
>
> On Wed, Jan 17, 2018 at 2:55 A
GitHub user gg-shq opened a pull request:
https://github.com/apache/ignite/pull/3419
IGNITE-6917: SQL: implement COPY command for efficient data loading
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignit
Issues
https://issues.apache.org/jira/browse/IGNITE-6711
https://issues.apache.org/jira/browse/IGNITE-6902
are in master and ignite-2.4
On Mon, Jan 22, 2018 at 6:43 PM, Denis Magda wrote:
> Igniters,
>
> What’s left and what prevents us from passing 2.4 through the QA phase?
>
> Petr, Anton, Vl
Denis Magda created IGNITE-7490:
---
Summary: Doc: clarify what's table name and how to change
fields/indexes for QueryEntity/Annotations configs
Key: IGNITE-7490
URL: https://issues.apache.org/jira/browse/IGNITE-7490
Hey Vladisav,
I implemented your requests. Take a look, specifically, i created an
interface to encapsulate the NodeUpdates and let
the DataStructuresProcessor handle the execution by checking for one type
as opposed to multiple if checks. In this case it checks for
GridCacheNodeUpdate
instance an
Ok, let’s target Wednesday as a code freeze date.
Community members who are involved in 2.4 release please merge you fixes and
optimizations by that time.
—
Denis
> On Jan 22, 2018, at 8:24 AM, Anton Vinogradov wrote:
>
> Issues
> https://issues.apache.org/jira/browse/IGNITE-6711
> https://is
Hi Roman and welcome to the Ignite community!
Added you to Ignite JIRA, so now you can assign tickets on yourself. Below you
can find additional useful information.
Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists
Get familiar with Ignit
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3335
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2283
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/3401
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/3181
---
Andrey Kuznetsov created IGNITE-7491:
Summary: Documentation: add new data region metrics description
Key: IGNITE-7491
URL: https://issues.apache.org/jira/browse/IGNITE-7491
Project: Ignite
Guys, can you check if you call tx.close(); or properly use
try-with-resources construct?
Tx context should not be cleared automatically otherwise user would not get
any notification that original transaction failed. I believe context should
be cleared on tx.close().
Anyway, let's take a look at
Val,
Your suggestion to prohibit any cache operation on partition loss does not
make sense to me. Why should I care about some partition during particular
operation if I don't access it? Imagine I use data on nodes A and B
performing reads and writes and node C crashes in the middle of tx. Should
Alexey Kuznetsov created IGNITE-7492:
Summary: Implement metrics for Memory Regions in UI tools
Key: IGNITE-7492
URL: https://issues.apache.org/jira/browse/IGNITE-7492
Project: Ignite
Iss
created ticket with reproducer [1]
I think the fix should be to clear context in tx.close()
[1] https://issues.apache.org/jira/browse/IGNITE-7486
> 23 янв. 2018 г., в 1:56, Yakov Zhdanov написал(а):
>
> Guys, can you check if you call tx.close(); or properly use
> try-with-resources construc
Vladimir Ozerov created IGNITE-7493:
---
Summary: Propagate WAL management API to .NET
Key: IGNITE-7493
URL: https://issues.apache.org/jira/browse/IGNITE-7493
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-7494:
---
Summary: WAL management commands for control.sh script
Key: IGNITE-7494
URL: https://issues.apache.org/jira/browse/IGNITE-7494
Project: Ignite
Issue Ty
Vladimir Ozerov created IGNITE-7495:
---
Summary: Ability to disable WAL globally for data region
Key: IGNITE-7495
URL: https://issues.apache.org/jira/browse/IGNITE-7495
Project: Ignite
Issue
38 matches
Mail list logo
