Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Do you have any particular motivation behind adding it? Not opposed (we use it in Kickstart 2.x), but the primary reason to include it on Drupal based REST servers in the past was likely to create collection resources powered by Views / Search API. I'm not a huge fan of configurable collections (makes it much harder to maintain a uniform querying interface across all collection resources), but it could always serve as the backend querying interface as a raplacement for what I've done with EntityFieldQuery in Commerce Services.
Perhaps you're thinking of it more from a consumption standpoint? Indexing remote data locally?
Comments
Comment #1
rszrama CreditAttribution: rszrama commentedDo you have any particular motivation behind adding it? Not opposed (we use it in Kickstart 2.x), but the primary reason to include it on Drupal based REST servers in the past was likely to create collection resources powered by Views / Search API. I'm not a huge fan of configurable collections (makes it much harder to maintain a uniform querying interface across all collection resources), but it could always serve as the backend querying interface as a raplacement for what I've done with EntityFieldQuery in Commerce Services.
Perhaps you're thinking of it more from a consumption standpoint? Indexing remote data locally?
Comment #2
niccolox CreditAttribution: niccolox commentedyes, I am thinking consumption of REST and then serving it out, and so, that's maybe not something your doing right now
I am thinking of making a Search API Nutch Solr module for the Big Data Drupal project
that is ;
Cloudera stack (Hadoop + MapReduce) Nutch job > Solr (Aegir / Jetty ) > Drupal Apache Solr or Search API modules > Drupal Views
another possibility for consumption is HBASE > Drupal via REST
I'll write a post on a sandbox that covers these various research ideas
cheers