May 15 - Production release 0.5.3
- End Points, Geocode, Geopulse, World Geographies released
- Multi-query support officially released
- Logged in users no longer are required to periodically submit CAPTCHAs to access endpoints
- A number of reliability updates
Known issues:
- Variants field in World Geographies is a JSON array rather than fully formed JSON
- Geocode is limited outside of the US (and non-functional outside of supported countries)
May 9 - Production release 0.5.2
- End Points beta
- Location beta
- Pulse beta
- Update to q parameter to properly handle mixed spaces and commas ("foo,phi fum,rum" will properly search for "foo" or "phi fum" or "rum").
May 2 - Production release 0.5.1
- Properly catching and returning error messages on a number of invalid parameter conditions
- Pass-through all error messages for multi calls
- in restaurants-us, 24_7 is being updated to open_24hrs due to a conflict with Solr.
- Many stability and debugging additions to the backend
Apr 24 - Production release 0.4.4
- Consumer Packaged Goods database released
Apr 17 - Production release 0.4.3
- GetSatisfaction has replaced Google Groups for support
- A number of updates to the Data Preview tool including:
- Ability to undo filtering on facets
- Total row count is displayed
- Descriptions for all tables added
- Facets API is now live
Apr 5, 2012 - Production release 0.4.1
- V3 is now live!
- Completely new website accompanies the site going live, with self-serve key generation
Mar 26, 2012 - BETA release 0.4.0
- A lot of under-the-hood changes
- Resolved an error with $blank filter behavior
- Resolved an issue with searches on locality failing
- Resolved an issue with $in failing with arrays
Feb 14, 2012 - BETA release 0.3.10
Updates
- KEY param is no longer required
- Cleaner 401 error messaging
- Resolved a number of RPD and offset limit check problems
- Do not return row count of 0 when include_row is not specified
Feb 7, 2012 - BETA release 0.3.9
Updates
- Support for Multi-requests added
- alpha release of Node.js API implementation
Jan 19, 2012 - BETA release 0.3.8
Updates
- All internal updates
Jan 11, 2012 - BETA release 0.3.7
Updates
- Large batch of performance improvements release.
- Resolve speed is improved by 100%
- Search is improved by 50%
Dec 28, 2011 - BETA release 0.3.6
Updates
- more performance improvements
Dec 20, 2011 - BETA release 0.3.5
Updates
- performance updates
Dec 13, 2011 - BETA release 0.3.4
Updates:
- Global dataset added to V3
- US Restaurants added to V3
Dec 6, 2011 - BETA release 0.3.3
Updates:
- alpha support for facetting
- Data Preview tool released (http://demos.factual.com/data_preview)
Nov 29, 2011 - BETA release 0.3.2
Updates:
- More stability improvements
Nov 23, 2011 - BETA release 0.3.1
Updates:
- Stability improvements
- Shortened view IDs
Nov 15, 2011 - BETA release 0.3.0
Updates:
- This is a big release, thus the jump to 0.3.0
- The permissions system was very nearly rewritten. Performance should be a LOT faster.
- A couple hot-fixes so far:
- OAuth signing properly accepts optional parameters oauth_version, oauth_token and oauth_body_hash
- We got a little overly agressive scrubbing response headers. Headers now include some basics that some systems depend on (accept-encoding, content-type, etc.)
Nov 1, 2011 - BETA release 0.2.1
Updates:
- All backend issues
- Added documentation for API limits
- Updated root page of documentation (this one!) to try to orient developers more quickly (feedback desired!)
- Input and Flag API calls in alpha.
New known issues
- A number of users are reporting receiving 403 errors prematurely. This includes users receiving throttle errors on their very first request.
Oct 27, 2011 - BETA release 0.2.0
Updates:
- Fixed an index issue whereby stemming was occurring at the wrong point. ApplePan could find "Appl" but not "Apple".
Oct 19, 2011 - BETA release 0.1.9
Updates:
- Fixed known issue whereby ALL errors were returning as 500
- Various updates to Resolve
Oct 10, 2011 - BETA release 0.1.8
Updates:
- First release of Resolve API
- Fixed problem where offset wasn't working for Crosswalk
Sep 28, 2011 - BETA release 0.1.7
Updates:
- Removed the canonical name for each field from the list of aliases to each field (since they were redundant).
- Fixed problem whereby OAuth signed requests were always being denied under certain configurations.
- Fixed schema call not responding (configuration mistake)
- Added schema_last_updated to schema
- Added various health checks to back end
Sep 21, 2011 - BETA release 0.1.6
Updates:
- Clearer error messages for 401 errors
- Each field in a table now supports an english-readable description of what the field contains (visible in the schema call).
Sep 13, 2011 - BETA release 0.1.5
Updates:
- Schema now includes geo_enabled
- Numerous back-end fixes for logging/reporting/administration
Sep 8, 2011 - BETA release 0.1.4
Updates:
- AND and OR are properly supported in the "q" parameter for /read
- Schema now includes fulltext_searchable
- response.view.fields is now an array of hashes instead of an array of arrays
- Exceptional limits for OAuth signed calls were throwing 403 errors instead of being respected. This is fixed.
New known issues:
- Schema is still missing schema_last_updated and geo_enabled
Aug 31, 2011 - BETA release 0.1.3
Updates:
- OAuth errors that can be fixed with proper credentials return HTTP 401 status rather than 403, as per the HTTP Specification.
- Updated an error whereby error messages from previous requests were being cached and messaged to subsequent requests
Aug 23, 2011 - BETA release 0.1.2
Updates:
- Fixed a problem where OAuth requests containing single quotes (URL encoded or not) would always fail.
- Fixed a problem where custom limits were being ignored for signed OAuth requests.
- OAuth error messages updated to match documentation
- Unrecognized parameter message updated to match documentation
- $distance and $relevance can now be specified in the sort parameter for reads.
- Schema method is now implemented
- Full-text search tweaked to provide more weight towards names. (Searching for "Starbucks" would previously show things in "Starbuck City" before it showed the well known coffee shop before).
- Aaron's Clojure SDK for the Factual API
- Added a quick tutorial on using Apigee due to common head-scratching
- Default sort for Crosswalk calls is now namespace
- Documentation updated to list which namespaces include namespace_id data
New known issues:
- Schema call is missing an array of the field IDs present
- Schema call is missing search_enabled and geo_enabled
- Schema call is missing schema_version
Aug 8, 2011 - BETA release 0.1.1
For this first release:
- Only U.S. Places is supported
- GET is the only supported API call (for filtered reads from place data)
- Support for Crosswalk and Crossref are built
- seed namespaces supported are here
Known issues:
- Currently limit and offset overrides for OAuthenticated users are not being respected (results in a 403)
- $distance and $relevance are not present as originally defined in the documentation
- Current Crossref contains is_canonical, which will be deprecated in the next release
- Some Foursquare data in Crosswalk appear to have the venue ID listed in the Foursquare url, but not broken out in the namespace_id field.
- Foursquare venue IDs are using the older sequential IDs, not their new UUID style IDs.
Labels