FQL and SpringSocialFacebook

[Rob Blair]

I saw the task https://jira.springsource.org/browse/SOCIALFB-8 targeted at 1.1.0 release, and wondered how it was going.

I'm about to start diving in to some serious FQL work, and wanted to be sure it going well.
Might also need to use the multi-query functionality, which makes an even more crazy api.

Has anybody out there made model classes to hold the data from various tables?
In particular, for the FQL stream table.

Thanks in advance,

[habuma]

Well, there's an initial bit of FQL work in the latest snapshots. Specifically, FqlOperations give you a method with this signature:

<T> List<T> query(String fql, FqlResultMapper<T> mapper);

Essentially, you pass in whatever FQL you want along with your implementation of the FqlResultMapper and it will return whatever type the result mapper returns. For example, here's some code from the FqlTemplateTest:

List<StatusObject> results = facebook.fqlOperations().query("SELECT uid, status_id, message, time, source FROM status WHERE uid=me()", new FqlResultMapper<StatusObject>() {
	public StatusObject mapObject(FqlResult result) {
		StatusObject status = new StatusObject();
		status.uid = result.getInteger("uid");
		status.statusId = result.getString("status_id");
		status.statusIdLong = result.getLong("status_id");
		status.message = result.getString("message");
		status.time = result.getTime("time");
		status.source = result.getLong("source");
		return status;
	}
});

It doesn't yet support multi-query (I envision that being a case where you send in a Map<String, String> of queries instead of a simple String), but single queries should work fine. AFAIK, I'm the only one who has tested this, so I welcome you to try it out and let me know what's missing or doesn't work (aside from multi-query, which I already know about).

[Rob Blair]

OK, I'll certainly give it a peek.
As for the mapObject logic, I'm tempted to add in more of the full jackson mapping logic. Many of the tables have complex sub-elements, which will start being more and more cumbersome to create mappers, each time.

Also thinking of having some cheats for SELECT strings for the basic case of 'return everything', per FQL table.
The multi-query would also need to be intelligent about partial failures.

Thanks,
me

[habuma]

Sounds good. I was wondering about nested elements in the return, but on my cursory review of the tables, I couldn't find an example...so I initially assumed a flat structure. Could you give me an example of a table that has more complex sub-elements that would require more detailed JSON-mapping? Not doubting you...just want to see what it looks like.

If you find opportunity for improvement, I always welcome pull requests!

[Rob Blair]

http://developers.facebook.com/docs/...ce/fql/stream/ has the data for the stream table, which is the wall / home type feed.

comments array
An array containing the following information about comments for a post:

can_remove (bool): Indicates whether users can remove comments
can_post (bool): Indicates whether users can post comments
count (int): The total number of comments added to the post
comment_list (array): A sample of comments made on the post, to get the full list of comments, use the Post Graph API object or query the comment FQL table

and a few others. The documentation is somewhat thin, so your guess is as good as mine.
I'll give you more specifics as I walk down that path.

[Rob Blair]

Comment about FqlResult: Most of the calls to getX return null if it's not present in the object map;
However, getTime will throw an exception.

	
public Date getTime(String fieldName) {
	try {
		long timeInMilliseconds = Long.valueOf(String.valueOf(resultMap.get(fieldName))) * 1000;
		return resultMap.containsKey(fieldName) ? new Date(timeInMilliseconds) : null;
	} catch (NumberFormatException e) {
		throw new FqlException("Field '" + fieldName +"' is not a time.", e);
	}
}

I believe Long.valueOf will be the culprit, as "null" will not parse.
The API should be consistent in how it treat missing (as opposed for malformed) map entries.