Github user gromtech closed the pull request at:
https://github.com/apache/ignite/pull/3860
---
Igniters,
It's a pleasure to see how our project is evolving in a directing of being
a self-healing solution:
- Ignite can already handle critical failures such as OOM, File I/O
issues, etc. [1]
- There is an endeavor to fix cluster lock-ins due to partition map
exchange issues. [2]
Hey, Apache Ignite folks from New York! Coming to your roaring city to give
three Ignite-based talks. Come over, let's meet in person.
1. Ignite vs. Cassandra for Hybrid Transaction/Analytical Applications:
http://bit.ly/2JO0rxj
2. Ignite internals (hard-core!!!): http://bit.ly/2Icovny
3. Ignite +
Turik Campbell created IGNITE-8850:
--
Summary: Add a GA example that solves 'Traveling Salesman Problem'
Key: IGNITE-8850
URL: https://issues.apache.org/jira/browse/IGNITE-8850
Project: Ignite
Roman,
Can you try rephrasing the LINQ query as the SQL goes?
var q1 = queryable.GroupBy(o => o.Value.ContractId).Select(g => new
{ContractId = g.Key, MaxVer = g.Select(x=>x.Value.Version).Max()});
var q2 = q1.Select( ...)
At least this first part works for me. I did not try further.
Ideally pl
Folks,
This release no longer reminds an emergency one :) Are we done with the
scope, who is a release manager?
>From my side, I'd like us to review and add the fix for broken Spring
integration which is a significant regression:
https://issues.apache.org/jira/browse/IGNITE-8740
--
Denis
On Mon
Hello Dmitry and welcome to the community!
Added your account to JIRA contributors' list. Feel free to take over the
ticket.
Look forward to seeing proposed Python APIs from you so that the community
can provide feedback.
--
Denis
On Thu, Jun 21, 2018 at 1:35 AM Dmitry Melnichuk <
dmitry.melnic
Hi Mulugeta,
Could you also outline what's already supported and what's still in
progress? Probably, it will help everyone in the community to grasp what
you will bring in with this integration and what's the overall plan if you
prepare an Ignite Enhancement Proposal. Refer to proposals we have:
h
Vladimir,
As I see from the IEP, this data loading technique is supposed to be used
for deployments with Ignite persistence enabled. Is it possible to
generalize this solution and use for pure in-memory and in-memory + 3rd
party DB scenarios?
--
Denis
On Wed, Jun 20, 2018 at 8:08 AM Vladimir Oze
+1. Looks like a bug.
-Val
On Thu, Jun 21, 2018 at 12:26 PM Denis Magda wrote:
> Hello Slava,
>
> BinaryContext implementation matches only classes that reside in
> > the "org.apache.ignite.examples" package
>
>
> This looks like an oversight on our side. Think we need to fix it.
>
> --
> Denis
Hello Slava,
BinaryContext implementation matches only classes that reside in
> the "org.apache.ignite.examples" package
This looks like an oversight on our side. Think we need to fix it.
--
Denis
On Thu, Jun 21, 2018 at 9:43 AM Вячеслав Коптилин
wrote:
> Hi Igniters,
>
> I would like to dis
Github user BiryukovVA closed the pull request at:
https://github.com/apache/ignite/pull/4169
---
Hi Igniters,
I would like to discuss the behavior of BinaryTypeConfiguration in case of
using a wildcard for type names.
Let's consider the following BinaryConfiguration:
...
Hi, Kolay.
This solution looks a bit ugly for me. So I'm not sure about it.
Also, I have tried implementing it but for some reason, only 5 tests start
to pass (95 fails left).
So it's not so obvious where and how cache cleanup happens.
I have found the code which removes for some reason factories
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/4241
IGNITE-8846 Optimize entry transform operations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8846
Alter
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4161
---
GitHub user SpiderRus opened a pull request:
https://github.com/apache/ignite/pull/4240
ignite-8780 File I/O operations must be retried if buffer hasn't
read/written completely
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gri
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4239
IGNITE-8849
Signed-off-by: EdShangGG
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8849
Alternatively you ca
Eduard Shangareev created IGNITE-8849:
-
Summary: Split suites to achieve 1 hour per suite run
Key: IGNITE-8849
URL: https://issues.apache.org/jira/browse/IGNITE-8849
Project: Ignite
Issue
Hi Nikolay,
I do not see any problems with TDE for now.
On Wed, Jun 20, 2018 at 6:16 PM, Nikolay Izhikov
wrote:
> Hello, Vladimir.
>
> Does this IEP fit with IEP-18: TDE?
>
> Do we allow to user to load data into encrypted cache?
>
> В Ср, 20/06/2018 в 18:08 +0300, Vladimir Ozerov пишет:
> > Ig
Hello, Alex.
Issue looks trivial from your description.
Can you clarify - What is the issues with obvious decision you describe?
В Чт, 21/06/2018 в 17:48 +0300, Александр Меньшиков пишет:
> Hi, Igniters!
> Can someone give me advice about IGNITE-8715 [1]?
> It's a part of IEP-21 [2] about updatin
Hi, Igniters!
Can someone give me advice about IGNITE-8715 [1]?
It's a part of IEP-21 [2] about updating to JCache 1.1.
According to JCache 1.0 and 1.1 specifications Cache#close() should clean
up all Closeable objects (CacheLoader, CacheWriter, CacheEntryListener,
ExpiryPolicy) created by factori
Pavel Kovalenko created IGNITE-8848:
---
Summary: Introduce new split-brain tests when topology is under
load
Key: IGNITE-8848
URL: https://issues.apache.org/jira/browse/IGNITE-8848
Project: Ignite
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4238
IGNITE-7526 SQL: Introduce memory region for reducer merge results with
disk offload
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Mikhail Cherkasov created IGNITE-8847:
-
Summary: Node doesn't stop on node verification failure
Key: IGNITE-8847
URL: https://issues.apache.org/jira/browse/IGNITE-8847
Project: Ignite
Iss
Alexei Scherbakov created IGNITE-8846:
-
Summary: Optimize entry transform operations.
Key: IGNITE-8846
URL: https://issues.apache.org/jira/browse/IGNITE-8846
Project: Ignite
Issue Type: I
Hi Sergey,
This is probably the most important IEP we have. I am assuming that after
this gets fixed, Ignite cluster will never come to a freezing state.
I propose to name the enum *PmeStopPolicy*. Here are my suggestions:
- NONE - will result in logging the state
- STOP_PRESERVE_PARTITION
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4237
IGNITE-8752 : Ensure that binary metadata is registered outside of topology
lock.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/ap
Mikhail Cherkasov created IGNITE-8845:
-
Summary: GridUnsafe.allocateMemory throws OutOfMemoryError which
isn't handled
Key: IGNITE-8845
URL: https://issues.apache.org/jira/browse/IGNITE-8845
Proje
Igniters,
I've created new IEP [1] to address important case when Partition Map
Exchange process (for more info on it refer to [2]) hangs for some reason.
If this happens user now has to manually identify nodes causing PME to hang
and do necessary actions (usually it is enough to stop hanging nod
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/4236
IGNITE-8188
- split into batches "createAll" and "deleteAll" operations if request size
overflow
- added tests
You can merge this pull request into a Git repository by running:
$ git p
Github user ilantukh closed the pull request at:
https://github.com/apache/ignite/pull/4215
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4214
---
Pavel Kovalenko created IGNITE-8844:
---
Summary: Provide example how to implement auto-activation policy
when cluster is activated first time
Key: IGNITE-8844
URL: https://issues.apache.org/jira/browse/IGNITE-8844
Hi,
Thank you for your willingness to contribute.
Please assign the Jira ticket to yourself and set it's status to "In
Progress", so Apache community can see that this feature is currently being
worked on.
Also, please open a Github pull request so we can review and give you
feedback in a more co
GitHub user gromtech opened a pull request:
https://github.com/apache/ignite/pull/4235
IGNITE-7993 Striped pool can't be disabled
Restored the capability to disable striped pool
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/grid
Hi Pavel,
Thank you for the response. Regarding support every LINQ expression, I agree
with you. It's not possible.
Let me show an example. The following LINQ query:
/var result = queryable.GroupBy(e => e.Value.ContractId).Select(group => new
{
ContractId = group.Key,
Id = group.OrderByD
Github user x-kreator closed the pull request at:
https://github.com/apache/ignite/pull/4234
---
Vasiliy Sisko created IGNITE-8843:
-
Summary: Web console: Actualize "Getting started" content
Key: IGNITE-8843
URL: https://issues.apache.org/jira/browse/IGNITE-8843
Project: Ignite
Issue Typ
Hello, my name is Dmitry Melnichuk, my Jira username is "Melnichuk". I
would like to work on issue IGNITE-7782. Please assign the task to me or
give me permissons to assign tasks.
Regards,
Dmitry
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/4234
jvm exit 137 after starting IgniteServiceProxyTimeoutInitializedTest â¦
â¦research - test suite constriction.
You can merge this pull request into a Git repository by running:
$ git pull h
Hi Roman,
It is even hard to say what kind of SQL should we produce for such a query.
The general idea of Ignite LINQ provider is:
Do not try to support every LINQ expression (which is not possible, because
LINQ and SQL are quite different);
but try to make most SQL scenarios possible to express
42 matches
Mail list logo