Igniters,
Getting back to the discussion on how to switch between caches when using Redis
(and potentially memcached).# Please note, that this is a problem only with a
part of Redis data stuctures such as currently implemented STRING. For sets and
hash tables, set/hash name can be treated as a c
Roman Shtykh created IGNITE-5241:
Summary: Redis hash table support
Key: IGNITE-5241
URL: https://issues.apache.org/jira/browse/IGNITE-5241
Project: Ignite
Issue Type: New Feature
Vasiliy Sisko created IGNITE-5240:
-
Summary: Web console: Invalid docker repository name in compose
file
Key: IGNITE-5240
URL: https://issues.apache.org/jira/browse/IGNITE-5240
Project: Ignite
Alexey Kuznetsov created IGNITE-5239:
Summary: Web Console: Add an option to show full stack trace on
Queries screen
Key: IGNITE-5239
URL: https://issues.apache.org/jira/browse/IGNITE-5239
Project
Denis Magda created IGNITE-5238:
---
Summary: Ignite Spark can't be used with Ignite REST
Key: IGNITE-5238
URL: https://issues.apache.org/jira/browse/IGNITE-5238
Project: Ignite
Issue Type: Bug
Taras Ledkov created IGNITE-5237:
Summary: JDBC Driver: support client info
Key: IGNITE-5237
URL: https://issues.apache.org/jira/browse/IGNITE-5237
Project: Ignite
Issue Type: Task
Taras Ledkov created IGNITE-5236:
Summary: JDBC Driver: implement Connection.isValid througn PING
message
Key: IGNITE-5236
URL: https://issues.apache.org/jira/browse/IGNITE-5236
Project: Ignite
Taras Ledkov created IGNITE-5235:
Summary: JDBC Driver: impelemnt prepared statement
Key: IGNITE-5235
URL: https://issues.apache.org/jira/browse/IGNITE-5235
Project: Ignite
Issue Type: Task
Taras Ledkov created IGNITE-5234:
Summary: JDBC Driver: support connection and query timeout
Key: IGNITE-5234
URL: https://issues.apache.org/jira/browse/IGNITE-5234
Project: Ignite
Issue Type
Taras Ledkov created IGNITE-5233:
Summary: JDBC Driver: implement metadata support
Key: IGNITE-5233
URL: https://issues.apache.org/jira/browse/IGNITE-5233
Project: Ignite
Issue Type: Task
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/1960
Ignite 4763 review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-4763-review
Alternatively you can review and ap
GitHub user rfqu opened a pull request:
https://github.com/apache/ignite/pull/1959
IGNITE-4831 fixed (Add an option to disable MBeans).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rfqu/ignite ignite-4831
Alternatively you ca
Github user rfqu closed the pull request at:
https://github.com/apache/ignite/pull/1957
---
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 enabl
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/1958
Ignite 5052
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5052
Alternatively you can review and apply th
Alexey Goncharuk,
I take a look at source code and noticed classes with names
like: GridCacheDatabaseSharedManager.java
As far as I remember we decided that "Grid" is a kind of "deprecated"
prefix?
What do you think? Does it make sense to rename?
On Tue, May 16, 2017 at 9:06 PM, Alexey Goncharuk
Denis,
Headers are updated, RAT check is passing now.
2017-05-16 2:37 GMT+03:00 Denis Magda :
> The receipt of the software grant (the persistent store) was acknowledged
> by Craig Russel.
>
> Now, we need to move on with this
>
> > In the meanwhile, I’ve prepared the IP Clearance page referring
Hi Vadim,
I see that testNaturalIdCache still fails for
HibernateL2CacheTransactionalSelfTest, need investigate and find root cause
of failure.
Thanks
On Wed, May 10, 2017 at 5:03 PM, Вадим Опольский
wrote:
> Hello guys!
>
> Semen, Sergey is issue https://issues.apache.org/jira/browse/IGNITE-1
GitHub user rfqu opened a pull request:
https://github.com/apache/ignite/pull/1957
Ignite 4831
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rfqu/ignite ignite-4831
Alternatively you can review and apply these changes as the p
Github user dspavlov closed the pull request at:
https://github.com/apache/ignite/pull/1943
---
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 e
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/1956
Ignite 4938 & IGNITE-4947: Fix AI 2.0 TC suites
Ignite 4938 & IGNITE-4947: Fix AI 2.0 TC suites
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/1955
IGNITE-5100 don`t remove active exchange events from exchange list
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/1954
ignite-gg-12199 added new variable CLEAN_WORK_DIR in config files
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite i
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1953
IGNITE-5208: Fixed sigfault on concurrent map access.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5208
Alter
Hi Vadim,
Did you check test pass on TeamCity in this suite, could you please provide
link for related TeamCity run?
Thanks
On Tue, May 16, 2017 at 1:35 PM, Вадим Опольский
wrote:
> Hi guys!
>
> IgniteCache150ClientsTest.java was removed from
> IgniteClientTestSuite.java to IgniteCacheTestSuit
Github user nizhikov closed the pull request at:
https://github.com/apache/ignite/pull/1948
---
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 e
Hi all,
I'll take IGNITE-5227 as a first ticket if you don't mind.
--
Thanks,
Mikhail.
Thank you!
On Tue, May 16, 2017 at 1:59 PM, Pavel Tupitsyn
wrote:
> Hi Mikhail,
>
> I've added you to the Jira project, welcome to the Ignite community!
>
> On Tue, May 16, 2017 at 1:56 PM, Mikhail Cherkasov <
> mcherka...@gridgain.com>
> wrote:
>
> > Hi all,
> >
> > Could you please provide me
Hi Mikhail,
I've added you to the Jira project, welcome to the Ignite community!
On Tue, May 16, 2017 at 1:56 PM, Mikhail Cherkasov
wrote:
> Hi all,
>
> Could you please provide me a contributor permissions?
> My jira account: mcherkasov
>
> --
> Thanks,
> Mikhail.
>
Hi all,
Could you please provide me a contributor permissions?
My jira account: mcherkasov
--
Thanks,
Mikhail.
Hi guys,
I've prepared the PR to show my idea.
https://github.com/apache/ignite/pull/1951/files
About querying - I've just copied existing tests and have annotated the
testing data.
https://github.com/apache/ignite/pull/1951/files#diff-c19a9df4058141d059bb577e75244764
It means fields which will
Hi guys!
IgniteCache150ClientsTest.java was removed from
IgniteClientTestSuite.java to IgniteCacheTestSuite.java. Single test suite
was deleted.
Review please this fix - https://github.com/apache/ignite/pull/1952
Vadim Opolskii
2017-05-15 11:38 GMT+03:00 Вадим Опольский :
> Hi guys!
>
> Vlad
Evgenii Zhuravlev created IGNITE-5232:
-
Summary: GridDhtPartitionDemander.requestPartitions invokes
sendMessages consequently, which lead to significant increase of node start
time on large clusters with ssl
Key: IGNITE-5232
GitHub user vadopolski opened a pull request:
https://github.com/apache/ignite/pull/1952
IGNITE-4447
Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vadopolski/i
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/1951
IGNITE-5226
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-5226
Alternatively you can review and apply these change
Github user vadopolski closed the pull request at:
https://github.com/apache/ignite/pull/1950
---
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
Andrey Novikov created IGNITE-5231:
--
Summary: Web Console: Add support for Ignite 2.0 cluster on
Queries screen
Key: IGNITE-5231
URL: https://issues.apache.org/jira/browse/IGNITE-5231
Project: Ignite
Vladimir, thank you for this suggestion.
As newcomer in the Ignite I agree with you, sometimes it is very hard to
understand huge classes which contain sets of inner classes.
>> 1) Inner classes (both static and non-static)
Completelly agree, especially classes which will be serialized.
>> 2) Usa
GitHub user vadopolski opened a pull request:
https://github.com/apache/ignite/pull/1950
IGNITE-4447
Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vadopolski/i
Igniters,
Ignite is known to be complex product. Partially this complexity comes from
... complex problems we are trying to resolve. But partially it comes from
how we write our code. I noticed several anti-patterns which makes our code
hard to manage:
1) Inner classes (both static and non-static
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/1942
---
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 AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1949
Ignite 1.8.7.b1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.7.b1
Alternatively you can review and app
Github user rfqu closed the pull request at:
https://github.com/apache/ignite/pull/1945
---
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 enabl
Ilya Borisov created IGNITE-5230:
Summary: Web Console: SVG icons integration
Key: IGNITE-5230
URL: https://issues.apache.org/jira/browse/IGNITE-5230
Project: Ignite
Issue Type: Task
To my knowledge, Memcached does not allow to do this.
-Val
On Mon, May 15, 2017 at 9:27 PM, Roman Shtykh
wrote:
> Denis, yes, I would like to enable switching caches via "CONFIG SET
> parameter value".I created https://issues.apache.org/
> jira/browse/IGNITE-5229 for this, and will discuss it i
Denis,
It changes format of serialized data. (arrays, Collection, Map, BigDecimal,
String, Enum)
Data which will have been serialized before this improvement won't be able
to be deserialized after and vice versa.
2017-05-16 2:52 GMT+03:00 Denis Magda :
> As I see the discussion is happening in
45 matches
Mail list logo
