Skip to content

Handle overlong content more gracefully #31

Description

@jplitza

As an app user, I want to index huge documents.

Both MySQL and PostgreSQL have maximum column content lengths. The app should detect those and act appropriately.

Possible solutions (in decreasing order of preference):

  1. Split the content into chunks and index all of them separately.
  2. Truncate the content and index only the first part, throwing an indexing warning.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions