MarginaliaSearch/code/processes/crawling-process/model
Viktor Lofgren b8581b0f56 (crawler) Safe sanitization of headers during warc->slop conversion
The warc->slop converter was rejecting some items because they had headers that were representable in the Warc code's MessageHeader map implementation, but illegal in the HttpHeaders' implementation.

Fixing this by manually filtering these out.  Ostensibly the constructor has a filtering predicate, but this annoyingly runs too late and fails to prevent the problem.
2025-01-31 12:47:42 +01:00
..
java (crawler) Safe sanitization of headers during warc->slop conversion 2025-01-31 12:47:42 +01:00
test/nu/marginalia/crawling Fix refactoring gore 2025-01-21 15:08:04 +01:00
build.gradle Merge branch 'master' into slop-crawl-data-spike 2025-01-21 13:32:58 +01:00
readme.md (doc) Correct dead links and stale information in the docs 2024-09-13 11:01:05 +02:00

Crawling Models

Contains crawl data models shared by the crawling-process and converting-process.

To ensure backward compatibility with older versions of the data, the serialization is abstracted away from the model classes.

The new way of serializing the data is to use parquet files.

The old way was to use zstd-compressed JSON. The old way is still supported for now, but the new way is preferred as it's not only more succinct, but also significantly faster to read and much more portable. The JSON support will be removed in the future.

Central Classes

Serialization

These serialization classes automatically negotiate the serialization format based on the file extension.

Data is accessed through a SerializableCrawlDataStream, which is a somewhat enhanced Iterator that can be used to read data.

Parquet Serialization

The parquet serialization is done using the CrawledDocumentParquetRecordFileReader and CrawledDocumentParquetRecordFileWriter classes, which read and write parquet files respectively.

The model classes are serialized to parquet using the CrawledDocumentParquetRecord

The record has the following fields:

  • domain - The domain of the document
  • url - The URL of the document
  • ip - The IP address of the document
  • cookies - Whether the document has cookies
  • httpStatus - The HTTP status code of the document
  • timestamp - The timestamp of the document
  • contentType - The content type of the document
  • body - The body of the document
  • etagHeader - The ETag header of the document
  • lastModifiedHeader - The Last-Modified header of the document

The easiest way to interact with parquet files is to use DuckDB, which lets you run SQL queries on parquet files (and almost anything else).

e.g.

$ select httpStatus, count(*) as cnt 
       from 'my-file.parquet' 
       group by httpStatus;
┌────────────┬───────┐
 httpStatus   cnt  
   int32     int64 
├────────────┼───────┤
        200     43 
        304      4 
        500      1 
└────────────┴───────┘