GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/4442
IGNITE-7165: skip rebalance if assigns not changed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-7165
Alternatively you
Sure, it can wait. Thanks! Take a rest )
On Thu, Jul 26, 2018 at 11:39 PM Nikolay Izhikov
wrote:
> Hello, Denis.
>
> Actually, I'm on vacation till July, 31.
> After it I will put all my efforts to manage Ignite release.
>
> Can we wait until Tuesday?
>
> В Чт, 26/07/2018 в 17:01 -0700, Denis Ma
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/4443
IGNITE-3499: remove unused class
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-3499
Alternatively you can review and app
Alexander Kalinin created IGNITE-9101:
-
Summary: Fix configuration e2e tests
Key: IGNITE-9101
URL: https://issues.apache.org/jira/browse/IGNITE-9101
Project: Ignite
Issue Type: Bug
Alexander Kalinin created IGNITE-9102:
-
Summary: Remove support for IE10
Key: IGNITE-9102
URL: https://issues.apache.org/jira/browse/IGNITE-9102
Project: Ignite
Issue Type: Task
Folks,
I've found issue related to this test [1] (created 2016).
Looks like it not used, I've prepared PR [2].
If you have time, please, review changes.
[1] https://issues.apache.org/jira/browse/IGNITE-3499
[2] https://github.com/apache/ignite/pull/4443
On Fri, 20 Jul 2018 at 13:27 Dmitry Pav
Alexander Kalinin created IGNITE-9103:
-
Summary: Select menu component doesn't strip html entities.
Key: IGNITE-9103
URL: https://issues.apache.org/jira/browse/IGNITE-9103
Project: Ignite
Alexander Kalinin created IGNITE-9104:
-
Summary: Enhance UI grid feature
Key: IGNITE-9104
URL: https://issues.apache.org/jira/browse/IGNITE-9104
Project: Ignite
Issue Type: Improvement
Alexander Kalinin created IGNITE-9105:
-
Summary: Move to canvas-based chart rendering library.
Key: IGNITE-9105
URL: https://issues.apache.org/jira/browse/IGNITE-9105
Project: Ignite
Issu
Alexander Kalinin created IGNITE-9106:
-
Summary: Add bytes abbreviation filter.
Key: IGNITE-9106
URL: https://issues.apache.org/jira/browse/IGNITE-9106
Project: Ignite
Issue Type: Improve
Ignite Dev Community,
Within Ignite-supplied Spark DataFrames, I’d like to propose adding support
for _key and _val columns which represent the cache key and value objects
similar to the current _key/_val column semantics in Ignite SQL.
If the cache key or value objects are standard SQL types (eg
Hello, Stuart.
I like your idea.
> 1. Ignite BinaryObjects, in which case we’d need to supply a Spark Encoder
> implementation for BinaryObjects
> 2. Kryo-serialised versions of the objects.
Seems like first option is simple adapter. Am I right?
If yes, I think it's a more efficient way compari
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4424
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4185
---
Hi Dmitriy,
I would like to stress this: I'm not saying local cache it useless. I'm
supposing it is not used widely. I want to figure out if I'm mistaking.
All folks involved into user list says it is not used, so why not to
deprecate? If we make a mistake, somebody will come to user list and say
Denis,
Main features of Ignite Cache are availability and throughput.
I'd like to refactor Serviсe Grid to be the same.
Main feature should be guarantee of availability and throughput (instance
count).
Client should ask grid to execute the service, that's all. No matter how
grid will do this.
Th
Guys,
I can miss some details, but at the first glance we have everething we need
to defer
region memory allocation if it has no cache groups assignments. And it
doesn't matter
where it happens on client or server nodes.
Currently region memory allocation happens at exchange future init method.
A
Github user zzzadruga closed the pull request at:
https://github.com/apache/ignite/pull/4431
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4425
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4438
---
Hello, Igniters.
TDE. Phase 1 [1] is ready for review [2].
I meet some corner cases during development I want to describe:
1. Creation of Cache Group Encryption Keys:
1.1. To build cache create request we has to create Cache Group
Encryption Key.
1.2. To create Cache Group Encr
Greg Bakos created IGNITE-9107:
--
Summary: FINE log level causes slow transactional cache
Key: IGNITE-9107
URL: https://issues.apache.org/jira/browse/IGNITE-9107
Project: Ignite
Issue Type: Bug
Igniters,
I am working on the stability of our TC test runs.
Some of our execution timeouts (hangings, unexpected stops) happen because
of issues in source code: test itself, test runners, configurations, bug,
Linux OOM killer and so on.
We could fix them by changing code.
But almost all of the
Ed,
We already discussed this some time ago. AFAIK SSD disks do not have this
problem, so all we need is to replace HDD with SSD.
On Fri, Jul 27, 2018 at 3:26 PM Eduard Shangareev <
eduard.shangar...@gmail.com> wrote:
> Igniters,
>
> I am working on the stability of our TC test runs.
>
> Some of
GitHub user zzzadruga opened a pull request:
https://github.com/apache/ignite/pull/
IGNITE-9073 Use jackson2 dependency instead of jackson1 and remove unâ¦
â¦used dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/
Vladimir,
I am talking only about Run Cache and Basic.
I don't see any objection why we couldn't do so.
Even with extra SSD, it could be worth to split configuration to have
control over their impact on the disk system.
On Fri, Jul 27, 2018 at 3:28 PM, Vladimir Ozerov
wrote:
> Ed,
>
> We alrea
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/4445
IGNITE-7701 SQL system view for node attributes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite ignite-7701
Alter
Maxim, thank you.
If it seems it is technically possible, we can file ticket for this change.
I find this proposal reasonable, change makes perfectly sense to me.
We can wait Alex G. feedback on this change before starting actual
implementation. It can take for a while, because he is travelling
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4443
---
Merged to master. Thank you, Maxim.
пт, 27 июл. 2018 г. в 11:17, Maxim Muzafarov :
> Folks,
>
> I've found issue related to this test [1] (created 2016).
> Looks like it not used, I've prepared PR [2].
>
> If you have time, please, review changes.
>
>
> [1] https://issues.apache.org/jira/browse/I
Thanks Nikolay. For both options if the cache object isn’t a simple type,
we’d probably do something like this in our Ignite SQL statement:
select cast(_key as binary), cast(_val as binary), ...
Which would give us the BinaryObject’s byte[], then for option 1 we keep
the Ignite format and introdu
Sure.
Please, send ticket number in this thread.
пт, 27 июля 2018 г., 16:16 Stuart Macdonald :
> Thanks Nikolay. For both options if the cache object isn’t a simple type,
> we’d probably do something like this in our Ignite SQL statement:
>
> select cast(_key as binary), cast(_val as binary), ..
Stuart Macdonald created IGNITE-9108:
Summary: Spark DataFrames With Cache Key and Value Objects
Key: IGNITE-9108
URL: https://issues.apache.org/jira/browse/IGNITE-9108
Project: Ignite
Is
Here’s the ticket:
https://issues.apache.org/jira/browse/IGNITE-9108
Stuart.
On Friday, 27 July 2018 at 14:19, Nikolay Izhikov wrote:
> Sure.
>
> Please, send ticket number in this thread.
>
> пт, 27 июля 2018 г., 16:16 Stuart Macdonald (mailto:stu...@stuwee.org)>:
>
> > Thanks Niko
Ilya,
As for me, the main cause of this problem is not in CLHM itself but that
we are using it for GridLogThrottle as container with fixed size. Suppose,
at current moment we have no alternative and should start thinking about
futher steps.
Can you create clear reproducer for described issue with
Hello!
Most of our code uses CLHM as a container with fixed size. I can surely fix
LogThrottle but my main concern is H2 indexing code which uses the same
CLHM with cap.
Regards,
--
Ilya Kasnacheev
2018-07-27 16:38 GMT+03:00 Maxim Muzafarov :
> Ilya,
>
> As for me, the main cause of this prob
Is it possible to replace current implementation with google's [1] or some
other?
It a bad idea to have own CLHM and keep it outdated (this version based on
CHM from java7!) and broken.
[1]
https://mvnrepository.com/artifact/com.googlecode.concurrentlinkedhashmap/concurrentlinkedhashmap-lru
пт, 2
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/4446
IGNITE-5103 - Server drops client node from cluster when no metrics uâ¦
â¦pdate messages received in clienFailureDetectionTimeout
You can merge this pull request into a Git repository by running
Dmitriy, Igor, Ilya, Sergey!
Thank you for sharing your ideas, concerns and criticism with me. I do
appreciate it.
I already made some changes in my API, influenced by your feedback. I
also plan to add a certain set of features, that will make my UX closer
to what you can see from other Igni
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4435
---
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/4447
IGNITE-9043 let values of any type be written to Object field
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE
GitHub user zzzadruga opened a pull request:
https://github.com/apache/ignite/pull/4448
IGNITE-8936 Remove AffinityAssignment#clientEventChange as not used
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zzzadruga/ignite IGNITE-8
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4449
IGNITE-8559 extract segment index storage to out of WAL manager
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8
Igor Sapego created IGNITE-9109:
---
Summary: CPP Thin: Implement SQL API
Key: IGNITE-9109
URL: https://issues.apache.org/jira/browse/IGNITE-9109
Project: Ignite
Issue Type: New Feature
Ryabov Dmitrii created IGNITE-9110:
--
Summary: Tx commit hangs after cross-cache operations with LOCAL
cache
Key: IGNITE-9110
URL: https://issues.apache.org/jira/browse/IGNITE-9110
Project: Ignite
Hello,
I want to contribute to Ignite. My JIRA id is pankaj024.
Please add me to the contributor list.
Thank you
Pankaj
Hi Pankaj,
Welcome to the Apache Ignite community. I've added you to contributor list,
so now you can assign ticket to yourself.
Looking forward to your contributions!
Sincerely,
Dmitriy Pavlov
P.S. Additional references for you that should boost your onboarding.
Please subscribe to both dev a
Hi I want to contribute to Ignite. My JIRA ID is jaikumarAJ.
please let me know the process.
Thanks & Regards,
A.Jaikumar
+91 - 9629075011
On Fri, Jul 27, 2018 at 8:52 PM pankaj kumar wrote:
> Hello,
>
> I want to contribute to Ignite. My JIRA id is pankaj024.
> Please add me to the contribut
Hi Arjunan,
I've added you to contributors list, and now you can assign ticket.
Best practice is to discuss ticket you would like to pick up using
dev.list. It will mitigate risk that ticket is outdated or already done by
someone else.
Full process and hints you can find here
https://cwiki.apach
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4180
---
Pavel Kovalenko created IGNITE-9111:
---
Summary: Do not wait for deactivation in
GridClusterStateProcessor#publicApiActiveState
Key: IGNITE-9111
URL: https://issues.apache.org/jira/browse/IGNITE-9111
Alexander Gerus created IGNITE-9112:
---
Summary: Pre-touch for Ignite off-heap memory
Key: IGNITE-9112
URL: https://issues.apache.org/jira/browse/IGNITE-9112
Project: Ignite
Issue Type: New F
Valentin Kulichenko created IGNITE-9113:
---
Summary: Allocate memory for a data region when first cache
assigned to this region is created
Key: IGNITE-9113
URL: https://issues.apache.org/jira/browse/IGNITE-911
Ticket created: https://issues.apache.org/jira/browse/IGNITE-9113
-Val
On Fri, Jul 27, 2018 at 5:59 AM Dmitry Pavlov wrote:
> Maxim, thank you.
>
> If it seems it is technically possible, we can file ticket for this change.
>
> I find this proposal reasonable, change makes perfectly sense to me
Andrew Medvedev created IGNITE-9114:
---
Summary: Fail fast in
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query
Key: IGNITE-9114
URL: https://issues.apache.org/jira/browse/IGNITE
Andrew Medvedev created IGNITE-9115:
---
Summary:
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query
has infinite loop with exit condition on success, thus failure to make
reservation on partition can "hang" quer
Guys,
Use cases for local caches are rare, but they definitely exist. I don't
think it's a very good idea to deprecate this functionality at this point.
At the same point, it's obviously not the most critical part of the
product, so maintaining the whole separate implementation for it is
probably
Stuart, Nikolay,
I really don't like the idea of exposing '_key' and '_val' fields. This is
legacy stuff that hopefully will be removed altogether one day. Let's not
use it in new features.
Actually, I don't even think it's even needed. Spark docs [1] suggest two
ways of creating a typed dataset:
Val,
Yes you can already get access to the cache objects as an RDD or
Dataset but you can’t use the Ignite-optimised DataFrames with these
mechanisms. Optimised DataFrames have to be passed through Spark SQL’s
Catalyst engine to allow for predicate pushdown to Ignite. So the
usecase we’re talking
Well, the second approach would use the optimizations, no?
-Val
On Fri, Jul 27, 2018 at 11:49 AM Stuart Macdonald wrote:
> Val,
>
> Yes you can already get access to the cache objects as an RDD or
> Dataset but you can’t use the Ignite-optimised DataFrames with these
> mechanisms. Optimised Da
If your predicates and joins are expressed in Spark SQL, you cannot
currently optimise those and also gain access to the key/val objects. If
you went without the Ignite Spark SQL optimisations and expressed your
query in Ignite SQL, you still need to use the _key/_val columns. The
Ignite documentat
Hi Igniters,
I would discourage all Igniters from direct assigning issues to anyone
else. Of cource excepting the case it was directly discussed with asignee.
Any contributor should be able to assign issue to himself.
I left issue unassigned until Alex G would assign it.
Sincerely,
Dmitriy Pavlo
Pavel Tupitsyn created IGNITE-9116:
--
Summary: .NET: LINQ: CacheConfiguration.SqlSchema is ignored
Key: IGNITE-9116
URL: https://issues.apache.org/jira/browse/IGNITE-9116
Project: Ignite
Issu
Hello Nikolay,
This is a great news!
Vladimir O., as far as I understand you will be reviewing the contribution,
won't you?
--
Denis
On Fri, Jul 27, 2018 at 5:16 AM Nikolay Izhikov wrote:
> Hello, Igniters.
>
> TDE. Phase 1 [1] is ready for review [2].
>
> I meet some corner cases during deve
Stuart,
_key and _val fields is quite a dirty hack that was added years ago and is
virtually never used now. We never recommend to use these fields and I
would definitely avoid building new features based on them.
Having said that, I'm not arguing the use case, but we need better
implementation a
On Fri, Jul 27, 2018 at 3:02 PM, Dmitriy Pavlov
wrote:
> Hi Igniters,
>
> I would discourage all Igniters from direct assigning issues to anyone
> else. Of cource excepting the case it was directly discussed with asignee.
> Any contributor should be able to assign issue to himself.
>
> I left iss
Anton, clients could be remote, not local. However, even if I agreed with
you, we cannot remove the current functionality from the product.
As suggested, by default services are deployed only on server nodes. If a
user wants to involve client nodes, then it should be done by specifying a
node filt
67 matches
Mail list logo
