Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / ldbc/ldbc_finbench_docs issues and pull requests
#50 - Refine the returned result
Issue -
State: closed - Opened by qishipengqsp about 2 years ago
#49 - simple-read and write query have some question
Issue -
State: closed - Opened by BingTong0 about 2 years ago
- 1 comment
#49 - simple-read and write query have some question
Issue -
State: closed - Opened by BingTong0 about 2 years ago
- 1 comment
#48 - acid has some error
Issue -
State: closed - Opened by BingTong0 about 2 years ago
#48 - acid has some error
Issue -
State: closed - Opened by BingTong0 about 2 years ago
#47 - add acid test chapter
Pull Request -
State: closed - Opened by qingfeng14 about 2 years ago
- 1 comment
#47 - add acid test chapter
Pull Request -
State: closed - Opened by qingfeng14 about 2 years ago
- 1 comment
#46 - put funcation result as a name
Issue -
State: closed - Opened by BingTong0 about 2 years ago
- 2 comments
#46 - put funcation result as a name
Issue -
State: closed - Opened by BingTong0 about 2 years ago
- 2 comments
#45 - Complex-Read Query Have Some Question
Issue -
State: closed - Opened by BingTong0 about 2 years ago
- 2 comments
#45 - Complex-Read Query Have Some Question
Issue -
State: closed - Opened by BingTong0 about 2 years ago
- 2 comments
#44 - specify the default values of truncation design
Issue -
State: closed - Opened by qishipengqsp about 2 years ago
#44 - specify the default values of truncation design
Issue -
State: closed - Opened by qishipengqsp about 2 years ago
#43 - specify the read-write queries' description and provide diagrams
Issue -
State: closed - Opened by qishipengqsp about 2 years ago
#43 - specify the read-write queries' description and provide diagrams
Issue -
State: closed - Opened by qishipengqsp about 2 years ago
#42 - Fix the typo errors in #41
Pull Request -
State: closed - Opened by qishipengqsp about 2 years ago
#42 - Fix the typo errors in #41
Pull Request -
State: closed - Opened by qishipengqsp about 2 years ago
#41 - [Format] Doc has some format or type errors.
Issue -
State: closed - Opened by zhengJade about 2 years ago
- 1 comment
#41 - [Format] Doc has some format or type errors.
Issue -
State: closed - Opened by zhengJade about 2 years ago
- 1 comment
#40 - Define abstract edge to inherit common attributes to derived edge to support per_node_limit feature
Issue -
State: open - Opened by qishipengqsp over 2 years ago
Labels: enhancement, Future work
#40 - Define abstract edge to inherit common attributes to derived edge to support per_node_limit feature
Issue -
State: open - Opened by qishipengqsp over 2 years ago
Labels: enhancement, Future work
#39 - enrich the properties
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
#38 - add relevance to each query
Issue -
State: open - Opened by qishipengqsp over 2 years ago
Labels: enhancement, Future work
#37 - refine queries and format code with autowrap
Pull Request -
State: closed - Opened by qishipengqsp over 2 years ago
#36 - unify diagrams in transaction workload
Pull Request -
State: closed - Opened by qishipengqsp over 2 years ago
#35 - add chokepoints without linking them with queries
Pull Request -
State: closed - Opened by qishipengqsp over 2 years ago
#34 - add design concepts and format all latex code
Pull Request -
State: closed - Opened by qishipengqsp over 2 years ago
#33 - rewrite introduction and fix #3
Pull Request -
State: closed - Opened by qishipengqsp over 2 years ago
#32 - add abstract and execution summary
Pull Request -
State: closed - Opened by qishipengqsp over 2 years ago
#31 - fix #17: carve out short query
Pull Request -
State: closed - Opened by qishipengqsp over 2 years ago
#30 - [Data] Transfer failure should be considered in the benchmark, which is applied in malicious activity monitoring
Issue -
State: open - Opened by qishipengqsp over 2 years ago
- 1 comment
Labels: enhancement, Future work
#29 - [Query] A high-complexity path query in Read Query #7
Issue -
State: closed - Opened by BingTong0 over 2 years ago
- 2 comments
#28 - [Query] Round to keep 4 decimal places about blockRatio in Read Query #5 and #6
Issue -
State: closed - Opened by BingTong0 over 2 years ago
- 1 comment
#27 - [Query] Result doesn't mean cycle-detection in Read Query #4
Issue -
State: closed - Opened by BingTong0 over 2 years ago
#26 - [Query] Add time range on the deposite relationship in Read Query #2
Issue -
State: closed - Opened by BingTong0 over 2 years ago
#25 - [Query] Add more queries from TF members @CreateLink
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
#24 - [Data] Add annotation about the data simulation scenario
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
#23 - [Data] Annotate the one-to-many or many-to-many relationship between two vertex types along with the edge multiplicity
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 1 comment
#22 - [Spec Writing] optimize the generation of spec pdf file
Issue -
State: open - Opened by qishipengqsp over 2 years ago
- 1 comment
Labels: enhancement, Future work
#21 - [Query] specify the return type of paths, e.g. Read Query #13 and #7
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
#20 - [Query] specifiy the ratios in Read Query #9
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
#19 - [Query] Merge the queries with similar patterns
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
#18 - [Read Write Query] relation between isolation level of SUT and RW query?
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 1 comment
Labels: Transaction workload design, Future work
#17 - [Query] Considering if we need carve out the "short queries"
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
Labels: Transaction workload design
#16 - [Spec Writing] unify the diagram and figures of queries
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 1 comment
#15 - [Query] Add more queries that applies function expression like min(), max(), etc..
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
Labels: Transaction workload design
#14 - [Data] Consider removing the timestamp attribute in `signIn` edge
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 1 comment
#13 - [Spec Writing] Refine the diagrams of the queries in the formats and description
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 2 comments
Labels: Future work
#12 - [Query] thresholds and time sequencing in read query #8
Issue -
State: closed - Opened by tian-zhong over 2 years ago
- 1 comment
Labels: Transaction workload design
#11 - [Query] add delete query
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
Labels: Transaction workload design
#10 - [Audit] specify the validation rules
Issue -
State: open - Opened by qishipengqsp over 2 years ago
- 2 comments
Labels: Future work
#9 - [Driver] Read Write Query definition and weight measurement
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 1 comment
Labels: Transaction workload design
#8 - [Data] More data profiling of different timestamp and distinguished edge types required
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 2 comments
Labels: Data schema design
#7 - wrong naming convention for property definition in table 2.4
Issue -
State: closed - Opened by tian-zhong over 2 years ago
#6 - [Test] A issue to test webhooks
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 2 comments
#5 - [Raw comments] Concerning data distribution and AP workload
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 3 comments
#4 - [Schema] add balance attribute to vertex Loan.
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
#3 - [Spec Writing] section 1.3 describing the differences should be more clear
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
Labels: Future work, Documentation
#2 - [Schema] Gurantee between Company entites?
Issue -
State: closed - Opened by qishipengqsp over 2 years ago
- 3 comments
#1 - [Schema] Gurantee between Company entites?
Issue -
State: closed - Opened by TuGraph-Tech over 2 years ago