Unsolved
This post is more than 5 years old
6 Posts
0
1180
June 2nd, 2011 02:00
Centera Queries - Doubts
Hi Guys,
First of all, sorry for my bad english.
Nowdays whe are working with Centera and we are very greatfull about that, it seems a robust and efficient storage system. But know we are facing with searches and i have a lot of doubts.
I read all the api about the Centera SDK.And I understand that queries are very "expensive" to do. That by default you can only do ten searches at once, and if there are a lot of files in Centera the cost will be very high.
When i create a FclipFile i put some DescriptionsAtributes in it. Like this:
theClip.setDescriptionAttribute("key","value"); ( We understand that this descriptionAtributte is like a metadata in a document).
- They are not indexed in Centera?.
- The way to look in this DescriptionAtributtes is making a query?
- Which is the best way to making this type of queries?.
- It will be expensive like it is describe it in the page 30-31-32 pages of the Centera_API (Centera_SDK_B1_D.0_Prog_Guide.pdf)?.
I'm a bit lost in this issue, could i find some usefull documentacion or advice me to go in the good direction?
Than you in advance.
Best Regards,
Alfredo.
gstuartemc
2 Intern
•
417 Posts
0
June 2nd, 2011 05:00
Alfredo - the code samples that come with the SDK show you how to retrieve clip level attributes via query. These come with the C and Java SDK (and .Net versions are also included if you are using the SourceForge .Net wrapper for the SDK).
10 Queries is on the high side - I would not ever recommend more than 5 concurrent queries in total running against a cluster. As you already seem to understand, Query is a very intense operation on the cluster and should not be used as part of general day-to-day processing. It is aimed at Disaster Recovery or bulk batch tasks that would typically run once a day. It should in no ways be viewed as being able to be used like a SQL database!!
You can only query using a time range, but (as demonstrated in the samples) you can include clip level attributes in the result set that comes back. This will alllow you to "filter" out the ones you are interested in by examing these attributes without having to open the clip.
I hope that helps!