Hi Monil,
Welcome to the Ignite community! Please use dev@ alias going forward
instead of dev-owner@.
Ignite comes with lots of examples. You can also find documentation and
screencasts on the Ignite website. If you run into any questions, please
send them here.
D.
On Tue, May 1, 2018 at 7:44 P
Alexey Kuznetsov created IGNITE-8428:
Summary: Web Console: Support connect to secured cluster
Key: IGNITE-8428
URL: https://issues.apache.org/jira/browse/IGNITE-8428
Project: Ignite
Issu
On Wed, May 2, 2018 at 4:15 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Vyacheslav,
>
> There is already a warning for this:
> https://github.com/apache/ignite/blob/master/modules/
> core/src/main/java/org/apache/ignite/internal/processors/cache/store/
> GridCacheStoreManager
Vyacheslav,
There is already a warning for this:
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheStoreManagerAdapter.java#L225
-Val
On Wed, May 2, 2018 at 11:31 AM, Vyacheslav Daradur
wrote:
> I agree I have not
I agree I have noticed that too.
But we can't just call setWriteThrough(true) if
setWriteBehindEnabled(true) was turned on because in this case
CacheStoryFactory should be properly set before.
Maybe it will be better to print to the log a warning which will
notify the user that setWriteBehindEnab
Igniters,
This is another usability issue that can be addressed quickly. Apparently,
setWriteBehindEnabled(true) is not enough to enable CacheStore, the
setWriteThrough(true) also needs to be enabled.
https://stackoverflow.com/questions/50118842/write-behind-and-write-through
Why not make it eas
GitHub user Celos opened a pull request:
https://github.com/apache/ignite/pull/3941
IGNITE-8293 BinaryUtils#isCustomJavaSerialization fails when only reaâ¦
â¦dObject is declared in a class
You can merge this pull request into a Git repository by running:
$ git pull https://gi
