You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by zhuangmz08 <zh...@qq.com> on 2016/06/14 09:54:21 UTC
回复: Python Interface
Yes, I look at the samples before. I wrote this email to ensure whether there's a format guide.
------------------ 原始邮件 ------------------
发件人: "Niclas Hedhman";<ni...@hedhman.org>;
发送时间: 2016年6月14日(星期二) 下午5:49
收件人: "dev"<de...@zest.apache.org>;
主题: Re: Python Interface
Pandas DataFrame ??? No idea what that is...
We have not written a Guide for the internal storage format of the
MapEntityStore or even the ValueSerialization subsystem.
But it is very straight forward; There are a handful of fields in the
"root" object, i.e. metadata about the object, such as identity,
lastModified, version number and so on. Then there are four fields in the
root object named; properties, assocations, manyassociations,
namedassociations, which contains entries with the "name" (the method name)
as the key and the value being the serialized form of each of those states.
It is pretty clear if you look at a capture sample;
{
"associations": {},
"identity": "97d21d04-58c4-44a9-bd6c-1f861cf0a1f9-0",
"modified": 1465718396917,
"namedassociations": {},
"type": "org.apache.zest.index.solr.SolrQueryServiceTest$TestEntity",
"version":
"MemoryEntityStoreService-d10f4fd5-da9a-4e56-9476-a1750c9509f10",
"manyassociations": {},
"properties": {
"identity": "97d21d04-58c4-44a9-bd6c-1f861cf0a1f9-0",
"name": "Hello World"
},
"application_version": "1.0"
}
In this example, there are no associations, but they are referencing
Identities, directly, List or Map form. The properties here are very
simple, only a
Property<String> identity(); // part of the Identity interface
Property<String> name(); // from somewhere...
So, to use this in another platform should be pretty simple if there is
JSON support.
Indexing format is a lot more complex, and is very different between
Indexing engines. There is no equivalent "unifying" intermediary, as we
have in the MapEntityStore.
Cheers
Niclas
On Tue, Jun 14, 2016 at 3:37 PM, zhuangmz08 <zh...@qq.com> wrote:
> Hi,
>
>
> I have some written python scripts, which consums data from former
> database. Now, I would like to switch the former database into a domain
> designed database, which is the mongo Map Entity Store. And I also like to
> use ONLY one domain model across multi language platform.
> I have some follwing questions:
> 1. Is there any exist python interface to read database into pandas
> DataFrame? I'm afraid not....
> 2. If I write my own python interface, I would have to know the Entity
> Format, since my interface exposes to this format. Is there explicit format
> guide?
>
>
> Thanks a lot.
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
Re: Python Interface
Posted by Niclas Hedhman <ni...@hedhman.org>.
If you would like to flesh out the details, and want some help to make it a
bit more formal language (in case you struggle expressing yourself in
English), I'd be happy to assist to make it into a formal documentation
page (probably 2 diff pages) on it.
Niclas
On Tue, Jun 14, 2016 at 5:54 PM, zhuangmz08 <zh...@qq.com> wrote:
> Yes, I look at the samples before. I wrote this email to ensure whether
> there's a format guide.
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "Niclas Hedhman";<ni...@hedhman.org>;
> 发送时间: 2016年6月14日(星期二) 下午5:49
> 收件人: "dev"<de...@zest.apache.org>;
>
> 主题: Re: Python Interface
>
>
>
> Pandas DataFrame ??? No idea what that is...
>
> We have not written a Guide for the internal storage format of the
> MapEntityStore or even the ValueSerialization subsystem.
>
> But it is very straight forward; There are a handful of fields in the
> "root" object, i.e. metadata about the object, such as identity,
> lastModified, version number and so on. Then there are four fields in the
> root object named; properties, assocations, manyassociations,
> namedassociations, which contains entries with the "name" (the method name)
> as the key and the value being the serialized form of each of those states.
>
> It is pretty clear if you look at a capture sample;
>
> {
> "associations": {},
> "identity": "97d21d04-58c4-44a9-bd6c-1f861cf0a1f9-0",
> "modified": 1465718396917,
> "namedassociations": {},
> "type": "org.apache.zest.index.solr.SolrQueryServiceTest$TestEntity",
> "version":
> "MemoryEntityStoreService-d10f4fd5-da9a-4e56-9476-a1750c9509f10",
> "manyassociations": {},
> "properties": {
> "identity": "97d21d04-58c4-44a9-bd6c-1f861cf0a1f9-0",
> "name": "Hello World"
> },
> "application_version": "1.0"
> }
>
> In this example, there are no associations, but they are referencing
> Identities, directly, List or Map form. The properties here are very
> simple, only a
> Property<String> identity(); // part of the Identity interface
> Property<String> name(); // from somewhere...
>
> So, to use this in another platform should be pretty simple if there is
> JSON support.
>
> Indexing format is a lot more complex, and is very different between
> Indexing engines. There is no equivalent "unifying" intermediary, as we
> have in the MapEntityStore.
>
>
> Cheers
> Niclas
>
> On Tue, Jun 14, 2016 at 3:37 PM, zhuangmz08 <zh...@qq.com> wrote:
>
> > Hi,
> >
> >
> > I have some written python scripts, which consums data from former
> > database. Now, I would like to switch the former database into a domain
> > designed database, which is the mongo Map Entity Store. And I also like
> to
> > use ONLY one domain model across multi language platform.
> > I have some follwing questions:
> > 1. Is there any exist python interface to read database into pandas
> > DataFrame? I'm afraid not....
> > 2. If I write my own python interface, I would have to know the Entity
> > Format, since my interface exposes to this format. Is there explicit
> format
> > guide?
> >
> >
> > Thanks a lot.
>
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java
>
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java