You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2016/12/15 10:36:58 UTC
[jira] [Updated] (IGNITE-4408) IndexingSpi support keepBinary
options
[ https://issues.apache.org/jira/browse/IGNITE-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Mashenkov updated IGNITE-4408:
-------------------------------------
Description:
For now key and values is being deserialized before passing to IndexingSpi. This can cause performance issues in some cases and there is no way to change this behavior.
It look like we should allow to avoid deserialization and pass BinaryObjects if keepBinary option is true as we do for CacheStore.
Also SpiQueries should nof fails then both IndexingSpi is configured and GridQueryIndexing is disabled.
was:
For now key and values is being deserialized before passing to IndexingSpi. This can cause performance issues in some cases and there is no way to change this behavior.
It look like we should allow to avoid deserialization and pass BinaryObjects if keepBinary option is true as we do for CacheStore.
> IndexingSpi support keepBinary options
> --------------------------------------
>
> Key: IGNITE-4408
> URL: https://issues.apache.org/jira/browse/IGNITE-4408
> Project: Ignite
> Issue Type: Improvement
> Components: binary
> Affects Versions: 1.8
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Labels: easyfix, performance
> Fix For: 2.0
>
>
> For now key and values is being deserialized before passing to IndexingSpi. This can cause performance issues in some cases and there is no way to change this behavior.
> It look like we should allow to avoid deserialization and pass BinaryObjects if keepBinary option is true as we do for CacheStore.
> Also SpiQueries should nof fails then both IndexingSpi is configured and GridQueryIndexing is disabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)