Re: data extractor

Alexey, 1. The utility will extract raw payload bytes. If you want to build binary object or Java class instances you will need binary/marshaller metadata. If two grid will have different metadata, you should move metadata as well as dumped data for construct binary objects on another grid. Do you

Re: data extractor

Dmitriy, A few questions regarding the user cases for the utility: 1) Would I be able to read the extracted data from the dumped file without Ignite node binary/marshaller metadata? In other words, will I be able to move only the dumped file to another grid or will I need to move the metadata as w

Re: data extractor

Nikolay, I think we won't support extract from encrypted store In the first implementation. I guess we can support the encrypted store in future, or you have a reason why we should do it in first? On Sun, Jul 1, 2018 at 11:48 AM Nikolay Izhikov wrote: > Hello, Dmitriy. > > Should we support ex

Re: data extractor

Hello, Dmitriy. Should we support extraction of encrypted data? There will be 2 type of keys we should load to successfully extract data: * master key: keystore + password required. * cache keys: masterkey + access to metastore required. TDE task is almost done, please, take a look. ticket - h

data extractor

Igniters, I am working on IGNITE-7644 (export all key-value data from a persisted partition), it will be command line tool for extracting data from Ignite partition file without the need to start node. The main motivation is to have a lifebuoy in