Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(server): reduce importer transaction time #1380

Merged
merged 2 commits into from
Jan 29, 2025

Conversation

yk-eukarya
Copy link
Contributor

@yk-eukarya yk-eukarya commented Jan 29, 2025

Summary by CodeRabbit

  • Refactor
    • Simplified and restructured the item import method to improve clarity and organization.
    • Streamlined error handling and control flow within the import process.
    • Removed nested function complexity to create a more linear execution path, enhancing maintainability.

@yk-eukarya yk-eukarya self-assigned this Jan 29, 2025
Copy link
Contributor

coderabbitai bot commented Jan 29, 2025

Walkthrough

The changes focus on refactoring the Import method in the Item struct within the server/internal/usecase/interactor/item.go file. The primary modification involves restructuring the method's internal logic to eliminate a nested function and create a more linear, straightforward execution flow. The refactoring aims to improve code readability and maintainability by flattening the control flow and simplifying error handling and event creation processes.

Changes

File Change Summary
server/internal/usecase/interactor/item.go Refactored Import method to remove nested function Run1, adjust error handling, and streamline metadata handling, enhancing readability and maintainability.

Poem

🐰 A Rabbit's Refactoring Tale 🔧

Nested functions, once tangled and tight,
Now dance in a sequence, clear and bright.
Code flows like a river, smooth and clean,
Complexity fades, a programmer's dream.
Simplicity triumphs, with logic so clear! 🌟

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Jan 29, 2025

Deploy Preview for reearth-cms canceled.

Name Link
🔨 Latest commit 8a5a1f2
🔍 Latest deploy log https://app.netlify.com/sites/reearth-cms/deploys/6799fecab406a70008eb9d5d

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
server/internal/usecase/interactor/item.go (3)

374-409: Consider consolidating error handling for data retrieval.

The data retrieval section could benefit from a helper function to reduce repetitive error handling patterns. Consider extracting the project, model, and items retrieval into a helper function.

+func (i Item) retrieveImportData(ctx context.Context, param interfaces.ImportItemsParam) (
+    *schema.Schema,
+    *project.Project,
+    *model.Model,
+    item.VersionedList,
+    item.VersionedList,
+    error,
+) {
+    s := param.SP.Schema()
+    prj, err := i.repos.Project.FindByID(ctx, s.Project())
+    if err != nil {
+        return nil, nil, nil, nil, nil, err
+    }
+
+    m, err := i.repos.Model.FindByID(ctx, param.ModelID)
+    if err != nil {
+        return nil, nil, nil, nil, nil, err
+    }
+
+    itemsIds := lo.FilterMap(param.Items, func(i interfaces.ImportItemParam, _ int) (item.ID, bool) {
+        if i.ItemId != nil {
+            return *i.ItemId, true
+        }
+        return item.ID{}, false
+    })
+    oldItems, err := i.repos.Item.FindByIDs(ctx, itemsIds, nil)
+    if err != nil {
+        return nil, nil, nil, nil, nil, err
+    }
+
+    metaItemsIds := lo.FilterMap(param.Items, func(i interfaces.ImportItemParam, _ int) (item.ID, bool) {
+        if i.MetadataID != nil {
+            return *i.MetadataID, true
+        }
+        return item.ID{}, false
+    })
+    oldMetaItems, err := i.repos.Item.FindByIDs(ctx, metaItemsIds, nil)
+    if err != nil {
+        return nil, nil, nil, nil, nil, err
+    }
+
+    return s, prj, m, oldItems, oldMetaItems, nil
+}

Line range hint 450-599: Consider breaking down the import logic into smaller functions.

The import logic is complex and could benefit from being split into smaller, focused functions for better maintainability and testability. Consider extracting the following operations:

  • Strategy handling
  • Metadata processing
  • Reference field updates
+func (i Item) handleImportStrategy(
+    param interfaces.ImportItemsParam,
+    oldItem *item.Item,
+) (interfaces.ImportStrategyType, error) {
+    if param.Strategy == interfaces.ImportStrategyTypeInsert && oldItem != nil {
+        return param.Strategy, nil
+    }
+    if param.Strategy == interfaces.ImportStrategyTypeUpdate && oldItem == nil {
+        return param.Strategy, nil
+    }
+    if param.Strategy == interfaces.ImportStrategyTypeUpsert {
+        if oldItem != nil {
+            return interfaces.ImportStrategyTypeUpdate, nil
+        }
+        return interfaces.ImportStrategyTypeInsert, nil
+    }
+    return param.Strategy, nil
+}

604-644: Consider batching event creation.

The event creation loop could be optimized by batching the database operations for referenced items.

+func (i Item) createBatchEvents(
+    ctx context.Context,
+    items item.VersionedList,
+    itemsEvent map[item.ID]itemChanges,
+    prj *project.Project,
+    s *schema.Schema,
+    m *model.Model,
+) ([]Event, error) {
+    var events []Event
+    // Batch fetch all referenced items
+    allFields := items.Fields()
+    refItems, err := i.getReferencedItems(ctx, allFields)
+    if err != nil {
+        return nil, err
+    }
+    
+    for k, changes := range itemsEvent {
+        vi := items.Item(k)
+        it := vi.Value()
+        
+        eType := event.ItemCreate
+        if changes.action == interfaces.ImportStrategyTypeUpdate {
+            eType = event.ItemUpdate
+        }
+        
+        events = append(events, Event{
+            Project:   prj,
+            Workspace: s.Workspace(),
+            Type:      eType,
+            Object:    vi,
+            WebhookObject: item.ItemModelSchema{
+                Item:            it,
+                Model:           m,
+                Schema:          s,
+                GroupSchemas:    param.SP.GroupSchemas(),
+                ReferencedItems: refItems,
+                Changes:         item.CompareFields(it.Fields(), changes.oldFields),
+            },
+            Operator: operator.Operator(),
+        })
+    }
+    return events, nil
+}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 19a4a58 and 68d5580.

📒 Files selected for processing (1)
  • server/internal/usecase/interactor/item.go (3 hunks)
🧰 Additional context used
🪛 golangci-lint (1.62.2)
server/internal/usecase/interactor/item.go

602-602: ineffectual assignment to err

(ineffassign)

🪛 GitHub Check: ci-server / lint
server/internal/usecase/interactor/item.go

[failure] 602-602:
ineffectual assignment to err (ineffassign)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: ci-server / test
🔇 Additional comments (2)
server/internal/usecase/interactor/item.go (2)

368-371: LGTM! Proper permission validation.

The permission check is correctly placed at the start of the function, ensuring early validation of workspace access rights.


420-448: Enhance schema mutation validation.

The schema mutation logic should validate field types more thoroughly and ensure compatibility with existing data.

Run this script to check for potential field type conflicts:

for k, changes := range itemsEvent {
vi := items.Item(k)
it := vi.Value()
runRes, err := Run1(ctx, operator, i.repos, Usecase().Transaction(), f)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix ineffectual error assignment.

The error assignment on line 602 is ineffectual as it's immediately overwritten.

-runRes, err := Run1(ctx, operator, i.repos, Usecase().Transaction(), f)
+runRes, runErr := Run1(ctx, operator, i.repos, Usecase().Transaction(), f)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
runRes, err := Run1(ctx, operator, i.repos, Usecase().Transaction(), f)
runRes, runErr := Run1(ctx, operator, i.repos, Usecase().Transaction(), f)
🧰 Tools
🪛 golangci-lint (1.62.2)

602-602: ineffectual assignment to err

(ineffassign)

🪛 GitHub Check: ci-server / lint

[failure] 602-602:
ineffectual assignment to err (ineffassign)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
server/internal/usecase/interactor/item.go (1)

602-605: ⚠️ Potential issue

Fix ineffectual error assignment.

The error assignment is ineffectual as noted by the linter.

Apply this fix:

-runRes, err := Run1(ctx, operator, i.repos, Usecase().Transaction(), f)
+runRes, runErr := Run1(ctx, operator, i.repos, Usecase().Transaction(), f)
 if err != nil {
     return interfaces.ImportItemsResponse{}, err
 }
🧹 Nitpick comments (3)
server/internal/usecase/interactor/item.go (3)

374-409: Consider enhancing error handling for database operations.

While the error handling is generally good, consider wrapping database errors with more context to aid in debugging:

 prj, err := i.repos.Project.FindByID(ctx, s.Project())
 if err != nil {
-    return interfaces.ImportItemsResponse{}, err
+    return interfaces.ImportItemsResponse{}, fmt.Errorf("failed to find project: %w", err)
 }

Line range hint 450-599: Enhance error messages for better debugging.

Consider adding more descriptive error messages for common failure scenarios during import:

 if param.Strategy == interfaces.ImportStrategyTypeUpdate && !operator.CanUpdate(oldItem) {
-    return interfaces.ImportItemsResponse{}, interfaces.ErrOperationDenied
+    return interfaces.ImportItemsResponse{}, fmt.Errorf("%w: user cannot update item %s", interfaces.ErrOperationDenied, oldItem.ID())
 }

607-649: Consider optimizing event processing.

The event handling could be optimized by:

  1. Batching database queries for referenced items
  2. Processing events in parallel where possible

Example optimization:

-for k, changes := range itemsEvent {
+// Batch fetch all referenced items
+allRefItems, err := i.getReferencedItems(ctx, lo.FlatMap(items, func(item item.Versioned) []*item.Field {
+    return item.Value().Fields()
+}))
+if err != nil {
+    return interfaces.ImportItemsResponse{}, err
+}
+
+for k, changes := range itemsEvent {
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 68d5580 and 8a5a1f2.

📒 Files selected for processing (1)
  • server/internal/usecase/interactor/item.go (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: ci-server / test
🔇 Additional comments (3)
server/internal/usecase/interactor/item.go (3)

368-371: LGTM! Early permission validation is well implemented.

The code properly validates workspace permissions before proceeding with the import operation.


411-418: LGTM! Well-structured change tracking implementation.

The use of a custom struct to track item changes is a clean and efficient approach.


420-448: Ensure schema mutations are transaction-safe.

While the schema mutation logic is thorough, consider adding explicit checks to ensure schema updates are atomic and consistent within the transaction.

Run this script to check for potential transaction issues:

@yk-eukarya yk-eukarya merged commit f6abbfc into main Jan 29, 2025
24 checks passed
@yk-eukarya yk-eukarya deleted the chore/reduce-impoter-transaction-time branch January 29, 2025 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant