Hi Paula, Thank you for your comment.
I would like to discuss the API document in the community, and to build a consensus to the specification. I saw your comments at the Wiki discussion page, and we also think these points are very important. > Suggestion about Data Types Certainly, we should be able to deduce the type for supporting more types of user defined metadata, and it sounds good for me to make some conventions to support deducing data types. # In our team, we discuss about a plan of using value conventions, # like "50d" for integer 50, "1.000f" for float 1.000 and so on. On the other hand, we should discuss this topic carefully, because any conventions may cause some limitations on users, we think. > Suggestion regarding System Metadata I agree, and I think we should specify the minimal set of attributes. We should reconsider system metadata which are part of proposal, based on attributes which are part of Swift and which we are really necessary. # For example, Attributes that relate to object CORS are not part of Swift, # and don't seems so necessary for us. Controlling which attributes are indexed also sounds good to me. Best regards, Yuji Hagiwara NTT DATA Corporation On Tuesday, September 02, 2014 9:45 PM, Paula Ta-Shma <[email protected]> wrote: > Hi, > > Great to see some renewed interest in metadata search for Swift. We are > working on this, and would be glad if there is renewed interest from the > community. > I saw your comments on thew wiki discussion page and they look good to me. I > just added some additional comments about Data Types and System Metadata to > the same page (I posted these to the mailing list a while back). > > Best regards > Paula > > Paula Ta-Shma, Ph.D. > Storage Research > IBM Research - Haifa > Phone: +972.3.7689402 > Email: [email protected] > > > > > From: <[email protected]> > To: <[email protected]>, > Cc: <[email protected]>, Paula Ta-Shma/Haifa/IBM@IBMIL, > <[email protected]>, <[email protected]>, <[email protected]>, > <[email protected]> > Date: 02/09/2014 12:54 PM > Subject: [Swift] Proposal for improving Metadata Search API > ________________________________________ > > > > Hi, > > At NTT Data, we work on system development projects with Swift. > Recently we have big interest in the metadata search feature of Swift, and > now we're planning to construct a search function into Swift. > > I checked some materials on wiki page > http://wiki.openstack.org/wiki/MetadataSearch to consider a detailed plan. > I found some discussions about the metadata search, but I cannot find any > information about recent progresses. > Is there any progresses about the metadata search ? > > I also checked the API document > http://wiki.openstack.org/wiki/MetadataSearchAPI to make the specification of > our metadata search based on community's standard, and I think this > specification has a full featured API. > However, the detail formats of HTTP request and HTTP response, such as > headers and response codes, are not clearly defined in this specification. > > These formats about a HTTP message are necessary for implementations of > clients, and without strict definition, clients may get confused. > > I added my suggestions about HTTP headers and response codes to the Wiki > discussion page https://wiki.openstack.org/wiki/Talk:MetadataSearchAPI > Does anyone have comments? > > p.s. I also found some typos in the chapter 10 and fixed them. > > Best regards, > > Yuji Hagiwara > NTT DATA Corporation > _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
