Skip to content

Update transaction object mapping for PriceOracle #68

@pkcs8

Description

@pkcs8

Oracle transactions have a peculiar behavior - it takes AssetPrice in base-10, but returns AssetPrice in base-16. Due to this transaction schema mapping is broken, and returns error while indexing.

2024-11-08T11:29:38+01:00 ERR Bulk index error hash=5C41B5C7C88A78FDBC7372FE2BCB6E30B3CB6AA74A3BFE2350A885A250DA6CC8 
reason="[1:300] failed to parse field [PriceDataSeries.PriceData.AssetPrice] of type [long] in 
document with id '5C41B5C7C88A78FDBC7372FE2BCB6E30B3CB6AA74A3BFE2350A885A250DA6CC8'. 
Preview of field's value: '1a905'" type=document_parsing_exception

Update config/mapping/transaction.go and fix mappings for PriceDataSeries array.

Related transaction: https://xrpscan.com/tx/5C41B5C7C88A78FDBC7372FE2BCB6E30B3CB6AA74A3BFE2350A885A250DA6CC8

Metadata

Metadata

Assignees

Labels

serverServer side component

Type

No type

Projects

Status

Todo

Relationships

None yet

Development

No branches or pull requests

Issue actions