Hi Pavel,
As far as I know batch tree updates already being developed. Alex, could
you please elaborate?
On Tue, Mar 5, 2019 at 5:05 PM Pavel Pereslegin wrote:
> Hi Igniters!
>
> I am working on implementing batch updates in PageMemory [1] to
> improve the performance of preloader,
Evgenii Zhuravlev created IGNITE-11487:
--
Summary: Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property
Key: IGNITE-11487
URL: https://issues.apache.org/jira/browse/IGNITE-11487
Project: Ignite
Hi, Andrey!
>> 6. ServiceGrid.
>> We can use Metastore and drop old-services later.
As you mentioned new Service Grid does not use system cache.
Legacy implementation (GridServiceProcessor), uses system cache
WITHOUT persistence since 2.3 release and does not restore services
state at node
Hi, Alexey!
>> If we can use multi JVM test with
>> different classpaths I will use them - such approach is more convenient
>> from TC point of view.
There is not such ability at the moment, you are only able to specify
additional JVM arguments in
'GridAbstractTest#additionalRemoteJvmArgs'.
Dmitriy Pavlov created IGNITE-11486:
---
Summary: Support Automatic modules for ignite-zookeeper: Resolve
issues with logging packages conflict
Key: IGNITE-11486
URL:
Dmitriy Pavlov created IGNITE-11485:
---
Summary: Support Automatic modules for ignite-hibernate: Package
interference with hibernate core and hibernate for particular verion
Key: IGNITE-11485
URL:
Maxim,
My humble opinion. If there is no convenient means to implement
partition file sending today then we should introduce something. And
keeping such facility private is much easier, because introduction of
new public API is a significantly more complex task.
пт, 1 мар. 2019 г. в 19:44, Maxim
Hi Igniters!
I am working on implementing batch updates in PageMemory [1] to
improve the performance of preloader, datastreamer and putAll.
This task consists of two major related improvements:
1. Batch writing to PageMemory via FreeList - store several values at
once to single memory page.
2.
Ivan Rakov created IGNITE-11484:
---
Summary: Get rid of ForkJoinPool#commonPool usage for csystem
critical tasks
Key: IGNITE-11484
URL: https://issues.apache.org/jira/browse/IGNITE-11484
Project: Ignite
Hi Igniters,
I'd like to start a discussion to avoid system cache usage with persistence.
System cache is used in number of component internals. No one cares
system cache can have stale data after grid restart as it wasn't impossible
before 2.1.
>From Ignite 2.1 version it is possible to be
Andrew Mashenkov created IGNITE-11483:
-
Summary: Make system cache non-persistent and deprecate.
Key: IGNITE-11483
URL: https://issues.apache.org/jira/browse/IGNITE-11483
Project: Ignite
Roman Kondakov created IGNITE-11482:
---
Summary: MVCC: Error on TxLog initialization.
Key: IGNITE-11482
URL: https://issues.apache.org/jira/browse/IGNITE-11482
Project: Ignite
Issue Type:
Alexey Platonov created IGNITE-11481:
Summary: [ML] Prototype of DatasetRow for Vectorizer
Key: IGNITE-11481
URL: https://issues.apache.org/jira/browse/IGNITE-11481
Project: Ignite
Issue
Alexey Platonov created IGNITE-11480:
Summary: [ML] Use only Vectorizer API in DatasetTrainer API
Key: IGNITE-11480
URL: https://issues.apache.org/jira/browse/IGNITE-11480
Project: Ignite
Alexey Platonov created IGNITE-11479:
Summary: [ML] Use new vectorizer API in PartitionDatasetBuilders
Key: IGNITE-11479
URL: https://issues.apache.org/jira/browse/IGNITE-11479
Project: Ignite
Ivan,
Thank for your answer. I want to use binary builds explicitly because they
don't share jars of client code. If we can use multi JVM test with
different classpaths I will use them - such approach is more convenient
from TC point of view.
P.S. I use Docker in my prototype just because it is
Alexey Platonov created IGNITE-11478:
Summary: [ML] Use new vectorizer API in Trainers
Key: IGNITE-11478
URL: https://issues.apache.org/jira/browse/IGNITE-11478
Project: Ignite
Issue
Alexey Platonov created IGNITE-11476:
Summary: [ML] Use new feature extraction API in examples
Key: IGNITE-11476
URL: https://issues.apache.org/jira/browse/IGNITE-11476
Project: Ignite
Alexey Platonov created IGNITE-11477:
Summary: [ML] Create tests for ML algorithms stability check
against binary builds
Key: IGNITE-11477
URL: https://issues.apache.org/jira/browse/IGNITE-11477
Alexey Platonov created IGNITE-11475:
Summary: [ML] Vectorizer API prototype with POC
Key: IGNITE-11475
URL: https://issues.apache.org/jira/browse/IGNITE-11475
Project: Ignite
Issue
Vladislav Pyatkov created IGNITE-11474:
--
Summary: Add possibility to run idle_verify in not idle cluster
Key: IGNITE-11474
URL: https://issues.apache.org/jira/browse/IGNITE-11474
Project: Ignite
Hello!
If you can modify your code to store nulls instead of empty strings, nulls
seem to be much more compact.
Regards,
--
Ilya Kasnacheev
вт, 5 мар. 2019 г. в 10:12, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> Hey folks,
>
> While working with Ignite users, I keep seeing data
Taras Ledkov created IGNITE-11473:
-
Summary: SQL: check convert to ENUM type by functions CAST,
CONVERT throws sane exception
Key: IGNITE-11473
URL: https://issues.apache.org/jira/browse/IGNITE-11473
Taras Ledkov created IGNITE-11472:
-
Summary: SQL: throw sane exception for unsupported features
Key: IGNITE-11472
URL: https://issues.apache.org/jira/browse/IGNITE-11472
Project: Ignite
Alexey,
If problems arise in environments different from one where usual
Ignite tests run then definitely it is a good idea to cover it. And
testing other build kinds and in other environments is a good idea as
well. But a particular problem with serialization and peer class
loading is not clear
Hi Alexey,
I think it's a great idea. Travis + Docker is a very good and cheap
solution, so we could start with it. Regards the statistics, Travis allows
to check a last build status using a badge, so it also shouldn't be a
problem.
Best regards,
Anton Dmitriev.
--
Sent from:
Hi Val,
I would say that we do not need string length at all, because it can be
derived from object footer (next field offset MINUS current field offset).
It is not very good idea to implement proposed change in Apache Ignite 2.x
because it is breaking and will add unnecessary complexity to
27 matches
Mail list logo
