tanishqgandhi1908 opened a new pull request, #7930:
URL: https://github.com/apache/texera/pull/7930

   ### What changes were proposed in this PR?
   
   Models had metadata and access APIs but no discovery: they were missing from 
the hub's
   counts, likes, views, tops and user-access endpoints, and from unified 
search.
   
   - Schema: `model_user_likes`, `model_view_count`, and `model` added to the 
PGroonga block.
     `texera_ddl.sql` builds that index only for a fresh database, so `42.sql` 
creates it as
     well — closing for models the gap datasets still have on migrated 
databases.
   - `EntityType.Model` plus one `EntityTables` registry entry wires up every 
hub endpoint.
   - `VersionedResourceTables.ModelTables` and `ModelSearchQueryBuilder` add 
search. The
     builder is a projection only; `framework` and `format` are the sole new 
union slots, and
     the rest are shared with the other versioned resources.
   - `DashboardResource` gains the `model` entry slot, a `modelId` filter, the 
query and
     `toEntry` cases, and models in `hasMismatch`. `getTops` needed no change — 
the descriptor
     path picks models up on its own.
   
   Model search matches on name and description, so the indexed expression is 
identical to the
   predicate the builder renders; `framework` and `format` are projected for 
display, not
   indexed.
   
   ### Any related issues, documentation, discussions?
   
   Part of #6501 (umbrella #6494). Builds on #7928, and takes migration 42 
because #6872 and
   #7922 hold 41 — their commits show in the diff until they merge.
   
   ### How was this PR tested?
   
   `WorkflowExecutionService/testOnly *dashboard*` — 498/498 across 27 suites, 
31 of them new:
   a `ModelSearchQueryBuilderSpec` pinning the projection, access scoping and 
id filter; model
   cases in `VersionedResourceTablesSpec`, `EntityTablesSpec`, `EntityTypeSpec` 
and
   `HubEntityModelSpec`; and hub coverage in `HubResourceSpec` for likes, 
unlikes, view counts,
   `getCounts`, `getTops` and `user-access`, including id collisions across all 
three entity
   types. `42.sql` was applied twice against a local Postgres for idempotence, 
and
   `idx_model_pgroonga` renders the same shape as `idx_dataset_pgroonga`.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 5)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to