Views integration

I have a question for the main developers of External Entities module:
has it been discussed to create a Views Query Plugin for External Entities as @Berdir suggested 📌 Make Views use SqlEntityStorageInterface Needs work in the issue #2079019?

If yes: Did you see any issue for creating one? Has any work been started I could collaborate on?
If no: Why not? It would be much better than relying on Search API Views Query Plugin (no index to update, live data).

I've started to write a module to integrate External Entities with views: xnttviews → .

The dev version is already working as a "proof of concept". It needs many improvements for sure but at least, it shows it is possible. I would be very happy if other people could get involved in the development, don't hesitate to contact me!

I've changed the status to "Needs review" as I would like feedback from the maintainers regarding this initiative:
if you think "xnttviews" should be part of external entities (core), then change the status to "needs work" with some explanations/advice, if you think it's a good approach to separate views management and external entities, then maybe this issue could be "closed (won't fix)" and the external entities module page ("Known limitations" section) could be updated according to that.

@guignonv, I'm having a look at your xnttviews module out of curiosity. My original plan was to use external_entities exactly as described by @sylus in comment #4 , however despite having solr indexed content and following steps described here → no matter what I do I have so far been unable see results generated using the solr indexed values only. I haven't given up yet but it's been a grind for 3 days learning this ecosystem of modules and getting some results but hitting a wall.

video tutorial, I pretty much did this using views to provide the json data on the remote and I added his patches.
https://www.youtube.com/watch?v=tHGc6AdLzs4

I originally tried tagged releases then switched to these, similar issues.

releases used, all updated:

    "drupal/search_api": "dev-1.x",
    "drupal/search_api_autocomplete": "dev-1.x#925a16b1",
    "drupal/search_api_page": "^1.0",
    "drupal/search_api_solr": "dev-4.x",
    "drupal/external_entities": "^2.0@alpha",

Patches used:

    "drupal/external_entities": {
      "3376591 - Field mappings form section doesn't show a form element": "https://git.drupalcode.org/project/external_entities/-/merge_requests/25.patch",
      "3376604 - missing @return in docs": "https://www.drupal.org/files/issues/2023-08-10/3376604-9.patch",
      "2998391 - signel item from remote drupal views rest is wrapped in an array by default, add option to handle this": "https://www.drupal.org/files/issues/2019-07-03/2988391-3-views_rest_support.patch"
    },

The issue that I might focus on next is why the "Tracking" procedure doesn't complete. It still allows indexing despite the tracking not completed (there's an error, I'll debug that again after changing approach a few times).

I wonder if there's a recent regression in external_entities or search_api / search_api_solr that is causing problems retrieving content from solr.

I've indexed, have indexed content, have re-indexed many times, reviewed the configuration and re-consulted documentation.

I have
search_api 1.29
search_api_solr 4.3.0-alpha1
D9.5.x
PHP 8.1
solr 8.11

Three days so far on this, usually by now I'd have figured it out.

Looking at this now
https://www.drupal.org/docs/8/modules/search-api-solr/search-api-solr-ho... →

I have a search index view with a database back end working with external entities 3.x.

It seems like search api is a useful layer for synchronizing and storing data. Using a regular view would be simpler to set up, but likely needs more complex logic for syncing and caching?

My understanding at this point is that a view integration is intended for 3.x, but looks like that's not available yet.

Is the current consensus of the blockers pointing to an issue with how the storageclient handles paging?

I have not worked yet on merging xntt Views → to the v3. I plan to do it after the first beta release (probably in September/October). However, for testing, current implementation of xnttviews should work. I didn't check if I released the last modifications but you can try the dev code if I did not. I tested filtering and sorting on "native" external entities and it worked but the code needs to be "cleaned" (it was a quick and dirty :p ).

v3 Beta1 includes an experimental views plugin that I've tested with several storage clients, filters and ordering. I currently only noticed that table display does not allow column sorting but I'll work on that.

Looks good. See comment #24 on ✨ Fetch from drupal.org API Active .

Automatically closed - issue fixed for 2 weeks with no activity.