Hi, Dmitry,
To get objects with full schema in footer you should just start your node
with config, which is going to have compactFooter set to "false" in it:
<property name="binaryConfiguration">
<bean class="org.apache.ignite.configuration.BinaryConfiguration">
<property name="compactFooter" value="false"/>
</bean>
</property>
For example, C++ server nodes use full footer in schema.
Two other cases - no schema and raw data are just the ways objects are
written. When you write some fields as named fields, and then write other
fields in raw mode, objects are going to have raw data in them. When all
fields in object are written in a raw mode, it contains no schema. So,
basically, you can get such objects from any cache, if this is how a user
have chosen to serialize them.
Best Regards,
Igor
On Fri, Jul 13, 2018 at 6:44 PM Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:
> Hello fellow Ignite developers!
>
> As you may already know, I am building Ignite thin client API library in
> Python. I have reached the point where all applicable operations are
> implemented. All data types are also fully covered, except for some
> variants of Complex object.
>
> I have been already told that Ignite stores its SQL tables using a
> Complex object data type. It lets me write parser and builder for that
> exact variant of Complex object used for an SQL row:
>
> - compact footer approach, all fields are named.
>
> Now I wonder if I can find any other real-life usage example of Complex
> objects
>
> - with no schema,
> - with full schema in footer,
> - with raw data.
>
> Your advice is greatly appreciated.
>
> Ideally I should be able to automate the creation of various kinds of
> Complex objects to build my unit tests upon it.
>
> Dmitry
>
