ngcp-panel

Commit Graph

Author	SHA1	Message	Date
Rene Krenn	171d79210a	MT#20027 porting number history -undo unique lnp_numbers: undo misleading unique keys -retain lnp_provider delete cascade restriction -api: wire lnp_numbers_actual -lnpnumbers collection pagination request takes several seconds (up to tens of for 200k lnp numbers), too slow especially for GET /api/lnpnumbers/?number=.. lookups -query param is properly injected into the virtual view sql query, so the lookup is fast now. -panel UI custom datatable filter to switch between complete history (all records) and actual portings -"terminate" lnp number: DELETE /api/lnpnumbers/?number=x +special use-case for melita's crm +all empty or future "end" timestamps of records are set to now(), so a subsequent listing shows no records any more. -number parameter is forced, other collection query params are currently not supported for DELETE Change-Id: I7b69d16a2d4f38ea84fc1cc0b407fa67e0f5ef8b	9 years ago
Andreas Granig	362b5711a4	MT#16777 Write chunks to db to not run out of mem If we have a 20M lnp file to upload, putting everything into the numbers array is killing the fcgi process on low-mem machines. Make sure to write each 2k chunk to DB and clear the array afterwards. Change-Id: I857be5d6a0195607b1fcb86db3327a9fd10ce5f1	10 years ago
Andreas Granig	492f58786e	MT#4067 Implement LNP via panel and API CAUTION: uses some optimized bulk-insert and truncate mechanisms bypassing DBIC to make it reasonably fast (1M rows up in ~20s). Optimized CSV download also to use partial writes to avoid gateway timeouts on huge files. Allows to handle LNP carriers in /api/lnpcarriers/. Allows to handle LNP numbers and batch uploads in /api/lnpnumbers/. Change-Id: I2f659bf5ee53270bedd3bb416a011bddc558b9ae	10 years ago

Author

SHA1

Message

Date

Rene Krenn

171d79210a

MT#20027 porting number history

-undo unique lnp_numbers: undo misleading unique keys
-retain lnp_provider delete cascade restriction
-api: wire lnp_numbers_actual

-lnpnumbers collection pagination request takes several
 seconds (up to tens of for 200k lnp numbers), too slow
 especially for GET /api/lnpnumbers/?number=.. lookups
-query param is properly injected into the virtual view
 sql query, so the lookup is fast now.

-panel UI custom datatable filter to switch between
 complete history (all records) and actual portings

-"terminate" lnp number: DELETE /api/lnpnumbers/?number=x
 +special use-case for melita's crm
 +all empty or future "end" timestamps of records
  are set to now(), so a subsequent listing shows no
  records any more.
-number parameter is forced, other collection query params
 are currently not supported for DELETE

Change-Id: I7b69d16a2d4f38ea84fc1cc0b407fa67e0f5ef8b

Andreas Granig

362b5711a4

MT#16777 Write chunks to db to not run out of mem

If we have a 20M lnp file to upload, putting everything into the
numbers array is killing the fcgi process on low-mem machines.
Make sure to write each 2k chunk to DB and clear the array
afterwards.

Change-Id: I857be5d6a0195607b1fcb86db3327a9fd10ce5f1

Andreas Granig

492f58786e

MT#4067 Implement LNP via panel and API

CAUTION: uses some optimized bulk-insert and truncate mechanisms
bypassing DBIC to make it reasonably fast (1M rows up in ~20s).

Optimized CSV download also to use partial writes to avoid
gateway timeouts on huge files.

Allows to handle LNP carriers in /api/lnpcarriers/.
Allows to handle LNP numbers and batch uploads in /api/lnpnumbers/.

Change-Id: I2f659bf5ee53270bedd3bb416a011bddc558b9ae

3 Commits (6c538c2a69ad074d860b744f0df15017fdc297ee)