Skip to content

General

General

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

36 results found

  1. Support for GraphQL Interfaces or Union Types through the built in GraphQL schema builder tool. This was extensively discussed in the Google Chat group.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Postgres support jsonb column that can store arbitrary jsonb objects, very suitable to store unstructured / semi-structured API output.

    Postgres also supports index on fields within jsonb.

    Can data connect support jsonb column? Mapping fields of API object to Postgres columns can be a headache

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Support AlloyDB as a datasource for Data Connect in addition to Cloud SQL via the same PostgreSQL bindings

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. On top of common scalars such as Email, Phone, etc., custom scalars are defined by developers on the client-side application, with logic for marshaling and unmarshalling the data provided, which could be either a class with the two methods or a couple of functions.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Create and store advanced embeddings for Data Connect types in pgvector through support of configurable chunking strategies and automatic embedding by annotations.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. It would be nice if we can set our custom Postgres instance connection string so that we can use postgres instances outside the Google Cloud infrastructure.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Add GeoPoint and GeoBox scalar types and enable rich geo searching queries including indexing, "search within area", "find closest to point within radius", etc.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. I love that data connect supports {.._expr: "auth.uid"} to define server value based on Firebase auth token.

    What about other CEL operations?

    I want the ability to perform simple transformation using GraphQL variables, Firebase auth token and current timestamp. For example: _expr: "'hello from ' + auth.email"

    I want the ability to combine data from different sources. Like execute a query and then use its result to perform another query or mutation. CEL expression can help cross reference data in previous steps.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Support Cloud Spanner as a datasource for Data Connect in addition to Cloud SQL via Cloud Spanner's PostgreSQL compatibility layer.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Connect  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Allow connections to PostgresSQL instances in other projects using Shared VPC, etc.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Currently only PostgreSQL is supported, but we are also highly interested in mysql support. Would love to see it on the roadmap.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Connect  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. The automatic custom schema migrations are great, but when managing an API expressed almost explicitly by the schema, there needs to be a clear dev story of how to migrate the database schema yourself, and move data in custom ways, while still allowing the exposed api to be backwards compatible. This can be very challenging with automatic migrations.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Connect  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Instead of only being able to select embedding models from Vertex AI (e.g. Gecko), it'd be great to be able to pass in any embedder imported from Genkit plugins like genkitx-openai-plugin or genkitx-cohere

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Connect  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Add deeper integration with Vertex AI to Data Connect, for example allowing direct LLM content generation and simple RAG use cases.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Connect  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?