Skip to content

Optimised prefix pattern per shard for remote store data and metadata files for higher throughput #362

Optimised prefix pattern per shard for remote store data and metadata files for higher throughput

Optimised prefix pattern per shard for remote store data and metadata files for higher throughput #362

Workflow file for this run

name: Auto triage based on the component label in issue
on:
issues:
types: [opened, reopened, transferred]
jobs:
apply-label:
if: github.repository == 'opensearch-project/OpenSearch'
runs-on: ubuntu-latest
steps:
- uses: actions/[email protected]
with:
script: |
const { issue, repository } = context.payload;
const { number, body } = issue;
const { owner, name } = repository;
const regex = /###\sRelated\scomponent\n\n(\w.*)\n/gm;
let match;
while ( ( match = regex.exec( body ) ) ) {
const [ , component_label ] = match;
await github.rest.issues.addLabels( {
owner: owner.login,
repo: name,
issue_number: number,
labels: [ `${ component_label }` ],
} );
}
github.rest.issues.addLabels({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
labels: ['untriaged']
})