[Feat/#220] 이미지 매칭 이름 기반 사전처리 도입 - #221
Conversation
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
#️⃣연관된 이슈
📝작업 내용
엑셀 분석 파이프라인의 이미지 매칭 단계에서, 상품명이 후보 썸네일 이름과 정확히 일치하는 경우까지 전량 AI에 태우던 것을 개선했다.
ExactThumbnailMatcher추가 — 상품명·후보 이름을 정규화(공백 축약·소문자화) 후, 같은 category 내에서 유일한 후보에만 확정 매칭. 동일 이름 후보가 여럿이면 모호한 것으로 보아 AI로 위임한다.ImportJobProcessor.matchAll에서 후보를 1회 로드해 exact 매칭을 선행하고, 잔여 항목만 기존 AI 매칭기(ProductImageMatcher)로 배치 호출한다. 잔여가 없으면 AI 호출 자체가 생략된다.GeminiProductImageMatcher프롬프트의 후보 목록을 자유 텍스트(id 1=애호박)에서 JSON 구조({"candidateId": 1, "name": "애호박"})로 변경해 AI가 식별하기 쉽게 하고, 응답 스키마의candidateId필드명과 통일했다.💬리뷰 요구사항(선택)