why not use reflect to get InternalEngine and IndexWriter?

Open
#28 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
elasticsearch, java
Domain
search

Research direction

Start by locating where ES-Fastloader obtains or depends on Elasticsearch's InternalEngine and IndexWriter, then review the Elasticsearch source changes currently required. Determine whether reflection can replace those modifications without breaking the index-building flow. Done means the approach is documented and validated as a workable alternative, or its limitations are clearly recorded.

Written by the indexing model from the issue text.

Description

if use reflect to get InternalEngine and IndexWriter, we need not modify elasticsearch source code

Dominant language
Java
Stars
272
Forks
88
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from didi/ES-Fastloader

All issues in didi/ES-Fastloader

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.