graflo.architecture.schema.db_aware¶
DB-aware projections for logical graph configs.
These wrappers materialize database-specific naming/defaults from logical
VertexConfig/EdgeConfig and DPProfile without mutating logical models.
EdgeConfigDBAware
¶
DB-aware projection wrapper for EdgeConfig.
Source code in graflo/architecture/schema/db_aware.py
240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 | |
relationship_merge_property_names(edge)
¶
Relationship properties used for edge upsert/MERGE keys (per backend).
Uniqueness is (source_id, *identity_fields, target_id) for the first
logical identities key (endpoints are matched separately on vertices).
Additional identities keys are compiled into separate unique indexes
via :meth:compile_identity_indexes but do not change the writer merge key.
If that key yields no relationship fields, or identities is empty,
falls back to all declared edge attribute names.
Source code in graflo/architecture/schema/db_aware.py
EdgeIngestionOverlay
¶
Bases: Protocol
Ingestion-only signals that affect DB projection (e.g. TigerGraph DDL).
Source code in graflo/architecture/schema/db_aware.py
EdgeRuntime
dataclass
¶
Resolved DB-facing runtime data for one logical edge.
Source code in graflo/architecture/schema/db_aware.py
SchemaDBAware
dataclass
¶
VertexConfigDBAware
¶
DB-aware projection wrapper for VertexConfig.
Source code in graflo/architecture/schema/db_aware.py
compile_secondary_identity_indexes()
¶
Register a lookup index for every declared secondary identity.
index(vertex_name)
¶
Get primary index for a vertex (DB layer needs Index for collection setup).
match_fields(vertex_name, selector)
¶
Fields an edge endpoint is matched on, with DB-aware identity fallback.
Source code in graflo/architecture/schema/db_aware.py
WeightConfig
¶
Bases: ConfigBaseModel
Configuration for edge weights and relationships.
This class manages the configuration of weights and relationships for edges, including source and target field mappings.
Attributes:
| Name | Type | Description |
|---|---|---|
vertices |
list[Weight]
|
List of weight configurations |
direct |
list[Field]
|
List of direct field mappings. Can be specified as strings, Field objects, or dicts. Will be normalized to Field objects by the validator. After initialization, this is always list[Field] (type checker sees this). |
Examples:
>>> # Typed fields: list of Field objects
>>> wc2 = WeightConfig(direct=[
... Field(name="date", type="DATETIME"),
... Field(name="weight", type="FLOAT")
... ])
>>> # From dicts (e.g., from YAML/JSON)
>>> wc3 = WeightConfig(direct=[
... {"name": "date", "type": "DATETIME"},
... {"name": "weight"} # defaults to None type
... ])
Source code in graflo/architecture/schema/db_aware.py
direct_names
property
¶
Get list of direct field names (as strings).
Returns:
| Type | Description |
|---|---|
list[str]
|
list[str]: List of field names |
compile_secondary_identity_indexes(vertex_config, db_profile)
¶
Register a lookup index for every declared secondary identity.
Endpoint resolution filters on these fields, so the index is what keeps the lookup from degrading into a scan — and on NebulaGraph a tag index is required outright for the property lookup to run at all.
Indexes are non-unique: secondary identities are softly unique, and asking the database to enforce uniqueness would reject exactly the duplicate data the ambiguity policy exists to handle.
Called from :meth:Schema.finish_init so the profile is populated for every
backend, including those whose index definition does not go through
:meth:Schema.resolve_db_aware.