First off, let me say that the Java Data Source Library is awesome. I had actually implemented the non-optional parts of the data source spec and was starting on parsing for the query language when I heard about the library at Google I/O. The API was easy and straightforward enough that I managed to swap out most of our implementation for Google's while sitting in the audience at I/O.
The only place the library fell short for me was in specifying the Capabilities of my DataTableGenerator. I'm building on top of a very basic data store with hundreds of numeric columns, so I'd really like the library to handle all of the aggregation, grouping, pivoting, etc. for me. However, I'd still like to see the incoming query so I can load the correct columns from the back end data store. Unfortunately, the library splits the query into parts it handles (which is everything, with Capabilities.NONE) and the part the DataTableGenerator handles (which is nothing). If I instead specify Capabilities.SELECT, I receive the SELECT part of the query, but I can no longer use the library to handle the aggregation functions (sum, avg, etc). I can work around this by parsing the entire query from the request and manually getting the columns from it; however, this seems like a less-than-ideal situation, especially since we end up performing both the parsing and the row-filtering twice. Ideally, there would be a more fine-grained Capability where I would receive a simple list of the columns that the library wants, and the library would handle the rest. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en -~----------~----~----~----~------~----~------~--~---
