Denis, Igor,
What can be done now
1. create a default cache name for Redis data, e.g. "REDIS_CACHE" that has to
be configured explicitly in xml file (as it is done with other caches) by a
user if he/she needs Redis protocol.
2. Force users to specify cache names as prefix to their keys, so that
GitHub user abeliak opened a pull request:
https://github.com/apache/ignite/pull/1862
Ignite 4799
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4799
Alternatively you can review and apply these
Github user abeliak closed the pull request at:
https://github.com/apache/ignite/pull/1850
---
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
Roman, would you suggest a quick solution for the redis integration or even
implement it in the nearest couple of days? We need to change the defaul
cache name in 2.0. Otherwise, it can be done only in an year or so in 3.0.
Denis
On Sunday, April 23, 2017, Seliverstov Igor
Hi guys!
Nikolay, the next improvements are maden (
https://github.com/apache/ignite/pull/1783):
- changed code according with code style (extra space, if else blocks,
javadoc)
- written two tests one which will testing new parametes and other which
will testing role validation
-
Hi,
excellent job so far!
What about classification algorithms?
If everyone agrees, let's start by adding logistic regression to the list:
https://issues.apache.org/jira/browse/IGNITE-5059
Best regards,
Vladisav
On Fri, Apr 21, 2017 at 10:00 PM, Nikita Ivanov wrote:
>
Vladisav Jelisavcic created IGNITE-5059:
---
Summary: Implement logistic regression
Key: IGNITE-5059
URL: https://issues.apache.org/jira/browse/IGNITE-5059
Project: Ignite
Issue Type:
Hi Roman,
The ticket number is IGNITE-3488.
It's planned not to have null-named or default caches at all. All the
caches must be defined explicitly or via templates and have names. The
current implementation uses a cache with null name, so, we need some
configuration property to define which