Copyright © 2008 Kaltura Inc.
All Rights Reserved. Designated trademarks and brands are the property of their respective owners.
Use of this web site constitutes acceptance of the Terms of Use and Privacy Policy.
famfamfam
I am having problems with filter:userIdEqual in v3 API.
When I use userIdEqual filter in list action (media, mixing or baseEntry service), the API always returns 0 result. Even I am sure the userId is existing and the userIdEqual is the only filter.
Does anyone else have the same problem?
Thanks.
Hi,
Where are all the kalturians?
Are you guys using Admin type KS or User type KS when requesting the list?
I am using Admin KS and filter:userIdEqual is not working for me.
User handling in API V3 included logical and DB changes in comparison to API V2.
As a result it is more efficient and provides better functionality in API V3. The downside is that it is not backward compatible. This means that filtering with API V3 for a user that was added using API V2 would not work, as you guys have seen.
We are thinking of creating a migration script for transferring from V2 to V3.
Bottom line:
API V3 & API V2 shouldn't be mixed when handling users.
Handling users in both API V3 and API V2 should work if using them exclusively.
Thanks for your answer. Zog.
However your answer brings me more concerns. There is no v2 and v3 compatibility issue addressed in any documents. So does this compatibility issue only happen to users data? Are there any other filters or data having the compatibility issues? If there are, we definitely need that to be documented.
Thanks.
Hi millsC,
In general we usually work hard to maintain backward compatibility.
However, the purpose of API v3 was to supply a better and more clear interface of what kaltura has to offer.
As part of the design and development of API v3 we decided on this change of the user management.
In the version currently on production (and in CE) no other compatibility issues should exists between the two APIs,
and if you find something that doesn't make sense to you please let us know because it will probably be something we'd want to look into.
Regarding documentation - we constantly try to improve in that area, but at the moment we don't have any specific documentation regarding changes between the twp APIs.
hope that reduces your concerns a bit.
Gonen
I'm having exact problem, even though i added users with api_v3, and sure that user exists:
and
however
brings me
i wonder what the heck, and how to fix that?
i just tried this on testMe console, same results.
Is there some solution to this?. I have the same problem.
it seams to be a general KalturaMediaEntryFilter issue in api v.3.0
$filter->userIdEqual = '31339';
or $filter->tagsLike = 'xxx';
want work for me too.
Any ideas?
It seems strange to me, because if this is a bug, then it is a BIG bug.
Is there another way to get user medias? If there is not, i think to query database directly (beautiful). I have no other ideas.
Hi All,
I am also having the same problem. And I have double checked the user is registered and I can even update the user. But when I filter by user id it returns 0 result. I even tried on Test me console. When I return all the result it shows the video posted by the specific user and also shows its user id in result. But when I filter by user id it shows 0 result.
Please can anybody help me out.
Thanks in advance.